Open Banking

Open banking is a set of rules and standards that let a customer share bank data, or start a payment, through a third party they have chosen. The bank keeps the account. The third party gets a narrow, short lived window into it, and only with clear consent. It all runs over secure APIs rather than screen scraping. So the bank knows exactly who is asking and what for. In practice an app can read a balance, list recent payments, or push a transfer straight from a bank account. It does not hold the login details.

The shift came from rules rather than the market. In the EU, the second Payment Services Directive created licensed roles for these firms and made banks open a route for them. In the UK, a competition ruling pushed the country's main banks to build one common standard. That is why the UK Open Banking API standards exist as a single public reference rather than nine different ones. Other markets have followed with their own models, some rule driven and some market led. So the term means slightly different things in different places, and the detail varies by market.

The Two Halves

Open banking splits into data and payments. On the data side, an account information firm reads balances and payment history with the customer's consent. That is what powers budget apps, lending checks and accounting tools. On the payment side, a payment initiation provider starts a transfer from the customer's account once they approve it in their own banking app. The two are licensed apart and carry different duties. Many firms hold both.

How A Payment Actually Runs

The shopper picks pay by bank at checkout and chooses their bank. They are handed to their own banking app. There they see the amount and the payee, and approve it. The bank then starts the transfer on a home market rail, often an instant one such as Faster Payments. The merchant gets a status back. The money follows on that rail rather than through card systems. Because the customer approves in their own app, the login stays with the bank.

What The Rules Ask Of Banks

Quite a lot, as it turns out. Under the standards that sit beneath the EU directive, banks must offer a route that lets licensed firms name themselves and talk securely. They must publish the technical detail free of charge. They must also give notice before changing it. Article 30 of those standards asks for a test facility ahead of launch as well. The aim is a route that works well, not one that merely exists. Where a bank's route performs poorly, the practical result is failed payments rather than a clean error.

Consent, Identity Checks And Trust

Consent is the whole basis of open banking, and it is time bound. A data permission is granted for a set purpose and period, and it has to be renewed. Payment approval happens once, per payment, in the bank's own app. It uses strong customer authentication. That design keeps credentials away from third parties. It also puts the bank's own login in front of the customer at the moment of payment. Some shoppers find that reassuring. Others find it slow. Both reactions are common, and they vary a lot by market.

Where It Helps A Business

Three places, mainly. Cost, since a bank transfer usually carries a different fee shape from a card payment. Certainty, because the money arrives as a push from the account rather than a promise that can be pulled back later. And reach, because it works for people with no card, or with a card that keeps failing. It also suits uses that cards handle awkwardly. Large one-off amounts, account top-ups, and paying a bill from a balance the customer can see. Open banking payments sit alongside cards rather than replacing them.

Limits Worth Knowing

There is no chargeback in the card sense. That cuts one risk and removes one customer safeguard. Refunds usually mean sending money back as a separate transfer, so the flow needs building rather than assuming. Coverage varies as well. Not every bank performs equally, and support for features such as repeat payments differs by market and by rulebook version. Disputes over goods sit outside the payment rail, which changes how a support team has to work. Knowing the Payment Services Directive helps, but local guidance still matters.

Practical Guidance

Start with a use case where the shape fits, such as a high value payment or an account top-up. Do not switch a whole checkout at once. Show the bank name early, since trust drives completion. Handle the return trip from the banking app with care, as that is where drop-off tends to cluster. Track success by bank, not just overall, because one poor performer can skew the picture. This guide to open banking and instant bank payments covers the detail. This piece on open banking in modern payment setups sets out where it fits.

‍