Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› PSD2
Cyber Security

PSD2

← Back to Glossary
By NHI Mgmt Group Updated November 2, 2026 Domain: Cyber Security

PSD2 is the European Union’s second Payment Services Directive. It establishes rules for payment service providers, including security expectations for customer authentication and fraud reduction. The framework applies to organisations operating in the European Economic Area and shapes how payment access, transaction approval, and liability are handled.

What PSD2 means for payment security

PSD2 matters because it turns payment security into a regulated control problem, not just a product feature. For banks, payment institutions, and third-party providers, the directive shapes how customers authenticate, how transactions are approved, and how fraud liability is assigned when access or payment flows are compromised.

That makes PSD2 both a compliance framework and an operational security baseline. It pushes organisations to treat authentication strength, transaction integrity, and access governance as part of the payment service itself, rather than as separate technical layers.

Strong customer authentication under PSD2

The best-known PSD2 security requirement is strong customer authentication, usually called SCA. In practice, this means payment flows often need multi-factor or otherwise strong, risk-aware authentication when a customer initiates access or approval that could create fraud exposure, especially where transaction approval is high value or remote.

PSD2 does not just ask for authentication in the abstract. It also influences how organisations handle exemptions, transaction risk analysis, dynamic linking, and evidence that a payment was authorised in the way the rules require. NHIMG’s PSD2/PSD3 Strong Customer Authentication Guide covers those rules in more depth, including the operational edge cases that matter in real payment environments.

Who PSD2 affects and where it applies

PSD2 applies across the European Economic Area and affects organisations that provide payment services, not only card issuers or consumer-facing banks. That includes firms that initiate payments, aggregate accounts, expose payment APIs, or rely on third-party access to customer accounts.

The practical effect is that PSD2 often reaches across internal teams and external providers. Authentication design, API access, audit evidence, payment approval logic, and fraud controls all need to line up with the same regulatory expectations, especially where open banking or delegated access is involved.

Why PSD2 changes payment architecture

PSD2 is not just about user login. It changes how a payment platform is designed, because access to account data and initiation of a payment become regulated trust events. That makes the security model closer to identity, authorisation, and transaction control than to ordinary web application access.

For that reason, PSD2 often drives architectural decisions around customer authentication, third-party access, transaction signing, fraud monitoring, and liability handling. NHIMG’s Financial Services Identity Security Guide places PSD2 in the wider banking and payments security context, alongside DORA, privileged access, and third-party risk.

How organisations usually prove PSD2 compliance

Compliance is typically demonstrated through a mix of policy, technical controls, and audit evidence. Organisations need to show that payment journeys are designed to satisfy authentication rules, that exemptions are applied consistently, and that the controls around approval and dispute handling are traceable.

In practice, this often means maintaining a clear inventory of payment flows, documenting where strong customer authentication is enforced or exempted, and aligning product, fraud, security, and compliance teams on the same control objectives. The challenge is not only meeting the rule once, but proving that the rule is operating consistently at scale.

Risk and Threat Considerations

PSD2 concentrates risk in the exact places attackers and fraudsters care about most, customer authentication, transaction approval, and account access. If those controls are weak or inconsistently applied, an organisation can face account takeover, unauthorised payments, exemption abuse, and disputes over whether a transaction was properly authorised.

Failure mechanism: Weak or bypassed authentication, poor transaction binding, and over-trusting third-party access can let an attacker or fraudster initiate or approve payments that appear legitimate to downstream systems.

Impact: The result can be direct financial loss, fraud reimbursement pressure, regulatory findings, and loss of trust in the payment service’s control environment.

Practitioner Guidance

Why practitioners should care: PSD2 should be treated as an operating model requirement, not a one-time compliance task. Product, security, fraud, and operations teams all need the same view of where authentication, exemption handling, and payment authorisation are enforced.

Governance implication: Assign clear ownership for SCA design, exception approval, and evidence retention so that payment controls are reviewable, auditable, and consistent across channels and third-party integrations.

Practitioner takeaway: The strongest PSD2 programmes are the ones that can explain not only what control is in place, but why a specific payment was allowed, challenged, or exempted.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org