Conception de flux de paiement pour la SCA

New regulation known as Strong Customer Authentication, or SCA, is changing online payments in Europe. See the impact it may have on your payment flows and learn how Stripe can help.


Last updated on September 14, 2019

Starting September 14, 2019 new payments regulation is being rolled out in Europe, which mandates Strong Customer Authentication (SCA) for many online payments in the European Economic Area (EEA). SCA is part of the second Payment Services Directive (PSD2).

To meet the new SCA requirements, a form of two-factor authentication is required for many online card payments in Europe. Without authentication, many payments may be declined by your customers’ banks. We designed new foundational payments APIs to help businesses handle this change and take full advantage of any SCA exemptions.

We recommend using this guide to understand how different types of payment flows have to change due to SCA, and to reference it as you redesign your payment flows.

How payments are changing

Traditional card payments usually involve two steps: authorization and capture. A payment is authorized when a customer’s bank or card issuer decides to approve a payment, and the payment is captured when the card is charged.

With SCA, there is an additional and mandatory step before authorization and capture: authentication. This step helps protect customers by preventing fraud. To authenticate a payment, a customer responds to a prompt from their bank and provides additional information. This may be something they know, like a password, something they use, like their phone, or something that’s part of who they are, like their fingerprint.

The most common way to authenticate a payment is a method called 3D Secure. You may recognize 3D Secure by its branded names, such as “Visa Secure” or “Mastercard Identity Check.” There’s a new version, called 3D Secure 2, that is expected to become the standard method to authenticate payments. You can learn about the differences between these methods in our 3D Secure 2 guide. Our new payments APIs, Stripe Billing, and the new version of Stripe Checkout, all support 3D Secure 2.

No matter what method you use, customers must be on-session to authenticate, which means they need to be using your website or app. Adding this step is be simpler for businesses that charge customers right away, and more complex for businesses that charge customers after they’ve left the checkout flow. (This is sometimes called off-session.)

The scenarios in this guide offer examples of how these three steps (authentication, authorization, and capture) can vary depending on how and when you charge your customers.

  1. Authentifier
    Un client authentifie un paiement en ligne.

    Un client répond à une invite 3D Secure de sa banque lui demandant de fournir des informations supplémentaires pour authentifier le paiement. Voir 3D Secure côté client.

    L'authentification est nécessaire lorsqu'un paiement n'est pas admissible à une exemption ou lorsque la banque du client refuse une demande d'exemption. Notre API Payment Intents sollicite automatiquement les exemptions admissibles avant d'ajouter l'étape d'authentification. Cela simplifie les flux de paiement et préserve les taux de conversion.

    Le saviez-vous ? L'authentification doit avoir lieu pendant que le client est en session, ou qu'il est connecté à votre site Web ou application. En conséquence, cette étape se déroule généralement au moment où le client passe sa commande.

  2. Autoriser
    Votre entreprise demande à la banque du client d'approuver le paiement.

    La banque du client décide d'approuver ou de refuser un paiement. En cas d'approbation, les fonds sont bloqués et garantis pendant sept jours. En cas de refus d'une demande d'autorisation, votre entreprise doit faire en sorte que le client rouvre une session pour réauthentifier le paiement, puis demander une nouvelle autorisation.

    Le saviez-vous ? Une demande d'autorisation peut encore être refusée par la banque du client après l'authentification. Cette situation peut se produire si le client ne possède pas suffisamment de fonds ou si la carte a expiré.

  3. Jusqu'à 7 jours

    Le délai entre l'autorisation et le débit peut aller jusqu'à sept jours, mais la plupart des entreprises débitent le paiement immédiatement après son autorisation.

    Le saviez-vous ? La banque d'un client peut indiquer qu'un paiement est « en attente » s'il a été autorisé sans avoir été débité.

  4. Débiter
    L'entreprise débite la carte du client, ce qui valide le paiement.

Understanding exemptions

There are certain types of payments—such as low-risk transactions, fixed-amount subscriptions, phone sales, and merchant-initiated transactions—that may be exempt from SCA. Merchant-initiated transactions are payments made with a saved card when the customer is off-session. Common examples include a gym membership payment or utility bill. To qualify for this exemption, your business must have an agreement with your customer and have them authenticate their card when it’s being saved or authenticate the first payment. Our Strong Customer Authentication guide goes into greater detail about these exemptions and others.

Stripe’s SCA-ready payment APIs and products help businesses take full advantage of these opportunities by automatically requesting exemptions. When exemptions are accepted by your customers’ banks, your customers won’t have to authenticate, minimizing the impact on conversion.

However, businesses can’t rely on exemptions and must design their payment flows to authenticate customers when necessary. This is because the rules around exemptions depend on your customers’ banks. The banks evaluate each payment and decide whether an exemption applies—and individual banks will apply exemptions differently.

Scénarios commerciaux

Afin d’illustrer l’impact de la SCA et son application, nous vous présentons ci-dessous la façon dont une étape d’authentification peut être intégrée aux flux de paiement pour différents types d’entreprises.

Retour aux guides
You’re viewing our website for Luxembourg, but it looks like you’re in the United States. Switch to the United States site