Open banking in 2026: which payment journey deserves a commercial proposition?

Open banking is no longer only a regulatory API story. The FCA reported more than 16 million users by the end of 2025, open-banking payments up 53% year on year and variable recurring payments representing 16% of open-banking transactions. In June 2026, it welcomed the UK Payments Initiative as a step towards commercial variable recurring payments, while a long-term regulatory framework remains under development. Those figures signal adoption, not a business case for every merchant or fintech. The make-money opportunity begins with one payment or data journey where consent, conversion, cost, failure and customer control can be measured. This reading shows how to turn that journey into a bounded proposition sprint, distinguish sweeping from emerging commercial VRP, and build a recurring optimisation service. It also explains how acquisition can target subscription businesses, lenders, savings providers and payment partners without claiming that an API automatically lowers cost, increases conversion or removes regulated responsibilities.

The 2026 opportunity combines mature account-information and one-off payment services with growing variable recurring payment use and the emerging UKPI commercial scheme. Businesses can explore better account connectivity, payment control and automated money movement, but availability, pricing, coverage and regulatory responsibilities still depend on the proposition and participating providers.

The decision should start with the customer journey, not an API catalogue. A merchant with failed subscription payments, a lender collecting flexible repayments and a savings app sweeping surplus funds need different permissions, safeguards and commercial models.

Sweeping uses variable recurring payments to move money between accounts held by the same customer within agreed parameters and was mandated for the CMA9. Commercial VRP extends the concept to recurring payments for goods or services under commercial arrangements. It is emerging rather than universally mandated, so firms must verify scheme access and bank coverage before promising launch.

Both rely on long-lived consent with agreed limits, but the economic relationship and risk differ. The proposition file should state payer, payee, payment purpose, amount parameters, end date, cancellation, dispute path and fallback method.

A valuable use case has visible friction and measurable economics: payment failures, slow account verification, expensive card processing, manual affordability evidence, weak savings automation or poor subscription control. The team should quantify the current journey before designing a replacement. Novelty is not a customer benefit and lower headline fees do not prove lower total cost.

The baseline combines initiation attempts, successful completion, abandonment, failure reasons, refunds, support contacts, fraud loss and provider fees. It also records customers who cannot or do not want to use open banking so the fallback remains part of the design.

A paid proposition sprint should choose one customer segment and journey, map providers and permissions, prototype consent and failure paths, model unit economics and issue a go, test or stop decision. It should avoid building production integrations before coverage, customer value, compliance ownership and a credible distribution route are understood.

The first purchase can run in two to four weeks using current payment data, interviews and a clickable journey. The partner names assumptions about bank coverage, access fees and conversion, then designs a controlled pilot rather than converting modelled potential into a promised result.

The consent journey should tell the customer which provider acts, what data or payment permission is granted, its limits and duration, how it can be changed or revoked, and what happens when a payment fails. Strong Customer Authentication and bank redirection must fit the journey without disguising the regulated parties or customer choice.

Testing should measure comprehension as well as completion. A shorter journey that leaves customers unsure about recurring authority may reduce durable adoption and increase support or disputes. Accessibility and fallback routes belong in the product acceptance criteria.

The business case should compare total economics per successful retained payment, including provider access, integration, reconciliation, customer support, failure, fraud and fallback. Open banking may reduce some payment costs or improve conversion in a particular journey, but those outcomes require a measured pilot and cannot be inferred from industry adoption alone.

Scenario ranges are more credible than one forecast. A pilot can set minimum completion, repeat-use and cost thresholds, with an explicit stop decision if the proposition simply shifts cost into operations or excludes a valuable customer group.

A healthy partnership defines regulated roles, API service, incident handling, data use, consent evidence, settlement, reconciliation, complaints, liability and exit. The merchant or fintech should understand which decisions it retains and which provider dependencies affect the customer promise. A badge or sandbox connection is not a production operating model.

Vendor selection should test current bank coverage, performance data and roadmap separately. The future framework and UKPI expansion may change the market, but contractual flexibility is safer than assuming one scheme becomes universal.

The strongest prospects have recurring payments, high card or failure cost, a customer-controlled savings or repayment use case, or an existing open-banking connection that is underperforming. Subscription firms, lenders, utilities, wealth and cash-management products may qualify, but only when transaction volume, authority and provider access make a pilot actionable.

Search captures active provider and VRP questions; payment partners and finance networks provide trust; account research can identify checkout change, payment hiring and recurring-revenue models. Telephone, email, events and targeted voicemail should test the current payment pain and pilot owner.

The recurring service should monitor bank coverage, consent completion, payment success, failure reasons, reconciliation, disputes, customer outcomes and provider changes. It earns a fee by improving a live journey and governing experiments. It must not guarantee savings, conversion or commercial-VRP availability across every bank and customer.

A monthly optimisation loop can compare cohorts and test one change at a time. Material rule, pricing or provider changes reopen the business case before the customer promise or acquisition budget expands.

The offer is ready when the partner can define one customer journey, access baseline payment evidence, map regulated dependencies and run a bounded pilot within capacity. GetFishNet’s free eligibility test checks the pain, proof, first purchase, distribution route and recurring economics before recommending channels or expansion.

The strategic story is growth through a better customer and payment decision, not open banking as decoration. If provider coverage or economics cannot be verified, the honest commercial result is a roadmap or stop decision—not a fabricated launch case.

Authorities cited: Financial Conduct Authority; Payment Systems Regulator; Competition and Markets Authority; Open Banking Limited. Dated references remain in the private source register.