3 Commercial VRP Platforms for Eligible UK Billers

Three commercial VRP providers currently serve eligible UK billers: Nuapay, Token.io, and GoCardless. Each connects to the UK’s open banking VRP rails through the CMA9 banks and selected challengers, but they differ on which banks they cover, how mandate management works, and what their APIs expose to developers. Eligibility starts with your biller category and your customers’ bank, not with choosing a provider.


What Is Commercial VRP and Who Is Actually Eligible Right Now?

Variable recurring payments (VRP) let a biller collect payments of varying amounts from a customer’s bank account under a single consent, without re-authenticating each time. The customer authorises a mandate through their bank’s app using Strong Customer Authentication, and the biller sweeps whatever amount falls within the agreed parameters.

The UK’s open banking VRP framework has two distinct tracks. Sweeping VRP, which lets customers move money between their own accounts, became mandatory for the CMA9 banks under the Competition and Markets Authority’s retail banking remedies. Commercial VRP, which covers third-party billers, is different. It is not mandated. Banks are participating voluntarily, and the rollout has been slow and sector-specific.

Wave 1 of commercial VRP in the UK targets utility providers, local authorities collecting council tax and rents, and financial services firms collecting loan repayments and insurance premiums. Some providers also list ecommerce merchants and subscription businesses, but biller eligibility is confirmed case by case with each bank, not assumed. If you sell SaaS subscriptions to UK consumers and your customers primarily bank with mid-tier challengers outside the CMA9, you are likely not eligible today.

The CMA9 banks are Barclays, HSBC, Lloyds Banking Group, NatWest Group, Santander UK, Danske Bank, Bank of Ireland UK, AIB Group UK, and Nationwide Building Society. Beyond these nine, coverage is provider-dependent. That distinction is where the three shortlisted providers diverge.


The FintechSpecs VRP Eligibility Stack: How to Read the Market Before Picking a Provider

Most VRP guides jump straight to provider comparisons. This one does not, because provider selection is the third decision, not the first. The FintechSpecs VRP Eligibility Stack names the three gates a UK biller must clear in sequence before a provider matters:

  1. Biller category gate: Does your sector fall within the current Wave 1 scope agreed between the banks and Open Banking Limited? Utilities, local government, financial services, and some regulated subscription categories pass. Generic SaaS or D2C ecommerce largely does not, yet.
  2. Bank coverage gate: Do your customers hold accounts at banks that have implemented commercial VRP? A biller in an eligible sector still cannot collect via VRP if their customers bank at an institution that has not gone live. Check the coverage table in the next section before shortlisting providers.
  3. Provider integration gate: Does the provider’s API suit your billing architecture? This is where mandate management depth, variable amount parameters, failure handling, and webhook reliability differ across Nuapay, Token.io, and GoCardless.

Running these in reverse order wastes months. A team that integrates a VRP provider before confirming their biller category is eligible with their customers’ specific banks will end up building a fallback to Bacs Direct Debit anyway.


Which UK Banks Support Commercial VRP Mandates Right Now?

Bank coverage is the most volatile variable in the commercial VRP market. Banks self-certify their VRP readiness to Open Banking Limited, and the list changes as institutions complete their implementations. The table below reflects publicly confirmed commercial VRP participation across the CMA9 and selected challengers. CMA9 live status is sourced from Open Banking Limited’s published conformance directory. Challenger bank statuses are sourced from individual provider documentation; verify directly with your shortlisted provider before relying on these entries.

BankCMA9 MemberCommercial VRP StatusNotes
BarclaysYesLiveRetail and business accounts. Source: OBL conformance directory.
HSBC / First DirectYesLiveIncludes First Direct. Source: OBL conformance directory.
Lloyds / Halifax / Bank of ScotlandYesLiveGroup-wide rollout. Source: OBL conformance directory.
NatWest / RBS / Ulster BankYesLiveIncludes NatWest Group brands. Source: OBL conformance directory.
Santander UKYesLivePersonal accounts confirmed. Source: OBL conformance directory.
NationwideYesLiveBuilding society accounts. Source: OBL conformance directory.
MonzoNoLive (voluntary)Confirmed via GoCardless and Token.io provider documentation.
Starling BankNoLive (voluntary)Confirmed via GoCardless and Token.io provider documentation.
Revolut UKNoPartial / in progressStatus varies by provider; confirm directly with your provider before assuming coverage.
Monzo BusinessNoNot confirmed for commercial VRPPersonal VRP only as of the most recent provider documentation reviewed. Confirm with your provider.

Confirm current status directly with your shortlisted provider before committing, and cross-reference against the OBL conformance directory. Bank conformance certification can lag behind actual go-live dates, and challenger bank support is the most likely column to change quarter over quarter.


Provider 1: GoCardless

GoCardless

GoCardless is the most widely deployed recurring bank payment processor in the UK, and its commercial VRP offering sits on top of an existing Direct Debit infrastructure that already covers millions of UK payers. For a biller already using GoCardless for Bacs Direct Debit, the VRP path is an extension of a known integration rather than a full rebuild.

What GoCardless VRP Covers

GoCardless routes commercial VRP mandates through the UK Open Banking infrastructure, with bank coverage across the CMA9 and confirmed voluntary participants including Monzo and Starling. The mandate management layer handles consent creation, parameter setting (amount caps and frequency limits), and payment initiation through a single API surface. Failure handling for VRP payments differs from Direct Debit: because VRP pulls from a confirmed real-time balance check at initiation, return rates are structurally lower than Bacs, though GoCardless does not publicly publish per-category return rate benchmarks.

Integration Depth and Developer Experience

The GoCardless API follows a resource-based REST model. Developers creating VRP mandates set a VrpConstraint object that defines the maximum single payment amount, the maximum total periodic amount, and the allowed date window. Webhooks notify the biller on mandate creation, payment initiation, and failure. The dashboard surfaces mandate status and payment history without custom tooling. For teams already familiar with the GoCardless Direct Debit integration, the conceptual model transfers directly.

Pricing

GoCardless does not publish a standard per-transaction rate specifically for VRP on their public pricing page. Pricing for commercial VRP is negotiated based on volume and biller category. Direct Debit pricing starts at 1% plus 20p per transaction, capped at £4, on the Standard plan according to their public pricing page, but VRP rates are confirmed separately. Request a quote if you are comparing total cost of ownership against Bacs.

Best Fit

GoCardless VRP suits billers already on the GoCardless stack who want to add open banking consent collection without changing payment operations infrastructure. It is also the strongest choice for billers with high Direct Debit return rates who want VRP’s real-time balance confirmation to cut failed payment costs. If you are evaluating the broader question of how recurring payment infrastructure affects SaaS billing, the comparison of dunning tools and failed payment recovery options is relevant context here.


Provider 2: Token.io

token.ai

Token.io positions itself as an open banking infrastructure layer rather than a payments brand. Its commercial VRP offering is API-first and aimed at billers, platforms, and financial institutions that want to build VRP collection into their own product rather than white-label a provider’s UX.

What Token.io VRP Covers

Token.io holds FCA authorisation as a Payment Initiation Service Provider (PISP) and Account Information Service Provider (AISP). Its VRP mandate API covers the CMA9 banks and maintains a conformance-tested bank connection list updated through Open Banking Limited’s directory. Token.io publishes a bank availability matrix in its developer documentation, which is more granular than what most competitors surface publicly.

Integration Depth and Developer Experience

Token.io’s VRP API exposes consent resource creation, payment initiation, and mandate management as separate endpoints, giving developers fine-grained control over each stage. This architecture suits platforms that need to store and replay mandate state independently of Token.io’s dashboard. The trade-off is a steeper integration lift than GoCardless: a team without prior open banking API experience should budget additional engineering time for the initial implementation. Token.io provides sandbox environments and postman collections through its developer portal.

Pricing

Token.io does not publish retail pricing for commercial VRP; contact their commercial team for a quote. Pricing is contract-based and varies by volume tier, biller sector, and whether the client is a direct biller or a platform reselling VRP collection to sub-merchants. Platforms building VRP into a broader payment infrastructure stack may find Token.io’s model more cost-effective at scale than per-transaction retail pricing, though this requires a volume commitment conversation.

Best Fit

Token.io suits engineering-led teams building VRP natively into a platform, particularly if the platform needs to white-label the consent flow under its own brand or embed VRP alongside account information retrieval. Financial institutions building a Bank on File product for their own customers are also a natural fit, given Token.io’s AISP authorisation running alongside its PISP capability.


Provider 3: Nuapay

GoCardless

Nuapay, operated by Sentenial and owned by EML Payments, is one of the longer-standing open banking payment processors in the UK and EU. Its commercial VRP product sits alongside a Direct Credit and Direct Debit suite, making it relevant for billers that need a single provider across multiple payment types and geographies.

What Nuapay VRP Covers

Nuapay’s VRP offering connects through the UK Open Banking infrastructure with coverage across the CMA9. Its differentiator relative to Token.io and GoCardless is the combined UK and SEPA footprint: a biller collecting in both sterling and euro can run VRP in the UK and SEPA Direct Debit in the eurozone through the same provider relationship and API. For UK billers with continental European operations, that reduces the number of payment provider contracts to manage. Nuapay is FCA authorised as a PISP.

Integration Depth and Developer Experience

Nuapay’s API documentation is available through its developer portal. The VRP mandate endpoints follow a similar resource model to the broader UK Open Banking standard, with Nuapay adding a reconciliation layer that ties VRP payment events to its existing transaction reporting. Teams that have integrated Nuapay for Direct Debit will find the VRP extension conceptually straightforward. The sandbox environment supports full mandate lifecycle testing.

Pricing

Nuapay does not publish VRP-specific transaction pricing publicly; contact their sales team for a quote. Their Direct Debit and payment initiation products follow a volume-based fee model, and VRP pricing is typically structured similarly. Specifying your biller category, estimated monthly transaction volume, and average payment value will give the sales team what they need to return a meaningful rate.

Best Fit

Nuapay is the strongest fit for UK billers that also collect in SEPA markets, or for financial institutions that want VRP alongside a broader payments stack from a single regulated provider. It is less suited to pure-play UK direct-to-consumer billers who have no need for multi-currency or multi-geography collection. For teams comparing open banking API providers more broadly, the open banking API options across the broader fintech stack gives useful framing.


Side-by-Side Comparison: Which Provider Fits Which Biller?

CriteriaGoCardlessToken.ioNuapay
CMA9 bank coverageFullFullFull
Monzo / Starling supportConfirmed (provider docs)Confirmed (provider docs)Not confirmed in public documentation; check directly with Nuapay
Multi-geography (SEPA)NoNoYes
Direct Debit fallbackYes (Bacs)No (pure API)Yes (SEPA + Bacs)
White-label consent flowLimitedYesPartial
AISP capability alongside VRPSeparate productYes (combined)Separate product
Public VRP pricingNo , contact for quoteNo , contact for quoteNo , contact for quote
Existing customer migration pathStrong (from DD)Build from scratchStrong (from DD)
Sandbox environmentYesYesYes
Best forExisting GoCardless billers, high DD return ratesPlatform builders, white-label VRPMulti-geography billers, SEPA + UK

What Is Bank on File and How Does It Relate to Commercial VRP?

Bank on File is the open banking equivalent of Card on File: a stored, reusable payment authorisation linked to a bank account rather than a card number. Under a commercial VRP mandate, the customer authenticates once through their bank’s SCA flow, and the resulting consent token acts as the Bank on File credential. The biller can then initiate payments within the agreed parameters without redirecting the customer to their bank again.

The practical difference from Bacs Direct Debit is speed and confirmation. Bacs settlement takes three working days. VRP payments settle in near-real-time through Faster Payments. The consent is also more granular than a Direct Debit mandate: the customer can see the exact amount caps and frequency limits they agreed to, inside their bank’s own app, and revoke access from there. That transparency reduces dispute rates, though none of the three providers above publish specific dispute rate comparisons against Direct Debit. The improvement in return rates is structural , VRP initiates against a real-time balance check rather than sending the payment blind , but no publicly available benchmark exists to quantify it on a per-category basis.

Bank on File is becoming a meaningful framing for billers who want to position recurring bank payments as a consumer-friendly alternative to card subscription storage. For businesses thinking through how recurring payment infrastructure connects to their broader billing stack, the payment infrastructure options for SaaS billing covers the wider decision space.


What Should a UK Biller Do Before Signing with a VRP Provider?

Four pre-contract steps matter more than any provider’s feature list. First, confirm your biller category is in scope with the specific banks your customers use, not just in scope with Open Banking Limited’s Wave 1 framework in the abstract. Category eligibility is a bilateral agreement between the biller (or its provider) and each bank. Second, audit your customer bank distribution. If more than 30% of your customers bank outside the CMA9 and confirmed voluntary participants, your effective addressable reach for VRP is limited until coverage expands.

Third, map the mandate management requirements. VRP mandates carry parameters including maximum single payment amount, maximum periodic total, and expiry date. If your billing model has variable amounts that might approach or exceed the cap you set at mandate creation, you need a re-consent flow. Build that into your product planning before you integrate. Fourth, test the sandbox thoroughly against your actual billing scenarios, including failed payment paths, mandate revocation by the customer, and edge cases where the payment amount hits the ceiling. All three providers above offer sandbox access before contract signature.

For teams building compliance and product readiness checks into this process, the fintech product and compliance readiness checklist is a useful parallel framework to run alongside provider evaluation.


Frequently Asked Questions

Can any UK subscription business use commercial VRP today?

No. Commercial VRP in the UK is live but limited to specific biller categories under Wave 1 eligibility, including utilities, local authority billing, and financial services. Generic SaaS subscriptions and D2C ecommerce do not automatically qualify. Eligibility is confirmed between the biller (or their VRP provider) and each individual bank, not by a central registry. Check your sector fit before engaging a provider.

What is the difference between sweeping VRP and commercial VRP?

Sweeping VRP covers a person moving money between their own accounts, for example from a current account to a savings account. It was mandated for the CMA9 banks under the Competition and Markets Authority’s remedies order. Commercial VRP covers third-party billers collecting from a customer’s account. It is not mandated. Banks participate voluntarily, which is why commercial VRP coverage is uneven across institutions and biller categories.

How does VRP compare to Bacs Direct Debit on failure rates?

VRP payments initiate against a real-time balance check, which structurally reduces the rate of returns caused by insufficient funds compared to Bacs, where the payment is sent blind and returned days later. None of the three providers above publish specific before-and-after failure rate data publicly. The improvement in practice depends on your customer base and payment timing, but the mechanism for reducing insufficient-funds returns is real and well-documented in Open Banking Limited’s technical standards.

Do customers have to re-authenticate for every VRP payment?

No. The VRP model requires one SCA authentication at mandate creation. Subsequent payments within the agreed parameters, the amount caps, frequency limits, and validity window, do not require the customer to re-authenticate. If a payment exceeds those parameters, a new consent is required. This single-auth model is what makes VRP operationally comparable to Card on File for recurring billing.

Which provider is best if I already use GoCardless for Direct Debit?

GoCardless. The mandate management concepts transfer directly, the API surfaces are consistent across Direct Debit and VRP products, and customer migration from a Bacs mandate to a VRP mandate is an in-platform workflow rather than a third-party integration project. Switching to Token.io or Nuapay purely for VRP while retaining GoCardless for Direct Debit creates unnecessary operational complexity.

Can I use VRP to replace SEPA Direct Debit for EU collections?

No, not through UK-focused VRP infrastructure. The UK commercial VRP framework runs on UK Open Banking rails and Faster Payments. SEPA collections require separate infrastructure. Nuapay is the only provider in this comparison that covers both, through its SEPA Direct Debit product alongside its UK VRP offering, but these are separate collection mechanisms, not a unified cross-border VRP product.

What does Bank on File mean in a VRP context?

Bank on File is shorthand for a stored, reusable VRP mandate. When a customer completes a VRP consent flow with their bank using SCA, the resulting authorisation acts like a Card on File credential but linked to a bank account. The biller can initiate payments within agreed parameters without sending the customer back to their bank. The customer retains visibility and revocation rights inside their bank app, which is a consumer protection feature distinguishing VRP from traditional Direct Debit.

How do I confirm which banks my provider actually covers?

Ask the provider for their current bank conformance list, then cross-reference it against Open Banking Limited’s published conformance directory at openbanking.org.uk. Provider documentation can lag behind actual bank go-lives, so check both sources. Additionally, run a quick analysis of your existing customer payment data to identify which banks appear most frequently, then confirm those specific institutions are covered before signing a contract.


The Practical Picture for Wave 1 Billers

Commercial VRP in the UK is a genuinely useful mechanism for the billers it covers, but the eligibility boundary is real and narrow. A utility company or regulated financial services firm collecting from customers across the CMA9 banks has a clear path to lower-cost, faster-settling recurring collections with better customer transparency than Bacs. A B2B SaaS firm billing UK customers monthly does not have that path yet, and no provider can manufacture eligibility that the banks have not confirmed.

The three commercial variable recurring payments providers UK billers are choosing between each solve a distinct integration profile. GoCardless minimises disruption for teams already on its stack. Token.io gives platform builders the most control over the consent UX. Nuapay is the only option that solves for UK plus SEPA in a single provider relationship. None of them can expand your biller category eligibility or your customers’ bank coverage. Those are upstream variables.

The more productive question for Wave 1 billers is not which provider is objectively best, but which provider’s bank coverage most closely matches where your customers actually bank. Run that analysis against your payment data before shortlisting. It is a faster filter than any feature comparison, and it will almost certainly narrow the decision before the API documentation becomes relevant. For teams thinking about how payment infrastructure choices compound across a growing stack, the common fintech infrastructure mistakes that create long-term lock-in is worth reading before you sign any long-term provider contract.

Michael Carter
Michael Carter

Michael writes about fintech strategy and operations for FintechSpecs, covering pricing models, banking-as-a-service, payment infrastructure, and the tools fintech founders use to scale. He focuses on the decisions behind the stack, not just the stack itself.