On this page · 11 sections
- What changed in 2026
- How a commercial VRP works under the UKPI rulebook
- Use cases: what Wave 1 covers and what it does not
- Pricing: the access fee and the July 2027 clock
- Who regulates what in 2027
- Build plan for billers and merchants
- Build plan for fintechs and PISPs
- Worked example: a UK energy supplier with 200,000 monthly payers
- Decision table: choose cVRP, Direct Debit or wait
- How eCorpIT can help
- References
Summary. The UK's first commercial variable recurring payments (cVRP) scheme is live. UK Payments Initiative Ltd (UKPI) launched it on 2 June 2026, published its scheme rulebook (version 3.0) that week and reported its first billers onboarding and live consumer payments. Wave 1 covers lower-risk payments: the Financial Conduct Authority (FCA) and Payment Systems Regulator (PSR) name regulated financial services, regulated utilities and local and central government, and UKPI adds charity donations and rail journeys. Payment initiation service providers (PISPs) pay banks a per-transaction access fee set by an independent UKPI pricing committee; the level is not published. The date that matters is July 2027. On 20 January 2026 the FCA and PSR said they would not prioritise a Competition Act 1998 investigation into that pricing, but only until the Data (Use and Access) Act 2025 framework is in place or July 2027, whichever comes first. The FCA plans to consult on a long-term open banking framework by the end of 2026, HM Treasury has committed to lay the open banking statutory instrument by then, and its consultation on a VRP right of access closed on 6 October 2026. We found neither document published by 13 November 2026, 230 days before 1 July 2027. Wave 1 billers can pilot now; ecommerce and subscriptions wait for Wave 2.
About this article. For payments and finance leads at UK billers, and for PISP and fintech engineering teams. We checked every date, rule and figure against FCA and PSR statements, HM Treasury's consultation, the Data (Use and Access) Act 2025, the Financial Services and Markets Bill, UKPI's rulebook and posts, and the Open Banking API standard, as they stood on 13 November 2026. This is general information, not legal or regulatory advice; scheme fees and rules can change, and no provider paid for inclusion. Researched with AI assistance and reviewed by our editorial team.
What changed in 2026
Each step below changes what a merchant or fintech can safely build. The timeline draws on the regulators' statements, UKPI's posts and HM Treasury's consultation page.
| Date | Event | Status |
|---|---|---|
| 2023 to 2025 | FCA and PSR gather evidence on extending VRPs to commercial use cases, starting under the Joint Regulatory Oversight Committee | Done |
| 9 April 2025 | Frontier publishes the Wave 1 commercial model analysis commissioned by UKPI | Done |
| 2025 | 31 firms come together to establish UKPI | Done |
| December 2025 | FCA and PSR delivery update expects first live UKPI payments in Q1 2026 | Superseded |
| 15 and 16 January 2026 | FCA and PSR write to the CMA; the CMA says it does not intend to take a different position | Done |
| 20 January 2026 | Joint FCA and PSR non-prioritisation statement on UKPI's access-fee pricing | Applies until the DUAA framework or July 2027 |
| 27 March 2026 | UKPI reports a controlled Stage 1 rollout with capped volumes | Done |
| 16 April 2026 | UKPI rulebook version 3.0 finalised | Done |
| 2 June 2026 | UKPI launches the scheme; the FCA welcomes it | Live |
| 14 July 2026 | HM Treasury opens its payment services consultation; Trustly and Hope Macy join UKPI as shareholders | Consultation closed 6 October 2026 |
| 11 September 2026 | UKPI reports 25 shareholders, including the nine largest UK banks and 16 PISPs | Done |
| 10 November 2026 | Commons second reading of the Financial Services and Markets Bill, which abolishes the PSR | Commons committee stage next |
| By end of 2026 | FCA consultation on the long-term open banking framework; DUAA statutory instrument | Announced; not seen by 13 November 2026 |
| July 2027 | Latest end of the FCA and PSR pricing comfort | Announced |
Shareholder and bill entries come from UKPI's posts and Parliament's bill record.
The market is already sizeable. The December 2025 delivery update recorded more than 16 million active open banking users, 53% year-on-year growth in open banking payments, and VRPs at 16% of open banking payments, mostly sweeping between a customer's own accounts. UKPI's launch release cites industry data of more than 37 million open banking payments a month, most of them one-off.
How a commercial VRP works under the UKPI rulebook
A cVRP is a standing permission. The payer sets up a mandate with a PISP and authenticates once with their bank (the account servicing payment service provider, or ASPSP). The PISP can then initiate a series of payments, with or without the payer present, as long as each stays within the consent parameters. The rulebook gives examples of those parameters: a maximum individual payment, a maximum amount per collection period and an expiry date. Payers can view and revoke mandates on an access dashboard at their bank.
The rulebook is a multilateral agreement (MLA) between UKPI as operator, ASPSP participants and payment initiation participants. Points that shape a build:
- Account coverage. A participating bank must enable cVRP mandates on all personal current accounts it offers for payment initiation. Extending to other account types, such as business accounts, is an opt-in by each bank, and an opt-in cannot be withdrawn.
- Mandated sweeping is separate. Sweeping VRPs mandated under the CMA's 2017 Order are not cVRP and sit outside the MLA, although the MLA can carry other sweeping payments.
- Scope is policed. A PISP cannot use the MLA, or its licence to banks' cVRP APIs, for out-of-scope use cases; those need a separate API licence with each bank. PISPs must carry out due diligence on billers, send UKPI a monthly list of new billers and their sectors, and stop any out-of-scope activity within 10 business days of notifying the operator, unless the operator agrees a phased plan.
- New use cases are opt-in. A use case added later applies only to banks that opt in, and UKPI records their status in a use-case capability register.
- Participation is not exclusive. PISPs and banks in UKPI remain free to join other cVRP schemes, a condition the FCA and PSR attached to their pricing statement.
The technical layer is the Open Banking Standard. Its VRP API profile, at version 4.0.1 on 13 November 2026, defines the consent and payment resources and lets banks add their own limits for non-sweeping VRPs, documented on their developer portals. A simplified flow:
1. PISP -> Bank : POST /domestic-vrp-consents (mandate request with control parameters)
2. Payer -> Bank : authenticate and approve the consent
3. PISP -> Bank : POST /domestic-vrp-consents/{ConsentId}/funds-confirmation (optional check)
4. PISP -> Bank : POST /domestic-vrps (each payment within the limits)
5. PISP -> Bank : GET /domestic-vrps/{DomesticVRPId}/payment-details (status, e.g. ACSC or RJCT)
For a biller, most of this sits behind the PISP's API. What you own is the mandate journey, the billing logic that decides amount and timing, and reconciliation.
Use cases: what Wave 1 covers and what it does not
The FCA and PSR statement describes Phase 1/Wave 1 as lower-risk use cases and lists three. UKPI's own materials list five. The difference matters because the regulators said their statement does not cover added use cases unless they agree.
| Use case | Named in FCA and PSR statement (20 January 2026) | Listed by UKPI | Examples |
|---|---|---|---|
| Regulated financial services | Yes | Yes | Loan repayments, insurance premiums |
| Regulated utilities | Yes | Yes | Energy and water bills |
| Local and central government | Yes | Yes | Council tax and other public-sector payments |
| Charity donations | Not named | Yes (June and September 2026) | Regular giving |
| Rail journeys | Not named | Yes (September 2026) | Rail fares |
| Ecommerce, subscriptions, retail, point of sale | No (Phase 2/Wave 2) | Next phase; purchase protection, disputes and pricing still being defined | Online shopping, streaming, gym memberships |
Charities and rail operators should ask their PISP whether the FCA and PSR have agreed to cover their use case; we found no public document extending the statement. Subscription businesses waiting for Wave 2 already have the UK subscription contracts rules to build for.
Wave 1 is modest by design. Frontier's modelling, which the FCA and PSR consider appropriate, puts Wave 1 uptake at about 1.2% of the addressable recurring-payments market by year 5 and about 3.4% by year 10. The prize UKPI is chasing is Wave 2: retail, ecommerce, subscriptions and, over time, point of sale.
Pricing: the access fee and the July 2027 clock
Each PISP pays an access fee to the payer's bank for every cVRP transaction. UKPI sets the fee centrally, and every participant agrees to it through the MLA. The FCA and PSR prioritisation statement lists the safeguards behind it, including:
- the fee is set by a pricing committee independent of shareholders and participants, which no participant may attend or observe;
- price-setting follows pricing principles agreed with the FCA and PSR, with controls on competitively sensitive information;
- no participant may get around the fee through other charges with an equivalent effect;
- any change to the fee, method or principles is notified to the FCA and PSR in advance, with reasons.
What is not published. The published rulebook defines the access fee and refers to a pricing schedule, which also covers the operator's own per-transaction scheme fees, but that schedule is not part of the published document, and we did not find the fee level on UKPI's website. What a merchant pays is set commercially by its PISP, which will price in the access fee, its own costs and margin. Treat any per-transaction figure you see in commentary as unconfirmed unless it comes from your provider's quote.
The July 2027 clock (Announced). The statement applies ahead of the legislative framework under the Data (Use and Access) Act 2025 (DUAA), or another legislative route, or until July 2027, whichever is earlier. If the framework is not in place by July 2027, the FCA and PSR will consider whether to issue a further non-prioritisation statement. The FCA, PSR and CMA can also change their position earlier if new information emerges. The statement is not a price approval: the regulators say they have reached no decision on whether the arrangement infringes competition law.
The statement also records the industry's preference: replace the Wave 1 model by the end of 2026 with a permanent centralised fixed-fee model covering Waves 1 and 2, underpinned by DUAA, with a fee that could vary with the nature or volume of transactions.
Three outcomes are plausible by mid-2027 (our reading, not a regulator's forecast).
| Scenario | Trigger | What it means for your pricing |
|---|---|---|
| Framework in place before July 2027 | DUAA statutory instrument made and FCA rules in force | Interim statement falls away; FCA pricing guardrails apply; fee may be reset |
| Framework late | No statutory instrument or FCA rules by July 2027 | FCA and PSR decide whether to issue a further statement; short-term uncertainty for contracts |
| Position revised | New information, or UKPI governance does not match the conditions | Possible change to the centralised fee model |
The legislative pieces are moving. HM Treasury's Modernising Payment Services Regulation consultation ran from 14 July to 6 October 2026, and on 13 November 2026 the Treasury was still analysing the responses. It proposes a new right of access for VRPs, under which a bank must let a PISP lodge a mandate for a series of payments, possibly limited to current account providers or banks above a certain size. Access under that right would not have to be free, except for sweeping. It also proposes FCA powers to set guardrails on scheme pricing, such as fair pricing and a transparent methodology, a power to require schemes to use centralised pricing, and possibly a power to cap prices. The government does not propose letting the FCA force banks to join commercial schemes.
Who regulates what in 2027
The FCA is the lead regulator for open banking and has worked jointly with the PSR on cVRP. That pairing is changing. The Financial Services and Markets Bill abolishes the PSR and moves payment systems regulation into the FCA; it had its Commons second reading on 10 November 2026 and goes to committee stage next. The abolition takes effect only from a date the Treasury sets by regulations once the bill is law.
Today, open banking rests on the Payment Services Regulations and the CMA's Retail Banking Market Investigation Order 2017. HM Treasury describes two tracks for the future framework: modernised payment services rules, and a statutory instrument under the DUAA, which the government has committed to lay by the end of 2026. Part 1 of the Act sets up smart data schemes, and its sections 14 to 17 cover the FCA and financial services interfaces. UKPI has argued publicly that the instrument should arrive early enough to avoid a gap between the interim position and the lasting regime.
On standards, the FCA is supporting industry work on a Future Entity to take over the standard-setting role of Open Banking Limited. UKPI's rulebook already defines the standard-setting body as the role OBL performs now, including any successor, so the technical baseline should carry over.
Status labels as of 13 November 2026:
- Announced: FCA consultation on the long-term open banking framework by the end of 2026, subject to the new legislation; FCA and PSR pricing comfort ending by July 2027 at the latest; FCA work with HM Treasury on open finance framework options by the end of 2027.
- Expected: DUAA statutory instrument for open banking.
- Before Parliament: abolition of the PSR.
- Proposed: new VRP right of access and FCA pricing guardrails (HM Treasury consultation, closed).
Build plan for billers and merchants
A biller does not join UKPI directly; it contracts with a PISP that is a payment initiation participant. The work is in product, billing and finance operations.
- Confirm eligibility. Map each payment stream to a Wave 1 use case and get your PISP to confirm it in writing.
- Choose a PISP. UKPI's 23 founding shareholders include payment and fintech firms such as Acquired, Atoa, Crezco, Fire, Fumopay, GoCardless, Modulr, Plaid, Token.io, TrueLayer, Wonderful and Yapily; Trustly and Hope Macy joined in July 2026. Shareholding is not the same as live participation, so ask which banks each provider can reach today for your account types.
- Design the mandate. Set consent parameters that fit your billing: a per-payment cap above your highest realistic bill, a period limit that covers one collection per cycle plus any catch-up you plan, and an expiry you will remember to renew. Caps set too tight turn into failed payments.
- Change billing logic. cVRP lets you choose amount and timing within limits, so decide rules for variable bills, partial payments and payer-chosen dates.
- Handle failure. Use the funds-confirmation check where your PISP supports it, design retries that respect the period limit, and make payment requests safe to repeat with idempotency keys.
- Reconcile. Map PISP payment statuses and references to invoices in your ledger.
- Run mandate lifecycle events. Payers can revoke from their bank's dashboard, so listen for revocation and expiry events. The rulebook requires a durable notice at least 48 hours before a mandate expires, and cancellation, after a 48-hour notice, of a mandate unused for 13 consecutive months; PISPs can delegate those notices to you.
- Agree disputes and refunds. The rulebook includes a disputes schedule between participants; agree with your PISP how payer complaints reach you and how refunds are made.
- Run alongside Direct Debit. Offer cVRP as a choice, not a forced migration, until coverage and pricing settle.
- Write the contract for July 2027. Include a re-pricing clause tied to regulatory change, a cap or notice period on fee increases, and a right to exit if the scheme's pricing model changes.
Build plan for fintechs and PISPs
For PISPs the work is heavier:
- sign the MLA and complete onboarding with UKPI as operator;
- implement the Open Banking VRP API profile against each participating bank, and track bank-specific limits published on developer portals;
- build biller due diligence, sector classification and the monthly biller report to UKPI;
- add controls that block out-of-scope use cases, and a playbook for stopping one within 10 business days;
- check the use-case capability register before creating mandates for any added use case;
- account for the per-transaction access fee in your merchant pricing, with headroom for a reset in 2027;
- design dispute handling to the MLA's disputes schedule;
- prepare a response to the FCA's long-term framework consultation when it is published.
Bank coverage is the commercial constraint. Industry participants told the regulators that, on average, at least 75% current account coverage is needed for cVRP to reach critical mass. Track which banks have gone live for which use cases before you promise merchants reach. If you also process euro payments, plan alongside the EU instant payments rules for payment institutions.
Worked example: a UK energy supplier with 200,000 monthly payers
The numbers below are assumptions to show the arithmetic, in pounds sterling.
A regional energy supplier has 200,000 customers paying monthly and offers cVRP alongside Direct Debit.
- Adoption. If 15% of customers switch in the first year, that is 200,000 × 0.15 = 30,000 payers.
- Volume. At 12 collections a year, 30,000 × 12 = 360,000 cVRP payments.
- Value. At an average bill of £95, 360,000 × £95 = £34.2 million collected by cVRP.
- Fee sensitivity. The access fee is not published and PISP pricing is commercial, so model it as a variable: every 1p of all-in cost per collection is 360,000 × £0.01 = £3,600 a year. Compare your PISP's quote with your current all-in cost per collection on the same basis, and with card costs if you also take cards (see our Stripe, Adyen and Checkout.com fee comparison).
- Mandate caps. If winter bills reach £220 and summer bills fall to £40, a per-payment cap of £300 and a monthly limit of £500 cover a winter peak plus one catch-up collection (£220 × 2 = £440). A £150 cap would fail every bill above it.
- Revocation exposure. If 1% of mandates are revoked each month, 30,000 × 0.01 = 300 customers a month need a prompt to set up a new mandate or return to Direct Debit.
- Time to July 2027. From 13 November 2026, 230 days remain to 1 July 2027. A pilot that starts in early 2027 gives about two quarters of data before the pricing position is revisited.
cVRP economics depend on two unknowns, the fee and adoption, and one known, your current collection cost. Get the known number right first.
Decision table: choose cVRP, Direct Debit or wait
| Choose | If |
|---|---|
| cVRP through UKPI now | Your payments fall in a Wave 1 use case, your payers mostly use personal current accounts, you want to vary amounts or dates within payer limits, and you can accept pricing that may change after July 2027 |
| cVRP as an option alongside Direct Debit | You have a large Direct Debit base and want evidence on adoption, failure and cost before switching defaults |
| Wait for Wave 2 | You sell ecommerce, subscriptions or retail goods, or your payers are mainly business accounts that banks have not opted in |
| A bilateral VRP agreement outside UKPI | You are a large PISP or biller with an out-of-scope use case and can negotiate a separate API licence with each bank |
| Sweeping VRP | You are moving money between a customer's own accounts, which is not commercial billing |
How eCorpIT can help
eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Our application development services team can integrate your chosen PISP's API into your billing platform and build the mandate, reconciliation and failure-handling flows that cVRP needs. Talk to us at /contact-us/.
Last updated: 13 November 2026.