Laut Sicherheitsmaßnahmen der PSD2, der sogenannten Strong Customer Authentication (SCA), müssen Kunden ihre Online-Käufe mit der Eingabe eines. Strong Customer Authentication: die neue Anforderung für Onlinetransaktionen. Wir klären: Was ist SCA? Was bedeutet es für den. Eine starke Kundenauthentifizierung ist eine Anforderung der überarbeiteten EU-Richtlinie über Zahlungsdienste für Zahlungsdienstleister im Europäischen Wirtschaftsraum.
Starke KundenauthentifizierungDie SCA (Strong-Customer-Authentication) oder starke Kundenauthentifizierung soll für mehr Sicherheit und Transparenz im finanziellen Bereich. Eine starke Kundenauthentifizierung ist eine Anforderung der überarbeiteten EU-Richtlinie über Zahlungsdienste für Zahlungsdienstleister im Europäischen Wirtschaftsraum. Lernen Sie, was starke Kundenauthentifizierung (Strong Customer Authentication, SCA) im Rahmen von PSD2 bedeutet und wie Sie Ihr Unternehmen dafür.
Strong Customer Authentication Background VideoA conversation about Strong Customer Authentication
To facilitate ongoing commitment to the managed rollout and for the best customer and industry outcomes, UK Finance set up a central Programme Management Office.
In the managed rollout, we propose a number of measures aimed at implementing SCA at pace, but also in a way that is structured to help coordinate as well as help answer the remaining tricky questions the industry still has.
This page will be regularly updated with information for the industry, merchants and consumers. Any app on the mobile device might read these to create a remote, fake environment with identical identifiers.
Instead of sending over a profile, some value needs to be derived from a possession element that itself remains secret. The most common example is a cryptographic key, where that key is used in an algorithm to prove possession of the key.
There are many approaches for storing and using cryptographic keys on a phone. These approaches range from simple file storage, using the keystore of the operating system, to using secure hardware.
Another question that needs to be addressed is which kind of cryptographic algorithm to use. As we will show in part 3 of this series, the use of public-key cryptography offers many benefits over legacy choices such as a One Time Password OTP.
Knowledge elements need be entered directly not cached by the app or phone by the user. Single use credentials printed on token cards are not considered a knowledge element, even though these are also entered by the user.
A smartphone has quite limited input capabilities, ruling out complex passwords as these are too error prone to enter.
In the case of changes to the payment amount or payee, the authentication token will no longer be valid and a new one needs to be generated and used.
The inclusion of such dynamic linking elements in SCA features a well encompassed additional authentication layer beyond the previously required guidelines.
With the new Payments Directive, banks and other financial institutions will have to comply with the SCA regulations.
The good news for merchants and issuers is that 3DS 2. Other card-based payment methods such as Apple Pay or Google Pay already support payment flows with a built-in layer of authentication biometric or password.
These can be a great way for businesses to offer a frictionless checkout experience while meeting the new requirements. Under this new regulation, specific types of low-risk payments may be exempted from Strong Customer Authentication.
Payment providers like Stripe are able to request these exemptions when processing the payment. Building authentication into your checkout flow introduces an extra step that can add friction and increase customer drop-off.
Using exemptions for low-risk payments can reduce the number of times you will need to authenticate a customer and reduce friction.
The Opinion also explains that sufficient time has been available for the industry to prepare for the application date of SCA, given that the definition of SCA had been set out in PSD2 when it was published in , which gave clear indications that existing authentication approaches would need to be phased out, and because PSD2 already granted an additional month period for the industry to implement SCA.
However, the Opinion acknowledges the complexity of the payments markets across the EU and the challenges arising from the changes that are required, in particular by actors that are not payment service providers PSPs and, therefore, not directly subject to PSD2 and the EBA's technical standards, such as e-merchants, which may lead to some actors in the payments chain not being ready by 14 September The EBA, therefore, accepts that, on an exceptional basis and in order to avoid unintended negative consequences for some payment service users after 14 September , NCAs may decide to work with PSPs and relevant stakeholders, including consumers and merchants, to provide limited additional time.
This is to allow issuers to migrate to authentication approaches that are compliant with SCA, such as those described in this Opinion, and acquirers to migrate their merchants to solutions that support SCA.
This supervisory flexibility is available under the condition that PSPs have set up a migration plan, have agreed the plan with their NCA, and will execute the plan in an expedited manner.
In order to fulfil the objectives of PSD2 and the EBA of achieving consistency across the EU, the EBA will later this year communicate deadlines by which the aforementioned actors will have to have completed their migration plans.
The revised Payment Services Directive was published in November , entered into force on 13 January and applies since 13 January The Directive brings fundamental changes to the payments market in the EU, in particular by requiring SCA to be applied by payment services providers PSPs when carrying out remote electronic transactions.
SCA is defined in the Directive as an "authentication based on the use of two or more elements categorised as knowledge something only the user knows , possession something only the user possesses and inherence something the user is that are independent, in that the breach of one does not compromise the reliability of the others, and is designed in such a way as to protect the confidentiality of the authentication data.
The EBA had been mandated to support the Directive by developing regulatory technical standards RTS setting out the details on strong customer authentication and common and secure communication RTS on SCA and CSC , including its exemptions, and to regulate the access to customer payment account data held in account servicing payment service providers.
The RTS deliberately refrains from referring to any particular authentication approaches in the industry, in order to ensure that the RTS remains technology neutral and future-proof.
In the Opinion, the EBA clarifies specific aspects on the use of qualified certificates for electronic seals QSealCs and qualified certificates for website authentication QWACs for the purpose of identification of payment service providers PSPs under the RTS, the content of these certificates, and the process for their revocation.
The Opinion aims at addressing questions and concerns raised by market participants related to the use of eIDAS certificates. E-commerce merchants must update the payment flows in their websites and apps to support authentication.
The public submission  process to the ECB identified three solutions to strong customer authentication, two of which are based on reliance authentication , and the other being the new variant of 3-D Secure which incorporates one-time passwords.
PSD2 strong customer authentication has been a legal requirement for electronic payments and credit cards since 14 September In , Visa criticised the proposal of making strong customer authentication mandatory, on the grounds that it could make online payments more difficult, and thus hurt sales at online retailers.