Payment Services Directive 2 PSD2

Payment Services Directive 2, or PSD2, is a European payments regulation that introduced stronger authentication, open banking rules, and consumer protections for electronic payments. It applies across the European Economic Area and affects banks, payment service providers, fintech companies, and many online sellers that accept European payments.

For ecommerce and checkout teams, the most visible part of PSD2 is Strong Customer Authentication. SCA can require buyers to complete extra verification during online payment, which can affect approval rates, checkout conversion, and fraud risk.

Key Takeaways

• PSD2 is a European payments regulation for electronic payments and payment service providers.
• Strong Customer Authentication is one of the most visible PSD2 requirements for online sellers.
• SCA can add checkout friction when a buyer needs extra verification.
• PSD2 also supports open banking through regulated access to bank account data with customer consent.
• Sellers should understand PSD2 as a payment compliance and checkout-experience issue.

PSD2 and Strong Customer Authentication

Strong Customer Authentication requires payment authentication using at least two independent factors from categories such as knowledge, possession, and inherence. In plain terms, a buyer may need something they know, something they have, or something they are.

Examples include a password, a phone, a banking app approval, or biometric verification. The exact experience depends on the bank, payment method, region, transaction type, and payment provider.

SCA is meant to reduce fraud, but it can also interrupt checkout. If the authentication flow fails, times out, or confuses the buyer, the sale may be lost.

PSD2 and Checkout Conversion

PSD2 affects checkout optimization because payment security and buyer experience meet at the same moment. A seller wants legitimate buyers to complete payment while risky transactions receive the right level of review.

A good checkout should make the payment step feel trustworthy, support SCA flows properly, and avoid adding unnecessary friction before authentication. It should also handle failed authentication gracefully, giving the buyer a clear path to try again or choose another payment method.

Exemptions and Transaction Routing

PSD2 includes exemptions and rules that can reduce unnecessary authentication in some cases. Examples may include low-value transactions, recurring transactions, trusted beneficiaries, or low-risk transactions. Whether an exemption applies depends on the transaction and the payment provider.

Sellers usually do not manage these rules manually. Their payment gateway or processor often handles routing, authentication requests, and exemption logic. Still, sellers should understand that payment setup can influence conversion and approval rates.

PSD2 and Subscriptions

Subscriptions can be affected by PSD2 because the first payment and later renewals may be treated differently. The initial setup may require authentication. Later merchant-initiated renewals may follow different rules when properly set up.

Clear subscription checkout language still matters. Buyers should understand the billing cadence, renewal amount, cancellation path, and what happens if a payment fails. Confusion around recurring billing can create payment disputes even when the payment flow is compliant.

PSD2 setup can also affect payment recovery. If the first payment is not authenticated or the recurring agreement is unclear, future renewal attempts may fail more often. Sellers should monitor failed renewals, authentication failures, and support tickets together.

PSD2 and Open Banking

PSD2 also supports open banking. With customer consent, regulated third-party providers can access account information or initiate payments through bank connections. This created room for account-to-account payments, financial apps, and new payment experiences.

For sellers, open banking can mean more payment options over time. It also raises expectations around consent, data handling, and clear user experience.

PSD2 is closely related to regional bank-payment methods and to wider payment-method strategy. A checkout that serves European buyers should consider which payment methods feel familiar and which authentication flows the audience can complete easily.

What Sellers Should Watch

Sellers accepting European payments should monitor authentication failure rate, payment approval rate, conversion rate, failed payments, disputes, and customer support tickets related to payment verification.

If buyers often fail authentication, the issue may involve payment method choice, bank behavior, checkout messaging, device flow, or processor setup. The seller may need better payment-method coverage or clearer instructions at checkout.

Practical Example

A seller offers a subscription to customers in Europe. The first checkout payment may trigger SCA through the buyer's bank. After approval, future renewals may run as merchant-initiated transactions if the subscription is set up correctly. The checkout explains renewal terms, the payment provider handles authentication, and support can help buyers who fail verification.

PSD2 is not only a legal topic. It is part of how payment trust, fraud reduction, and checkout completion work together.