Open Banking APIs in the EU and UK: PSD2, PSD3 and What Changes
The EU and the UK both run open banking on PSD2-era rules, but their access, API performance, pricing and fraud liability rules are diverging. Here is what fintechs must plan for.
Key takeaways
- EU and UK still share PSD2-era plumbing, but the UK has added performance reporting, commercial VRP pricing and mandatory fraud reimbursement
- PSD3 and the PSR reached a Council first-reading position in October 2026, so the EU timetable still runs behind the UK's live changes
- API performance transparency is asymmetric: the UK publishes ecosystem stats, the EU does not
- TPP revenue models are shifting, because UK commercial VRPs introduce a PISP-to-ASPSP fee that changes account-to-account unit economics
Two regimes, one job: letting third parties touch a bank account
In both the European Union and the United Kingdom, the legal right of a licensed third party to read someone else's bank data or move money from their account comes from the same source: the second Payment Services Directive, PSD2 (Directive (EU) 2015/2366). The UK implemented PSD2 into domestic law before leaving the EU and kept the substance afterwards, then layered its own competition remedies on top.
That shared origin is why the two markets still look similar on paper. Two roles do the work. An account information service provider (AISP) reads balances, transactions and standing orders with the customer's consent. A payment initiation service provider (PISP) triggers a credit transfer from the customer's account, either as a single immediate payment or under a recurring mandate.
The divergence now sits in four places: how access is enforced, how API performance is measured, how third parties earn (and pay for) access, and who carries fraud losses. Each of those is labelled by jurisdiction below.
EU: PSD2 in force, PSD3 and PSR in the endgame
What today's rules require
Under PSD2, banks that offer online accounts (account servicing payment service providers, ASPSPs) must give licensed providers access through a dedicated interface — typically an API — or via a customer-facing interface with a fallback. The technical detail lives in the RTS on strong customer authentication and common and secure communication, which has applied since 14 September 2019 (Commission Delegated Regulation (EU) 2018/389). Dedicated interfaces must offer the same level of availability and performance as the bank's own customer channel, and must not create obstacles to access.
The obstacle problem the EBA had to police
That "no obstacles" rule turned out to be the hardest part to supervise. In 2020 and again in February 2021, the European Banking Authority (EBA) set out what it considered obstacles, including forcing users to type IBANs manually, requiring more than one strong authentication for a single payment, and bloated consent journeys of roughly five to fifteen screens where the bank's own app took one to three (EBA opinion on obstacles to account access).
The EBA also refused to publish absolute performance benchmarks, on the grounds that the legal test is parity with each bank's own interface, which differs bank by bank (EBA working group note on interface performance). The practical effect: the EU has no single public league table of bank API quality comparable to what the UK publishes, and a provider's access experience varies hugely by member state and by bank.
Where PSD3 and the PSR actually stand in November 2026
The European Commission proposed the current package on 28 June 2023, splitting it into a directive (PSD3) and a directly applicable regulation (the Payment Services Regulation, PSR) (European Commission, payment services). The timeline since then has been long:
- April 2024: European Parliament adopts its first-reading position
- 13 June 2025: Council agrees its negotiating mandate; trilogues open 9 July 2025
- 27 November 2025: Parliament and Council reach provisional political agreement
- 5 May 2026: ECON approves the agreed text
- October 2026: Council adopts its first-reading position on the agreed texts (Council first-reading documents and statement of reasons; summary)
The next formal step is a plenary vote in Parliament, after which member states begin transposition work. The Council's own statement of reasons describes the agreed aims as tackling payment fraud, strengthening consumer protection, improving access to cash, tightening safeguarding of customer funds (including giving payment institutions better access to central bank settlement accounts), folding e-money institutions into the payment institution regime, and "enhancing open banking and updating licensing requirements". Until PSD3 and the PSR apply, PSD2 and the RTS remain the operative rules in the EU.
One EU rule is already binding and easier to plan around: the Instant Payments Regulation. Fee parity for euro instant payments applied from 9 January 2025, sending instant payments plus verification of payee obligations applied from 9 October 2025, and payment service providers outside the euro area face their own deadline in 2027 (European Commission timeline). That matters for open banking because faster rails change how much a payment-initiation product is worth. We covered the mechanics in EU Instant Payments Regulation: What Banks and Fintechs Must Change.
UK: performance stats, paid VRPs and hard fraud liability
The UK's open banking build-out started as a competition remedy rather than a payments rule. The CMA's retail banking market investigation order forced the nine largest banking groups (the CMA9) to fund and adopt a common API standard, delivered through the Open Banking Implementation Entity, now Open Banking Limited (OBL).
The transparency asymmetry
Only the CMA9 are obliged to report availability and performance statistics, and to have them published; other banks are merely encouraged to do so (OBL publication of statistics guidelines). That is a real limitation for anyone benchmarking bank quality: the public dashboard covers a minority of UK accounts.
The figures are still informative. For September 2026, OBL reported average API availability of 99.51%, an average API response time of 327 milliseconds, 99.52% successful calls, and 2,921.8 million successful calls during the month (OBL API performance statistics). In September 2026 OBL also announced that the ecosystem had passed one billion open banking payments (OBL insight). Ahead of that, the FCA and PSR reported over 16 million active users and 53% year-on-year growth in open banking payments during 2025, with variable recurring payments (VRPs) accounting for around 16% of those payments (FCA and PSR, commercial variable recurring payments: update on delivery, December 2025).
Commercial VRPs are the economics story
VRPs let a customer authorise recurring payments where amount or timing varies. So far they have been used mainly for "sweeping" between a customer's own accounts. Commercial VRPs (cVRPs) extend that to utilities, regulated financial services, and payments to local and central government.
Industry set up the UK Payments Initiative (UKPI) to run a scheme, with the first live payments expected in the first quarter of 2026, and the FCA and PSR published a prioritisation statement signalling they would not pursue Competition Act investigations into phase 1 pricing arrangements (FCA and PSR prioritisation statement). On pricing, UK Finance's industry proposal for e-commerce cVRPs is explicit: a multilateral, centrally set transaction fee, charged ad valorem as a percentage of transaction value, paid by the PISP and received by the customer's bank, with no discounts and no introductory period (UK Finance, Open Banking Payments commercial model, January 2026).
This is a structural difference from the EU, where access to the account data mandated by PSD2 is free of charge to providers. In the UK, payment initiation is moving towards a paid model with the bank on the receiving end, which changes the unit economics for large merchants comparing pay-by-bank with cards.
The rulebook behind all this is also changing. HM Treasury is expected to legislate in 2026 to give the FCA powers to set open banking rules under the Data (Use and Access) Act 2025, with the FCA intending to consult on a long-term regulatory framework (FCA and PSR update, December 2025).
Fraud liability: the UK moved first
Since 7 October 2024, UK payment firms must reimburse victims of authorised push payment (APP) fraud sent over Faster Payments and CHAPS, including payment initiation transactions. The maximum is £85,000 per claim, down from an originally published £415,000; the sending firm bears the cost but the receiving firm must fund 50%; firms may apply a claim excess of up to £100 (not against vulnerable consumers); claims must ordinarily be settled within five business days and can be made up to 13 months after the payment. The PSR estimated the cap would fully reimburse 99.8% of APP scam claims by volume and 90% by value (PSR consolidated policy statement PS25/5; PSR consumer guidance).
In the EU, PSD2 liability rules remain narrower. Unauthorised transactions must be refunded, generally by the end of the next business day, and the payer's liability is capped at €50 where the payment instrument was lost or stolen or used without authorisation, unless the customer acted fraudulently or with gross negligence (PSD2, Article 73). The EU package is intended to strengthen fraud defences, but responsibility sits with the payer's provider far more than in the UK's 50/50 APP model.
The comparison, side by side
| Dimension | EU | UK |
|---|---|---|
| Legal basis | PSD2 plus RTS on SCA and CSC; PSD3 and PSR agreed text pending final adoption | Retained PSD2 plus CMA order and OBL standard |
| Access obligation | Dedicated interface or customer interface with fallback; parity with own channel | Same PSD2 baseline, enforced through the CMA9 remedy and OBL standard |
| Performance transparency | Reported to national regulators; no ecosystem-wide public dataset | Monthly ecosystem statistics published by OBL, CMA9 only |
| Payment initiation economics | Mandated access free of charge to providers | Commercial VRP model proposes a PISP-to-ASPSP ad valorem fee |
| Fraud liability | €50 payer cap for unauthorised payments; refund next business day | Mandatory APP reimbursement, £85,000 cap, 50/50 cost split |
| Recurring payments | Payment initiation per transaction; no UK-style commercial VRP framework | Commercial VRPs rolling out from 2026 under UKPI |
What this means for fintechs building in both markets
Plan for two tracks, not one. The UK's changes are live or imminent — cVRP pricing, the Data (Use and Access) Act powers, APP reimbursement — while the EU's are legislative and will arrive through transposition with national variation. Product roadmaps, fraud models and pricing sheets need jurisdiction labels on every assumption.
Second, budget for API quality as a cost line, not a given. In the EU the parity rule makes it hard to prove a bank is underperforming, so providers need their own monitoring, retry logic and fallback planning. In the UK, public statistics only cover the CMA9, so the long tail of banks and e-money firms is invisible until you are live with them.
Third, revisit payment-initiation margins. If the PISP pays the bank a percentage fee per successful UK commercial VRP, then merchant pricing has to absorb a cost that does not exist on the EU leg of a pan-European checkout, and pay-by-bank's advantage over card interchange shrinks accordingly. We looked at the card side of that trade-off in Card Interchange Fees Explained: Who Pays and Why.
Fourth, fraud economics now differ enough to affect licensing strategy. A UK firm absorbing APP reimbursement claims carries a loss profile that an EU-only AISP or PISP does not, which pushes capital, insurance and monitoring costs in different directions. Providers that already run partner-bank models, as covered in Banking as a Service: How FinTechs Launch Without a Bank Licence, should check who contractually holds fraud liability across each market.
Risks and costs
- Regulatory timing risk: PSD3 and the PSR have cleared Council first reading but still need a Parliament vote and national transposition, so implementation dates and national gold-plating remain open. Building to a draft text is a real risk.
- API availability risk: 99.5% headline availability still means meaningful downtime across a month, and the UK data covers a limited set of banks. Screen-scraping fallbacks carry their own security, consent and reliability costs where they remain permissible.
- Pricing risk: the UK commercial VRP fee is set multilaterally by an operator and remains subject to competition-law scrutiny and possible revision; pricing built on today's assumptions may not hold.
- Fraud and liability risk: the UK's £85,000 reimbursement cap and 50/50 split create real losses for payment firms, while the EU's €50 cap leaves customers exposed to authorised push payment scams in most cases.
- Compliance and operating cost: OBL membership and directory costs, API certification, security standards, per-call infrastructure, consent monitoring and support are recurring costs for third-party providers, and they scale with the number of banks covered, not with revenue.
- Concentration risk: open banking access depends on a small number of large banks and, in the UK, on a standards body and scheme operator whose funding and governance model is itself being reformed.
Bottom line
The EU and UK open banking regimes still share a PSD2 chassis, but they are now diverging in ways that matter commercially. The UK has published performance data, is introducing a paid model for commercial variable recurring payments, and has shifted APP fraud losses onto payment firms. The EU is still finishing PSD3 and the PSR, keeps mandated data access free, and leaves authorised push payment scams largely with the customer.
For a fintech operating in both markets, the practical work is unglamorous: separate fraud and pricing assumptions per jurisdiction, your own API monitoring because public benchmarks are incomplete, and a roadmap that treats the UK's 2026 rulebook changes as certain and the EU's transposition timetable as not.
Follow the shortlist
Following payments, banking and market-infrastructure change? Our global ETF and stock research watchlist is tracked daily. Premium members get the full list, the reasoning behind every entry and updates when entries change.
See premium accessInformation and education only, not investment advice.
Related
Stablecoin Regulation Compared: EU MiCA vs the US GENIUS Act
How MiCA and the GENIUS Act differ on who may issue payment stablecoins, what must back them, how redemption works and where depeg risk still sits.
FinTechTokenised Deposits vs Stablecoins: How Bank-Issued Money Differs
Tokenised bank deposits and reserve-backed stablecoins both move value on programmable rails, but they differ in legal claim, deposit insurance, balance-sheet treatment and risk.
FinTechInstant Payments for Small Business: FedNow, RTP, Zelle Compared
How FedNow, RTP and Zelle differ for US small businesses on speed, settlement finality, limits and cost, plus which emerging options fit SME cash flow.