TL;DR
Open banking lets a customer give a regulated third party permission to read their bank data or start a payment from their account, through an API rather than a password handed to a screen-scraper. In the UK it runs on one mandated standard at the nine biggest banks. In the EU it runs on PSD2 with several competing API standards, and a replacement regime (PSD3 and a new Payment Services Regulation) is on its way. For a product team, the useful questions are: which of the three jobs (data, payments, recurring payments) are you doing, who holds the regulatory permission, and how much inconsistency between banks can your architecture absorb?
Why product teams should care now
Open banking has stopped being a regulatory experiment. The UK's Open Banking Limited (OBL) announced on 30 July 2026 that the CMA9 banks had passed more than one billion open banking payments and more than 100 billion API calls since launch. Its June 2026 figures show 2.81 billion API calls in a single month, 40.16 million payments and 18.81 million user connections, with an average API response time of 349 milliseconds (Open Banking Limited, 2026).
A caution on that last number: OBL reports "user connections", not unique people, because it cannot identify someone who uses more than one app or brand (Open Banking Limited, 2025). When you build a business case, quote it the way OBL does.
Most of that traffic is invisible to consumers. They see a "pay by bank" button, a budgeting app that shows all their accounts, or an affordability check that doesn't ask for three months of PDFs. The product team behind each of those had to answer the same questions this guide covers.
What an open banking API actually is
An open banking API is a standardised, permissioned interface that a bank (the account servicing payment service provider, or ASPSP) exposes so that an authorised third party can do one of two things on the customer's behalf:
- Read account information, such as balances and transactions. The regulated role is the account information service provider (AISP).
- Initiate a payment from the customer's account. The regulated role is the payment initiation service provider (PISP).
The customer's consent is central. The flow is almost always a redirect or app-to-app hop: your product sends the user to their bank, the bank authenticates them with strong customer authentication, the customer approves exactly what you asked for, and your product receives a token. You never see their banking credentials.
That token-based model is the real difference from screen scraping. Scraping stores a credential and impersonates the customer; open banking gives you a scoped, revocable permission that the customer can see and withdraw.
The two roles you need to understand
Whether you are a bank, a fintech, a retailer or a software company with a payments feature, you will sit in one of three positions:
- Regulated provider. You hold your own AISP or PISP permission (an authorisation or registration with the FCA in the UK, or with a national authority such as BaFin in Germany). You carry the regulatory obligations directly.
- Agent or customer of a regulated provider. You use a licensed aggregator or payment provider under their permission. This is the most common route for product teams, because you can ship without becoming a regulated entity, but you inherit their coverage, pricing and roadmap.
- Data holder. You are the bank or payment account provider and you must expose the APIs.
Your answer drives almost every later decision: timeline, compliance workload, engineering effort and who answers the phone when a bank's API goes down on a Friday afternoon.
The three jobs open banking does
Most product ideas collapse into one of three categories. It helps to pick the one you actually need.
1. Reading data (account information)
Typical uses: personal finance and budgeting, affordability and income checks for lending, accounting software feeds, account verification, and wealth dashboards that consolidate holdings across providers.
What you get depends on the bank and the permissions requested: usually account identifiers, balances and transaction history, with enriched or categorised data coming from your own or a vendor's processing layer. What you build on top (categorisation, cash-flow forecasting, risk scores) is where the product value sits.
2. Single payments (payment initiation)
Typical uses: checkout payments paid account-to-account, loan disbursement and repayment, top-ups, B2B invoice settlement, and refunds back to source accounts.
The attraction is that the customer authenticates in their own bank app and the payment is pushed, rather than pulled as with cards. For a product team, that changes the failure modes. There is no card scheme dispute process to lean on in the same way, so your own reconciliation, refund and customer-support flows must be sound. If you are still deciding how much of that ledger logic to own, our guide on build vs buy for payments ledgers in regulated fintechs covers the trade-offs.
3. Recurring payments (variable recurring payments)
Variable recurring payments (VRPs) let a customer authorise a standing consent with limits, so a provider can initiate payments within those limits without the customer approving every one. This is the open banking answer to direct debits and card-on-file.
UK status is worth knowing in some detail, because it is moving:
- According to The Payments Association, VRPs are just over 15% of open banking transactions in the UK. OBL's June 2026 breakdown lists 7.73 million sweeping VRPs (sVRPs) alongside 32.43 million single domestic payments (The Payments Association, 2026; OBL, 2026).
- Sweeping VRPs move money between a customer's own accounts. The next step, commercial VRPs (cVRPs), covers payments to businesses. The first cVRP was made in November 2025 by Tink with Visa, Kroo Bank and Utilita. A group of 31 firms, the UK Payments Initiative, will operate the scheme.
- The rollout is phased: Wave 1 targets low-risk use cases and Wave 2 targets e-commerce. Proposed fee structures for Wave 2 have been under discussion, and the FCA and the Payment Systems Regulator are expected to evaluate cVRP adoption at the end of 2026.
If your product depends on commercial VRPs for e-commerce checkout, treat that as "watch closely", not "build the business on it", until the scheme rules and fees are settled.
UK versus EU: one idea, two operating models
Product teams that expand from one side of the Channel to the other tend to discover that "open banking" means different things in practice.
| Dimension | United Kingdom | European Union |
|---|---|---|
| Legal basis | UK payments regulation derived from PSD2, plus a competition-law order that created the open banking standard | PSD2, soon to be replaced by PSD3 and the Payment Services Regulation |
| API standard | One mandated technical standard at the CMA9 banks | No single pan-European standard; Berlin Group NextGenPSD2, STET and others are used |
| Who must open up | The nine largest banks and building societies by current account volume under the mandate, with wider participation on a voluntary and regulatory basis | All payment account providers under PSD2 |
| Standard-setting body | OBL today; a "Future Entity" planned | Industry bodies and national choices |
| Recurring payments | VRP (sweeping live; commercial in phased rollout) | No equivalent pan-EU open banking VRP product |
Two notes on that table. The UK's coverage and the EU's differing standards come from regulators' and industry descriptions; a vendor blog we reviewed (Finexer, 2025) describes the same split, so treat the finer points (for example the share of EU banks using each standard) as unverified. And the table is a simplification; always check the current rules for the specific countries you serve.
What this means in practice
In the UK, one integration pattern gets you broad coverage at the largest banks, though real-world behaviour still varies by bank. In the EU, the same product needs to cope with more variation: different standards, different consent and authentication flows, and different quality levels. This is the single biggest reason many teams use an aggregator rather than integrating each bank directly. Our deeper engineering guide on handling inconsistent bank APIs in custom fintech platforms goes into the normalisation layer in detail.
For Germany specifically, BaFin supervises payment service providers, and German consumers' habits around direct debits and bank transfers shape which use cases land. Check with local counsel before assuming a UK-style "pay by bank" proposition will convert the same way.
What is changing: PSD3, the PSR and the UK's next steps
EU: PSD3 and the Payment Services Regulation
On 27 November 2025 the Council and Parliament announced a provisional agreement on a new Payment Services Regulation (PSR) and a revised Payment Services Directive (PSD3), replacing PSD2 and the E-Money Directive (Taylor Wessing, 2025). The points that matter most for open banking product teams, based on that summary and a later industry analysis (Worldline, 2026):
- Permission dashboards. Customers get a dashboard to monitor and manage the access permissions they have granted. Expect more customers to see, and revoke, your access. Design for consent that lasts and that can be withdrawn gracefully.
- Barriers to access. The PSR is set to include a list of prohibited obstacles to data access, and banks must give payment institutions access to payment accounts on a non-discriminatory basis.
- Dedicated interface obligation. Worldline reports that the obligation for ASPSPs to provide a dedicated data interface is removed. We could not confirm the practical consequences from primary text, so test your assumptions against the final regulation.
- Fraud and liability. PSPs must share fraud-related information and check that the payee's name and unique identifier match. A PSP without suitable anti-fraud mechanisms can be liable for the customer's losses.
- Timing. The sources we read disagree on the transition period (one says expected to be 21 months, another cites an 18-month transition and transposition), with application broadly around 2028. We could not confirm the final publication status of the texts at the time of writing, so check the Official Journal before locking a roadmap.
UK: a new standards body and more rule-making power
The FCA's feedback statement FS25/4 sets out the planned "Future Entity" for UK open banking: expected to be the primary standard-setting body for open banking APIs, subject to future legislation, run as a not-for-profit company limited by guarantee, with responsibilities that include common standards, performance monitoring, adherence checks, and directory and certification services. The FCA said it no longer planned to set up an interim entity (FCA, FS25/4). It is a planned body rather than one we can point to as established in the source we reviewed.
The Payments Association also notes that HM Treasury is expected to give the FCA new powers to set open banking rules in 2026. For a product team, the message is simple: more of the rulebook is moving from voluntary industry practice to formal regulation.
One thing that is easy to miss: authentication and reconfirmation
Open banking customers used to have to reconfirm their consent with the bank every 90 days. In the UK the FCA removed that bank-side requirement in 2021, citing friction and customer drop-off, and the burden of reconfirming moved towards the third-party provider (PYMNTS, 2021). Our source on the exact mechanism was partly paywalled, so confirm the current rules with your compliance adviser. The product lesson stands: consent has a lifecycle, and your UX for expiry, re-consent and revocation is part of your retention story.
How to choose your architecture
Direct integration versus an aggregator
| Factor | Direct bank integration | Aggregator or licensed partner |
|---|---|---|
| Regulatory status | You need your own permission | You usually operate under the partner's permission |
| Coverage | Only the banks you build | Many banks behind one API |
| Control over data and UX | High | Limited by the partner's design |
| Engineering load | High: each bank's quirks are yours | Lower for connectivity, but you still own your data model |
| Dependency risk | Bank APIs only | Bank APIs plus the aggregator |
| Best for | Banks, large payment firms, specialised needs | Most product teams validating or scaling a proposition |
Most teams should start with an aggregator, learn what their users need, and revisit when volume or control justifies more. That is a product decision as much as an engineering one.
The layers you will build regardless
Even with a partner, a robust open banking feature has recognisable layers:
- Consent and permissions service. Records what was asked, what was granted, when it expires and when it was revoked. Must tie into your privacy and audit obligations.
- Connector layer. Wraps each provider or bank API behind your own interface so you can swap vendors and handle outages.
- Normalisation layer. Maps differing field names, formats and quirks into your single internal model. This is where inconsistent bank behaviour is contained.
- Event and webhook handling. Payments are asynchronous. Your system must cope with pending, executed, failed and unknown states without double-processing.
- Reconciliation and ledger. Matches initiated payments to bank-confirmed credits, handles partial and late settlements, and produces the audit trail finance expects. See our piece on reconciliation automation for payment platforms.
- Observability and fallback. Per-bank success rates, latency, error taxonomies and a graceful degradation story when a bank is unavailable.
If you are building toward a regulated product, our guidance on API-first architecture for fintech startups and on scoping a regulated fintech MVP will help you sequence what to build first.
Security, privacy and resilience
Open banking data is some of the most sensitive data your product will ever handle. A few principles are non-negotiable:
- Collect the minimum. Request only the data scopes the feature needs. Broad scopes raise your breach impact and your consent-screen friction.
- Protect tokens like credentials. Store them encrypted, rotate them, and restrict access by service.
- Treat consent as a legal record. Keep immutable logs of consent events to answer customer and regulator questions.
- Plan for third-party failure. Banks and aggregators will have outages. In the UK and EU, regulators expect regulated firms to think about operational resilience, which we covered in operational resilience for fintech software under FCA, DORA and MAS.
- Handle personal data lawfully. In the UK and EU that means UK GDPR or GDPR obligations on top of payments rules. For a broader view of the stack, see data security architecture for fintech.
A practical checklist for product teams
Before you commit engineering time:
- Which job are you doing: data, one-off payments, or recurring payments?
- Will you be regulated directly, or work under a licensed partner? Who is liable for what?
- Which countries and which banks must you cover on day one? What is your coverage target in each?
- How will you measure bank-level success rates, and what will you tell customers when a bank fails?
- What does your consent UX look like on expiry, re-consent and revocation?
- How will you reconcile and refund? Who owns disputes?
- What happens to your roadmap if PSD3, the PSR or UK rule changes land earlier or later than planned?
- Do you have a clear data-retention and deletion policy for the data you pull?
Common mistakes
Treating the UK standard as the European standard. It isn't. Budget for variation if you serve EU customers.
Designing for the happy path. Redirect flows fail: users abandon at the bank, apps time out, consents expire. The unhappy paths decide your conversion.
Forgetting the money-movement back office. The API call is the easy part. Settlement, refunds and reconciliation are where finance teams lose time.
Building on a scheme that isn't live yet. Commercial VRP, for example, is still in phased rollout with fee details under discussion. Prototype if you like, but don't promise customers a launch date based on it.
Ignoring consent as a product surface. With permission dashboards coming in the EU, customers will see your access listed alongside everyone else's. Make your value obvious and your permissions proportionate.
Where Syslabs fits
Syslabs builds custom software for fintech and regulated businesses, including API integration, ledgers and reconciliation, and the data pipelines behind open banking features. If you are choosing between an aggregator and a direct build, or planning how to normalise bank behaviour across markets, we are happy to compare options with you. Have a look at our fintech work, our API development and integration service, and our personal finance and PFM SDK for what we cover. Pricing is scoped on a consultation, because it depends on your coverage, regulatory position and volumes.
Conclusion
Open banking is a mature, high-volume part of UK payments and a still-fragmenting but fast-changing one across the EU. The product teams that do well are rarely the ones with the cleverest API call. They are the ones that pick the right job to be done, choose a sensible regulatory and partner model, design consent as a feature, and build the unglamorous back office of reconciliation, refunds and resilience. Keep one eye on PSD3, the PSR and the UK's Future Entity, because the rules will keep moving.
If you are weighing up an open banking feature, a pay-by-bank flow or a data-driven lending product, we would be glad to talk it through. Book a meeting with Syslabs and the booking page will show times in your own time zone.
Sources
- Open Banking Limited (30 July 2026). Open Banking surpasses one billion payments and 100 billion API calls. https://www.openbanking.org.uk/news/open-banking-surpasses-one-billion-payments-and-100-billion-api-calls/
- Open Banking Limited (2 September 2025). 2 billion API calls and 15 million users: a landmark month for open banking in the UK. https://www.openbanking.org.uk/insights/2-billion-api-calls-and-15-million-users-a-landmark-month-for-open-banking-in-the-uk/
- FCA (2025). FS25/4: Design of the Future Entity for UK open banking. https://www.fca.org.uk/publications/feedback-statements/fs25-4-design-future-entity-open-banking/printable/print
- The Payments Association (16 March 2026). The state of open banking payments in the UK in 2026. https://thepaymentsassociation.org/article/the-state-of-open-banking-payments-in-the-uk-in-2026/
- Taylor Wessing (1 December 2025). EU lawmakers strike a deal on payments reforms. https://www.taylorwessing.com/en/insights-and-events/insights/2025/11/eu-lawmakers-strike-a-deal-on-payments-reforms
- Worldline (10 March 2026). The scope and timeline are locked in for PSD3 and PSR. https://worldline.com/en/home/main-navigation/resources/blogs/2026/the-scope-and-timeline-are-locked-in-for-psd3-and-psr-what-should-psps-know
- PYMNTS (2 December 2021). UK's FCA scraps 90-day reauthentication open banking rule. https://www.pymnts.com/news/banking/2021/fca-scraps-90-day-reauthentication-open-banking-rule/
- Finexer (12 May 2025). UK Open Banking vs EU standard (vendor blog; unverified claims flagged in text). https://blog.finexer.com/uk-open-banking-vs-eu-standard/



