Time for a Level Playing Field for Regulated UK Gambling Payments
Download Whitepaper
Compliance & Regulation

Open Banking

What Is Open Banking? Definition and How It Works

Definition

Open banking is a financial services framework in which banks and account-holding institutions are required or encouraged to provide licenced third parties with API access to customer account data and payment initiation capabilities, with customer consent, enabling new payment and financial service products built on bank account infrastructure.

How it works

Open banking in Europe is mandated by PSD2, which requires banks to expose standardised APIs to licenced third-party providers (TPPs). Two categories of TPP are defined: Account Information Service Providers (AISPs), which read account data with customer consent, and Payment Initiation Service Providers (PISPs), which initiate payments directly from customer bank accounts. Both require explicit customer authorisation before any data access or payment action.

A PISP-initiated open banking payment works as follows: the customer selects pay-by-bank at checkout, is redirected to their bank's interface (app or web), authenticates using their bank's standard authentication (which satisfies SCA), and authorises the payment. The PISP submits the payment instruction to the customer's bank via the open banking API; the bank executes the payment directly from the account.

Open banking payments bypass card network rails entirely. There is no card, no acquirer in the card-acceptance sense, no interchange fee, and no chargeback mechanism as defined by card scheme rules. Settlement is account-to-account, typically over domestic faster payment rails (UK Faster Payments, SEPA Instant). Settlement timing is faster than card payments in markets with instant payment infrastructure.

Open banking is at different maturity levels globally. The UK has the most developed ecosystem, with a dedicated regulatory body (Open Banking Limited) and high API quality across major banks. Europe is maturing under PSD2. The US has no mandated open banking framework; data sharing occurs through commercial agreements. Australia, Brazil (via PIX infrastructure), and other markets have national open banking initiatives at various stages.

Why it matters

Zero interchange is the core cost advantage: open banking payments carry no interchange fee and no scheme fee. For merchants with high card payment costs, particularly those with commercial card volumes or cross-border transactions, open banking payments can reduce payment acceptance costs materially.

No chargeback mechanism is also a risk trade-off: card payments give consumers a chargeback right enforced by the card scheme. Open banking payments have no equivalent, dispute resolution falls to the merchant's refund policy and any protections offered by the PISP. For merchants with elevated chargeback exposure, this changes the risk dynamic.

Conversion depends on bank API quality: the open banking payment experience is only as good as the bank redirect flow the customer goes through. Bank authentication UIs vary significantly in quality. In markets with mature open banking (UK), conversion on open banking payment flows is competitive with card. In markets with inconsistent bank API implementations, conversion is lower.

Open banking is not yet a global standard: the absence of a mandated open banking framework in the US means open banking payments cannot be offered to US cardholders in the same way as EEA customers. Global merchants need to plan open banking as a market-specific offering rather than a global checkout option.

With PXP

PXP supports open banking payment initiation for EEA and UK merchants through regulated PISP connections. Open banking payments via PXP settle over domestic faster payment rails, with consolidated reporting alongside card payment data in PXP's dashboard. PXP's open banking integration covers the major bank APIs in supported markets.

Talk to a payments specialist

Frequently asked questions

What is the difference between open banking data access and open banking payments?

Open banking data access (via AISPs) allows third parties to read account balance, transaction history, and account details with customer consent, used for affordability checks, account aggregation, and financial management tools. Open banking payments (via PISPs) allow third parties to initiate payment transactions from a customer's account with customer consent, used as an alternative to card payments at checkout. They are separate capabilities enabled by the same infrastructure.

Do open banking payments use card network rails?

No. Open banking payments are account-to-account transfers that go directly from the customer's bank to the merchant's account via domestic payment infrastructure (UK Faster Payments, SEPA Credit Transfer, SEPA Instant). They do not involve card networks, acquirers in the card sense, interchange, or scheme fees. This is both the cost advantage and the reason why card chargeback protections do not apply.

How do open banking payments satisfy SCA?

When a customer initiates an open banking payment, they are redirected to their bank's authentication interface, typically their mobile banking app or online banking. The bank applies its own SCA-compliant authentication (biometric, OTP, etc.) before authorising the payment instruction. This bank authentication satisfies SCA natively, without requiring the merchant to implement 3DS. The SCA obligation is fulfilled by the bank, not the merchant.

What are the main limitations of open banking payments for merchants?

Key limitations: geographic coverage is fragmented (strong in UK and some EEA markets, minimal in US); bank API quality and uptime varies significantly across institutions; no universal chargeback mechanism (disputes are handled through merchant refund policies and PISP processes); not suitable for recurring payments in the same way as card stored credentials; and customer recognition of pay-by-bank options is lower than card in most markets.