WorldAML Blog · Regulatory Updates · 2025-03-08 · WorldAML Compliance Team

PSD2 and Open Banking: AML Obligations for Third-Party Providers

PSD2 opened payment markets to new entrants — but it also extended AML obligations to Account Information Service Providers (AISPs) and Payment Initiation Service Providers (PISPs). This guide explains what is required.

The EU's Second Payment Services Directive (PSD2) fundamentally reshaped the European payments landscape by mandating open access to bank account data and enabling third parties to initiate payments on behalf of customers. While PSD2's innovation goals are well-documented, its AML implications for the new category of Third-Party Providers (TPPs) — Account Information Service Providers (AISPs) and Payment Initiation Service Providers (PISPs) — are frequently overlooked. This guide sets out what PSD2 firms must do to meet their AML obligations.

PSD2 in Brief: What Changed

Implemented in January 2018, PSD2 required EU banks and payment account providers to open access to customer account data (with customer consent) via standardised Application Programming Interfaces (APIs). This gave rise to two new regulated payment service categories: AISPs, which aggregate and display account information from multiple banks, and PISPs, which initiate payments from customer bank accounts on behalf of merchants or users. Both categories require authorisation from a national competent authority under PSD2.

How PSD2 Intersects with AML Regulations

PSD2 itself does not override or replace AML obligations — it adds to them. Authorised payment institutions (PIs) and electronic money institutions (EMIs) operating under PSD2 are also subject to the EU's Anti-Money Laundering Directives (4AMLD/5AMLD/6AMLD) and their national transpositions. The AML obligations apply whenever a PSD2-licensed firm falls within the definition of an 'obliged entity' under the AMLD.

Important distinction: AISPs that only access account information and do not hold or move funds typically have lighter AML obligations. PISPs, which initiate payment transactions, are more likely to be classified as obliged entities under the AMLD and have full AML programme requirements.

AML Obligations for PISPs

Payment Initiation Service Providers sit squarely within the scope of EU AML obligations when they facilitate fund transfers. Key obligations include:

  • Customer Due Diligence (CDD) at onboarding — verify identity, screen for sanctions and PEPs
  • Ongoing transaction monitoring to detect unusual payment patterns
  • Suspicious Transaction Reporting (STR) to the national Financial Intelligence Unit (FIU)
  • Maintenance of a firm-wide risk assessment covering customer types, payment corridors, and product risk
  • Senior management approval for higher-risk customer relationships
  • Record-keeping for a minimum of 5 years post-transaction

The Strong Customer Authentication (SCA) and Fraud-AML Overlap

PSD2's Strong Customer Authentication (SCA) requirements — mandating multi-factor authentication for electronic payments — have a natural overlap with AML controls. SCA reduces the risk of unauthorised payment initiation, which is a prerequisite for many money mule schemes. However, SCA is a fraud prevention mechanism, not an AML control: it does not substitute for CDD, transaction monitoring, or SAR filing obligations. Compliance teams should ensure there is no confusion between the two frameworks in their programme design.

Open Banking AML Risk Factors

Open banking creates new money laundering typologies that traditional bank AML models were not designed to detect. Key risk factors include:

  • Layering via multiple AISPs: structured use of multiple account aggregators to obscure fund flows across banks
  • Rapid payment velocity: PISPs enabling high-frequency micro-transactions that individually fall below reporting thresholds (smurfing)
  • Cross-border payment corridors: PSD2 operates across 30+ EEA countries, creating complex multi-jurisdiction transaction chains
  • Synthetic identity fraud at onboarding: using stolen or fabricated identity data to open accounts exploited through open banking
  • Third-party payment abuse: directing payments through legitimate third-party PISP services to distance funds from predicate offences

Transaction Monitoring for Open Banking Providers

Conventional transaction monitoring rules were designed for bank accounts and card payments. Open banking providers often need to adapt or build new monitoring scenarios specific to their payment model. Relevant monitoring typologies include: rapid in-and-out transactions with no plausible commercial purpose; payments to counterparties in high-risk jurisdictions; multiple small payments to the same recipient just below reporting thresholds; and sudden changes in transaction volume or value inconsistent with a customer's profile.

WorldAML's Transaction Monitoring module supports custom rule-building, enabling open banking firms to deploy typology-specific scenarios alongside standard AML monitoring frameworks. Review the full capabilities at /platform/transaction-monitoring.

PSR 2017 and the Travel Rule for PISPs

In the UK, the Payment Services Regulations 2017 (PSR 2017) transpose PSD2 into domestic law and are supervised by the Financial Conduct Authority (FCA). UK PISPs are also subject to the FATF Travel Rule (implemented in the UK under the Wire Transfer (Information on the Payer) Regulations 2017), which requires that payment firms include payer and payee information in electronic fund transfers above EUR 1,000. With the EU's Transfer of Funds Regulation (TFR) extended to crypto-asset transfers under MiCA, open banking and crypto convergence is creating new compliance complexity for multi-product PSD2 firms.

PSD3 and Future AML Requirements

The European Commission published its PSD3 proposal in June 2023, alongside a new Payment Services Regulation (PSR). PSD3 strengthens fraud liability rules, refines open banking API standards, and aligns more closely with the forthcoming EU AML Regulation (AMLR) — which will establish a single EU AML rulebook directly applicable across member states without national transposition. PSD2-licenced firms should begin gap analysis against the AMLR now, as the new framework is expected to apply from 2027.

Building an AML Programme for a PSD2 Firm

  1. Determine your regulatory perimeter: are you an AISP, PISP, or both? Are you an obliged entity under the AMLD?
  2. Conduct a firm-wide risk assessment tailored to open banking payment typologies
  3. Implement CDD workflows with automated identity verification and sanctions/PEP screening at onboarding
  4. Deploy transaction monitoring with scenarios specific to your payment flows and customer behaviour
  5. Establish an STR filing process with your national FIU
  6. Train all relevant staff on PSD2 and AML obligations at least annually
  7. Appoint a qualified Money Laundering Reporting Officer (MLRO) with direct access to the board
  8. Review and update your risk assessment and monitoring rules at least annually

WorldAML provides a complete compliance stack for PSD2 firms: KYC onboarding, automated sanctions and PEP screening, real-time transaction monitoring, and regulatory reporting — all accessible via API for seamless integration into your payment platform. See /platform/suite for the full module overview.

More compliance articles · Talk to our team