Skip to content
The ValyrPayMerchant Services

Rules and compliance

3-D Secure and strong customer authentication: a merchant’s guide

How strong customer authentication works under PSD2 and UK rules: exemptions, liability shift, and balancing 3-D Secure friction with approvals.

8 min readUpdated 23 October 202612 sources

Contents8 sections
  1. What strong customer authentication requires
  2. How 3-D Secure works
  3. The exemptions
  4. Liability: two different questions
  5. Friction versus approval rates
  6. The UK and the EU are diverging
  7. What to do next
  8. Sources

What strong customer authentication requiresLink to this section

SCA comes from the EU’s second Payment Services Directive (PSD2) and, in the UK, from the Payment Services Regulations 2017 (regulation 100) and the FCA’s technical standards. It requires a payment service provider to authenticate the customer using at least two independent elements from different categories:

  • Knowledge — something only the customer knows, such as a password or PIN.
  • Possession — something only the customer has, such as their phone, proven by a one-time code or a banking app.
  • Inherence — something the customer is, such as a fingerprint or face scan.

For remote payments, the authentication must also be dynamically linked to the amount and the payee, so the customer sees exactly what they are approving and a code cannot be reused for a different payment.

The FCA explains that SCA applies to electronic payments initiated by the payer, including card payments initiated through the payee — an online checkout, for example. Payments initiated by the payee are not subject to SCA, provided no action of the payer is needed to trigger them. That covers merchant-initiated transactions made under a mandate the customer has given, such as a subscription renewal. Setting up that mandate online does require SCA, and a price increase outside the original mandate needs the customer’s agreement (FCA Approach Document, paragraph 20.9).

Who is responsibleLink to this section

SCA is an obligation on regulated payment service providers — the card issuer and the acquirer — not directly on merchants. In practice, merchants carry it out by supporting 3-D Secure in their checkout through their gateway or payment service provider. The issuer decides whether to authenticate, and makes the final call on whether an exemption requested by the merchant or acquirer is accepted.

When the rules took effectLink to this section

SCA applied in the EEA from 14 September 2019, with the European Banking Authority allowing card e-commerce a migration period that ended on 31 December 2020. In the UK the FCA extended the e-commerce deadline more than once, finally to 14 March 2022 (FCA statement, 20 May 2021).

How 3-D Secure worksLink to this section

3-D Secure is the card industry’s authentication protocol. The current generation, EMV 3-D Secure, is maintained by EMVCo; the card schemes brand their programmes as Visa Secure and Mastercard Identity Check. EMV 3-D Secure works in browsers and inside mobile apps, and lets the merchant send the issuer far more information about the transaction and device than the original protocol did.

A 3-D Secure request has two possible outcomes:

  • Frictionless flow. The issuer’s risk engine is satisfied by the data it receives and authenticates the customer without any interaction. The customer sees nothing.
  • Challenge flow. The issuer asks the customer to prove who they are — usually by approving the payment in a banking app, entering a one-time code or using biometrics.

The richer and more accurate the data you send — billing and shipping details, account age, device information, previous purchases — the more often issuers can approve without a challenge. EMVCo describes the aim as helping issuers spot risky activity without adding unnecessary friction.

The exemptionsLink to this section

The technical standards allow payment service providers not to apply SCA in defined cases. The EU text is Commission Delegated Regulation (EU) 2018/389; the UK version is maintained by the FCA. The figures differ.

ExemptionEEAUK
Low-value remote payment (Art. 16)Up to €30; SCA again once €100 cumulative or 5 consecutive exempted payments are reachedUp to £25; SCA again once £85 cumulative or 5 consecutive exempted payments are reached
Transaction risk analysis (Art. 18), remote card paymentsUp to €100 at a fraud rate of 0.13% or less; up to €250 at 0.06%; up to €500 at 0.01%Up to £85 at 0.13%; up to £220 at 0.06%; up to £440 at 0.01%
Recurring payments of the same amount to the same payee (Art. 14)SCA when the series is created, changed or first initiated; later payments exemptSame
Trusted beneficiaries (Art. 13)The customer adds the merchant to a list held by their bank (with SCA); later payments may be exemptSame
Secure corporate payments (Art. 17)Dedicated processes for business payers onlySame

Transaction risk analysisLink to this section

TRA is usually the most useful exemption for online merchants. Either the issuer or the acquirer may apply it, provided the payment service provider applying it keeps its own fraud rate for remote card payments at or below the reference rate for the value band, and its real-time risk analysis has flagged nothing unusual — such as abnormal spending, an unusual device, malware, a known fraud pattern or a high-risk location (Article 18). The European Banking Authority has confirmed that only the provider applying the exemption needs to meet the reference rate. Merchants can indicate in a 3-D Secure request that they believe TRA applies, but the issuer always makes the final decision.

Low-value paymentsLink to this section

The low-value exemption is less useful than it looks for merchants. The acquirer cannot see how many exempted payments a card has already made, so an issuer may still demand authentication once its counters are reached — which is why Visa’s guidance recommends considering TRA first.

Out of scope, not exemptLink to this section

Some transactions are outside SCA altogether rather than exempt from it:

  • Merchant-initiated transactions, such as subscription renewals or instalments charged under an agreed mandate. They must be correctly flagged as merchant-initiated and linked to the original authenticated transaction (see subscription billing and card scheme rules).
  • Mail order and telephone order payments.
  • One-leg-out transactions, where the issuer or the acquirer is outside the UK and EEA. SCA should still be applied on a best-effort basis.
  • Anonymous prepaid card payments.

Labelling a customer-initiated payment as merchant-initiated to avoid authentication is not permitted, and issuers are likely to decline it.

Liability: two different questionsLink to this section

Regulatory liabilityLink to this section

Under the Payment Services Regulations 2017, if SCA was required but the payee or the payee’s payment service provider did not accept it, they must compensate the customer’s bank for the losses it has to refund (regulation 77(6)). And a customer is generally not liable for an unauthorised payment where SCA was required but their bank did not require it (regulation 77(4)(c)).

Chargeback liability under scheme rulesLink to this section

The card schemes decide who bears the cost of fraud disputes. Under Visa’s rules, a card-not-present fraud dispute (Dispute Condition 10.4) is invalid when the transaction was authenticated through Visa Secure with EMV 3-D Secure and the authentication value was included in the authorisation (electronic commerce indicator 5), and, with some exceptions, when the issuer or Visa responded with an “attempt” (indicator 6). This is the liability shift: authenticated fraud becomes the issuer’s problem.

Two cautions follow:

  • The shift covers fraud disputes only. It does not protect you against disputes for goods not received, not as described, or cancelled subscriptions. Nor does authentication stop customers querying a charge they do not recognise; a clear billing descriptor does that.
  • Exemptions usually mean you keep fraud liability. If you or your acquirer request an exemption and the payment goes straight to authorisation without authentication, the transaction has not been authenticated, so the protection generally does not apply. An issuer that authenticates through the frictionless flow of 3-D Secure has still authenticated the payment. Confirm the exact rules for your scheme and region with your acquirer.

Friction versus approval ratesLink to this section

Every challenge risks a customer abandoning the checkout; every unauthenticated payment risks a decline or a fraud loss. In the UK and EEA, an issuer may refuse an unauthenticated payment with a “soft decline” asking for SCA, so skipping authentication is not free either. A sound approach balances both:

  1. Send complete, accurate data in every 3-D Secure request. It is the lever you control most directly.
  2. Use exemptions where your provider’s fraud rate qualifies, especially TRA, and accept that you hold fraud liability on those payments.
  3. Authenticate when the risk or the stakes are higher — new customers, high values, changes of card or delivery address, and whenever you set up a stored card or subscription.
  4. Flag merchant-initiated and recurring payments correctly, linking them to the original authenticated transaction, so renewals do not trigger needless challenges.
  5. Handle soft declines automatically by retrying the payment with 3-D Secure rather than failing the order.
  6. Support in-app authentication properly if you sell through a mobile app, rather than sending customers to a browser.
  7. Measure by issuer, country and card type. Authentication success, challenge rate, abandonment and approval rates vary widely; the averages hide the problems.

For merchants with high fraud exposure, acquirers sometimes require 3-D Secure on all eligible transactions as a condition of the account. For low-risk merchants, an exemption-first strategy can work well. Most businesses sit in between and benefit from rules that adapt by risk.

The UK and the EU are divergingLink to this section

Since leaving the EU, the UK has kept SCA but adapted it. The FCA now maintains the UK technical standards. It set the sterling thresholds shown above, and from 19 March 2026 it replaced the fixed contactless limits with a risk-based exemption that lets payment service providers set their own contactless limits (FCA Handbook Notice 136). That change affects card-present payments rather than e-commerce, but it shows the direction: the FCA is adjusting SCA to UK conditions.

The EU is also changing its framework. The Council and the European Parliament reached a provisional agreement on 27 November 2025 on a new Payment Services Regulation and amendments to PSD2, with a strong focus on fraud prevention. As of October 2026 we have not been able to confirm its publication in the Official Journal; until the new regulation applies, PSD2 and the existing technical standards remain the rules for EEA transactions. If you sell in both markets, expect the details to drift further apart and check both rulebooks.

What to do nextLink to this section

Authentication choices sit in your payment stack: how your gateway handles 3-D Secure, which data it sends and how it requests exemptions. Our payment gateway page explains how the ValyrPay payment gateway, available through The ValyrPay Merchant Services, fits into a merchant’s setup, and our consultants can review your authentication and approval data with you. We are not a bank or a payment institution; your issuer and acquirer apply the rules described here.

Sources

Each source was read on the date shown. Card-scheme rules and regulations change; check the current edition before relying on a detail.

  1. FCA Handbook — Technical Standards on Strong Customer Authentication and Common and Secure Methods of Communication, Chapter 3 (exemptions) (external site)handbook.fca.org.uk · read 23 October 2026
  2. FCA — Payment Services and Electronic Money: Our Approach, May 2026 (version 8), chapter 20 (external site)fca.org.uk · read 23 October 2026
  3. FCA Policy Statement PS19/26 (Brexit — SCA-RTS), Appendix: UK exemption threshold values and reference fraud rates (external site)fca.org.uk · read 23 October 2026
  4. FCA Handbook Notice No 136, December 2025 (contactless limits replaced by a risk-based exemption from 19 March 2026) (external site)fca.org.uk · read 23 October 2026
  5. FCA statement — Deadline extension for Strong Customer Authentication (20 May 2021; e-commerce deadline 14 March 2022) (external site)fca.org.uk · read 23 October 2026
  6. The Payment Services Regulations 2017, regulation 77 (external site)legislation.gov.uk · read 23 October 2026
  7. Commission Delegated Regulation (EU) 2018/389 (RTS on SCA), article 16 — legislation.gov.uk copy showing the EU text (external site)legislation.gov.uk · read 23 October 2026
  8. Visa — PSD2 SCA Regulatory Guide, version 1.0, December 2020 (external site)visa.co.uk · read 23 October 2026
  9. Visa Core Rules and Visa Product and Service Rules, edition 18 April 2026 (Dispute Condition 10.4, invalid disputes) (external site)usa.visa.com · read 23 October 2026
  10. Mastercard Transaction Processing Rules, 10 June 2025 (rule 5.1.1, Mastercard Identity Check) (external site)mastercard.com · read 23 October 2026
  11. EMVCo — EMV 3-D Secure (external site)emvco.com · read 23 October 2026
  12. Council of the EU — Payment services: Council and Parliament agree to step up the fight against fraud and increase transparency (27 November 2025) (external site)consilium.europa.eu · read 23 October 2026

Keep reading

Rules and compliance

Website compliance checklist for card acceptance

What acquirers and card schemes expect on a merchant website before approval: legal pages, pricing, refunds, subscriptions, contact details, card marks.

9 min read11 sources