Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Are PSD2 and Strong Customer Authentication?

PSD2 is the European payment services framework that introduced strong customer authentication, a requirement for two independent factors and dynamic linking on remote payments.

Illustration for the cybersecurity term PSD2 and Strong Customer Authentication
Home / Blog / Cybersecurity Terms / What Are PSD2 and Strong Customer Authentication?
17 November 2026

What Are PSD2 and Strong Customer Authentication?

What Are PSD2 and Strong Customer Authentication?

The second Payment Services Directive, invariably called PSD2, reshaped European payments in two ways. It opened bank account data and payment initiation to licensed third parties, which produced open banking, and it required strong customer authentication for electronic payments and for access to payment accounts. The second of those is the part that touches almost every online business, because it is why customers are challenged when they pay.

Strong customer authentication, abbreviated to SCA, means authentication based on at least two independent elements drawn from different categories, in a way that protects the confidentiality of the data being authenticated. The categories are knowledge, something only the user knows; possession, something only the user has; and inherence, something the user is.

Independence Is the Hard Part

Two factors from the same category do not qualify, so a password plus a memorable word is not SCA. More subtly, the elements must be independent in the sense that compromise of one does not compromise another. A one-time code sent by text to the same phone that is being used to make the payment is a weak form of possession for exactly this reason, which is why banks have moved to in-app approval with device binding and cryptographic keys held in secure hardware.

For remote transactions there is a further requirement called dynamic linking. The authentication code must be specific to the amount and the payee, both must be shown to the customer during approval, and any change to either must invalidate the code. This is the control that defeats malware or an attacker who captures an approval and attempts to reuse it against a different transfer, and it is the requirement most often implemented poorly.

The Exemptions

Blanket challenges would destroy conversion, so the rules provide exemptions that the payment service provider may apply at its own risk:

Exemptions move liability. A transaction authenticated with SCA generally shifts fraud liability to the issuer under scheme rules; one on which an exemption was claimed generally does not, so the decision is commercial as well as technical.

Where the UK Rules Now Live

PSD2 was implemented in Britain through the Payment Services Regulations 2017. After the UK left the European Union, the technical standards on SCA and common secure communication were brought into the FCA’s own rulebook, and the FCA has amended them since, so the UK and EU positions have diverged in detail even though the principles match.

Two dates matter for the UK. Enforcement for e-commerce card transactions ran to a final deadline of 14 March 2022, later than the European timetable, after the FCA gave the industry additional time. And in 2021 the FCA removed the requirement for customers to reauthenticate every ninety days when a third party accessed their account data, replacing it with a confirmation of consent given to the third party instead, which materially improved the usability of account information services.

Implementation Advice That Survives Contact with Reality

  1. Pass the full data set to 3-D Secure 2. Issuers approve without challenge far more often when they receive complete device, address, and history information, so richer data means less friction, not more.
  2. Use delegated authentication and exemptions deliberately, with the liability consequence understood by the commercial team rather than discovered in a chargeback review.
  3. Treat dynamic linking as a user interface problem as well as a cryptographic one. If the customer cannot see the amount and payee on the approval screen, the control has failed regardless of what the protocol does.
  4. Handle the accessibility cases. Customers without a smartphone, without reliable mobile coverage, or with impairments that make biometrics unusable still have a right to pay, and card readers or callback processes have to exist.
  5. Instrument the funnel. Measure abandonment at the challenge step by issuer and by method; the difference between a good and a poor implementation is usually several percentage points of revenue.

Turkey arrived at a similar place by a different route: the banking regulator requires two-factor authentication for banking transactions under its information systems regulation, and the central bank’s payment services regulation governs payment and electronic money institutions, so a UK firm operating there meets comparable expectations under local rules rather than under PSD2 itself.

Our web application security services test authentication and payment journeys against the implementation failures that leave SCA technically present and practically bypassable.

FAQ – Frequently Asked Questions

Does PSD2 Still Apply in the UK?

Its substance does, through domestic law. PSD2 was implemented by the Payment Services Regulations 2017, which remain in force, and the technical standards on strong customer authentication now sit in the FCA Handbook rather than in retained EU law. The FCA has amended them since, so the UK and EU regimes are closely related but no longer identical in detail.

Is an SMS Code a Valid Possession Factor?

It is accepted in practice but widely regarded as the weakest option. A code delivered by text is vulnerable to number porting fraud, SS7 interception, and malware reading notifications on the same device used for the payment. Regulators have not banned it, and firms have steadily moved to app-based approval with device binding and keys held in secure hardware instead.

What Is Dynamic Linking?

A requirement that the authentication code for a remote payment is tied to the specific amount and payee, that both are displayed to the customer at the moment of approval, and that any change invalidates the code. It prevents an approval captured by malware or an attacker from being reused for a different transfer, and it is the single most important technical element of strong customer authentication.

Who Decides Whether an Exemption Applies?

The payment service provider, usually the issuer, though a merchant or acquirer can request one. The issuer may still challenge the transaction. Because an exempted transaction generally leaves fraud liability with the merchant or acquirer rather than shifting it to the issuer, the decision should be made with the commercial consequence understood rather than purely as a conversion optimisation.

Related Terms

You May Be Interested In These

What Is Full Disk Encryption?

Cybersecurity Terms

17 November 2026

What Is Full Disk Encryption?

Read More
What Is Promotion Abuse?

Cybersecurity Terms

17 November 2026

What Is Promotion Abuse?

Read More
What Is XXE Injection?

Cybersecurity Terms

17 November 2026

What Is XXE Injection?

Read More