Open Banking Payments: What's Actually Shipping in 2026

Open banking payment initiation has been "about to disrupt card payments" for eight years, and its progress sits squarely within the PSP and infrastructure transformation reshaping digital commerce. The actual data tells a more nuanced story: PISP volumes are real in specific use cases, meaningful in specific markets, and almost entirely absent from general e-commerce checkout. Understanding which use cases have crossed the adoption threshold — and why the others haven't — is more useful than another macro prediction about the card network's demise.

The Promise vs The Gap

Payment initiation can avoid card interchange, and an instant underlying rail can provide fast payment confirmation. The merchant still pays provider/service charges and incurs integration, reconciliation and refund costs. Absence of card-scheme chargebacks does not eliminate fraud, reimbursement or contractual dispute exposure; the UK has protections for eligible APP scam victims.

Checkout completion is an empirical question. Compare the actual stored-card and Pay by Bank journeys on the same device, bank, customer cohort and purchase context, including bank-app handoff, authentication and return to the merchant. No measured two-second card versus 30–60-second bank-payment benchmark is established here.

Additional screens or failed app handoffs can cause abandonment, but step count alone does not establish the conversion effect. Instrument each stage and measure completed orders, bank errors and customer support contacts. Do not treat every provider implementation as having an identical redirect path.

The commercial question is whether provider cost, coverage and observed completion suit the use case. Compare a bank-payment option with the payment methods customers actually use rather than assuming every saved basis point becomes margin.

UK — The Most Developed PISP Market

The UK has established open banking payment services. Market-level payment or user counts do not establish general e-commerce checkout share or a particular merchant's conversion. Use dated, clearly defined adoption figures and a provider pilot for the task you are evaluating.

Where it's working:

Utility and bill payments. Compare one-off Pay by Bank with Direct Debit on mandate needs, confirmation, account coverage, collection failure and refund handling. A one-off bill payment and an ongoing debit mandate solve different customer tasks; the useful question is when to offer each.

Gambling top-ups. The Gambling Commission's ban, effective 14 April 2020, concerns credit-card gambling payments. It does not establish a blanket debit-card prohibition. Pay by Bank may be evaluated alongside permitted funding methods, subject to the operator's gambling, customer-protection and payment-provider requirements.

HMRC tax payments. Government payment collection is a useful bill-pay context to assess. Compare the supported payment journey and actual provider charges; no universal processing saving or absence of completion concerns is established here.

For retail checkout, request merchant-specific completion and usage evidence by bank and device. A provider launch or a large retailer integration is not proof of a universal sub-5% share, a conversion ceiling or displacement of cards.

Variable Recurring Payments (VRP). Sweeping moves funds between accounts owned by the same person. Commercial VRP permits payments to businesses within customer-approved limits. Open Banking Limited confirms cVRP is live through UKPI as checked on 28 October 2026. That confirms a live scheme, not universal availability for subscription merchants: request enabled banks, eligible use cases, production access, fees and loss-allocation terms. No specific next-wave launch date is assumed here.

EU — Evaluate the Current Service, Not a Forecast

PSD2 payment initiation, bank interfaces and the underlying transfer rail are distinct parts of a merchant service. Test the provider's actual bank coverage, authentication, payment confirmation, error recovery and refund workflow in each target market. Do not infer reliable coverage across the EU from one country's adoption.

For legislative status and implementation dependencies, use the PSD3 and PSR operator checklist. A political agreement or forecast application date does not itself establish a live EU-wide VRP product, a particular API uptime entitlement or general merchant availability. Base an integration decision on the current service contract and production evidence rather than an assumed 2028 improvement.

Australia — CDR Action Initiation and PayTo

Australia's Consumer Data Right action-initiation policy and a live PayTo merchant service must be assessed separately. Legislative enablement alone does not prove payment initiation is operational through CDR for your accredited provider. Obtain the provider's actual production scope before treating it as available.

The more practically important development is PayTo — the New Payments Platform's (NPP) mandate framework. PayTo allows businesses to create customer-approved payment agreements with consumers, enabling NPP-backed debits that function like Direct Debit replacements. PayTo mandates are real-time, can be managed by consumers through their bank apps, and can be initiated by the merchant as variable amounts within consumer-approved limits.

PayTo is a direct competitor to card-on-file subscription billing for Australian merchants, with provider-specific fees. Early deployment is in utilities, subscriptions, and rent payments. Confirm enabled banks and account types with the provider; both customer coverage and merchant integration affect access. The merchant value proposition is clear for recurring billing — no card expiry, no card interchange, fast underlying-rail execution and consumer-managed consent, subject to provider workflow. Measure agreement setup completion and subsequent collection success separately.

Where Open Banking Payments Actually Win

Stripping out the hype, PISP and open banking payments deliver genuine merchant value in specific scenarios:

High-value B2B payments. A bank-payment option can be attractive when the avoided card fee exceeds provider, integration and operating costs. As an illustrative calculation, a $50,000 invoice at an assumed 1.5% card fee has a $750 card charge before bank-payment costs; it is not evidence of a universal $750 saving or zero B2B abandonment.

Regulated sectors with card restrictions. Gambling (UK), crypto exchanges (many issuers block crypto card purchases), and other regulated categories where card acceptance is restricted by issuers or regulators. Confirm the actual restriction and permitted alternatives; a credit-card restriction does not imply all card funding is unavailable.

Government and utility payments. Compare completion, accessible bank coverage, confirmation and collection costs; public-service journeys also need to work for customers.

Subscription and recurring billing with VRP. Evaluate commercial VRP only where your provider confirms the bank and merchant use case is enabled. Compare consent setup, revocation, insufficient-funds handling, collection limits and all-in charges with the existing recurring method.

Cash-preferred consumers. In markets with significant unbanked or card-averse populations, PISP can be an on-ramp — consumers who have bank accounts but no cards. Less relevant in UK/EU/AU; more relevant in emerging markets with open banking frameworks.

What Operators Should Actually Do

A useful integration candidate has supported bank coverage, a customer task that fits bank payment, and a credible cost advantage after implementation and operating overhead. Bill pay, account funding, B2B invoicing and supported recurring use cases are candidates for a pilot, not automatic winners.

For low-value or general retail checkout, use measured completion, customer demand and matched provider quotes. There is no universal £100 exclusion or £1,000 inclusion threshold. Retain alternative methods where coverage or conversion is weaker.

The integration complexity is real. PISP providers (TrueLayer, Plaid, GoCardless) have improved their developer experience significantly, but bank API reliability varies, error handling is complex, and refund workflows for PISP are less standardised than card refunds. Budget for meaningful engineering effort beyond the happy path.

Set a rollout gate using live provider eligibility, measured checkout completion, successful payment confirmation and tested refunds. Expand after the pilot demonstrates useful results; a forecast scheme wave or legal milestone is not a substitute for that evidence.

Open banking payments are real and growing. They're just not growing in the places the press coverage implied they would.