PSD2 Compliance: strong customer authentication without friction
The PSD2 raises the level of security requirements ruling the validation of financial transactions and regulates access to banking data with, in particular, the generalization of strong authentication for specific operations, including online payment. E-merchants, payment service providers, banks, don’t be afraid of losing your customers by complying with the PSD2.
What is the PSD2 regulation?
Payment security is achieved through strong authentication with the PSD2
What is strong authentication, also known as MFA (Multifactor Authentication)?
Authentication is said to be strong when a user must, in order to log in or validate his operation, provide two elements from different categories among the three possible ones. The 3 categories of identification factors are:
- something I know: the most common example is the password for applications or the PIN code for payment cards.
- something I own: a phone, a computer, a flash drive, a connected device. There are many possibilities. The Possession factor is usually referred to as a token.
- something that I am: it’s essentially biometrics – fingerprint, retinal, voice, facial recognition.
PSD2 Compliance : operations requiring strong customer authentication (SCA)
The PSD2 provides for some exceptions to these rules, listing transactions that are considered low risk. These exceptions include payments up to €50 in contactless mode or €30 online, or transfers to a beneficiary previously validated by strong authentication.
No, SMS validation is not strong authentication
The main consequence of PSD2 is that the usual process of the payment security system (3D Secure), which validates operations by sending a one-time password (OTP) via SMS to be re-entered by the user, no longer complies. It is indeed based on a single factor, the possession of a mobile phone, and can very easily be circumvented by a cyber attack like SMShing.
The directive thus changes the customer journey in e-commerce at its most crucial point: payment validation. Hence the fears of online merchants who are worried about an increase in shopping cart abandonment due to what they perceive as a more complex customer journey. This concern is easily understandable if we consider only the most widespread multi-factor authentication solutions. Generally not very secure, they are also complicated to use, often requiring the re-entry of a single-use password obtained by more or less practical means.
Compliance PSD2 : TrustBuilder.io MFA, the multi-factor authentication solution that ticks all the boxes
Complying with the entire PSD2 regulation is a complex project, requiring many skills. The good news is that inWebo’s MFA solution not only ticks all the boxes necessary to secure transactions but also offers exclusive advantages to facilitate the implementation and improve the user experience.
With TrustBuilder.io MFA SaaS Multifactor Authentication
access to accounts is protected
TrustBuilder.io MFA can be easily deployed and integrated to protect external access to bank deposit accounts or accounts with payment providers.
sensitive operations and status changes are sealed by a dynamic link
This dynamic link, in accordance with PSD2, ensures the traceability and security of all transactions deemed to be at risk such as the addition of a transfer beneficiary.
strong client authentication (SCA) is ensured
SCA (Strong Customer Authentication) involves authentication with at least 2 factors, which excludes one-time password solutions via SMS. TrustBuilder.io offers the most complete range of connection factors, with its mobile, desktop, browser (Deviceless and Smartphoneless) tokens.
Essential condition for its banking customers to be PSD2 certified, inWebo is a certified Supplier of Externalized Essential Services, guaranteeing the resilience of the MFA service.
How to be PSD2 compliant by offering a frictionless customer journey
However, the main obstacle to PSD2 compliance today is not technical but, as we have seen, linked to fears about changes in the payment journey.
This is where one of the main differentiators of the inWebo solution comes in: strong authentication without a smartphone, via a simple browser. The Deviceless (or Smartphoneless) token allows the customer to authenticate in compliance with PSD2 without any other trusted device than his browser, via a simple reusable PIN code. This is achieved while ensuring the highest level of access security of any MFA solution through the use of proprietary dynamic random key technology. To learn more about this technological achievement, see our article Deviceless MFA.
The implementation of the inWebo MFA solution not only does not degrade the connection experience, but it even makes it simpler by removing the need to have a smartphone, to have mobile network connection to receive the SMS and to re-enter a unique code, a major source of mistakes and payment abandonment.
The route is therefore simplified. But it is also unified. With hundreds of available integrations, via connectors, its API mode or its SDK, the inWebo MFA solution can be deployed on all application accesses, not only on bank account accesses. Thus, the user, who wants to connect to his email, validate a transaction, or access his company’s VPN, will benefit from a unified interface, a uniform login experience and even a unique PIN code (or any other knowledge factor) without any security degradation.
Do not fear PSD2 compliance
Online retailers, payment service providers, banks, you need not be afraid of losing your customers by complying with PSD2. With TrustBuilder.io, you can combine strong customer authentication with a frictionless customer journey. And as an added bonus, you’ll get a Full SaaS MFA solution that can be deployed in a few clicks on thousands of users, without any equipment constraints.
Check out the replay of our webinar
PSD2 and strong client authentication SCA: combine security and a simplified user experience
The PSD2 is the revised Payment Services Directive issued by the European Commission which regulates payment services throughout the European Union. The Payment Services Directive was first adopted in November 2015 (PSD1), and then enforced throughout the European Union in January 2018 (PSD2). The directive raises the level of security requirements ruling the validation of financial transactions and regulates access to banking data.
PSD2 compliance requires financial services to setup strong customer authentication (SCA) on 3 types of operations: (i) access and management of the payment account, (ii) online payment and (iii) online transaction with a significant risk of fraud.
PSD2 brings more competition to the payments market by allowing non-banks to offer new and innovative services to their customers. As a result, since the adoption of PSD1 in 2007, new online payment services have emerged – known as FinTechs or “Third Party Providers (TTPs)”. With PSD2, FinTechs have been required to follow the same rules as traditional payment service providers which as a result guarantees that they can offer their services throughout the EU.