Variable Recurring Payments Explained for EU and UK Businesses

Subscription and usage billing breaks when every renewal needs a new card authorisation or a fixed direct debit that cannot match the invoice. Variable recurring payments (VRP) are a UK open-banking pattern where a customer consents once to repeat pulls from their bank account within agreed limits — so you can charge different amounts each period without sending them back to checkout. For EU euro-area businesses, the parallel is often SEPA Direct Debit plus an initial pay by bank setup, not a single EU-wide “VRP” label. This article explains what VRP is, where it works today, how it differs from cards and fixed mandates, and what to ask providers before you pilot.

Variable recurring payments (VRP): Repeat collection from a customer’s bank account after one consent, where each charge can differ in amount within limits they approve in their banking app — typically implemented via open banking in the UK, not as a universal EU product name.

What problem VRP solves for billing teams

Fixed direct debits work when the amount is predictable. They strain when:

• Usage or metered billing changes every month
• Insurance premiums adjust with risk
• Marketplaces settle variable seller fees
• B2B invoices differ by line items

Cards on file solve variability but bring interchange, expiry, and chargeback profiles some businesses want to reduce on eligible flows. VRP targets variable amounts on bank rails with customer authorisation in the banking channel — fewer card details stored, different economics on supported flows.

Trade-offs remain: bank coverage is not universal; customers must complete a consent journey; failed pulls still need dunning like any debit scheme.

How variable recurring payments work (UK pattern)

In the UK, VRP is implemented as a consent record between the customer, their bank, and a licensed third party you integrate with. A simplified flow:

1. Customer starts setup — from checkout, billing portal, or onboarding.
2. They authenticate at their bank — mobile app or online banking.
3. They approve limits — maximum per payment, periodic cap, payee, and duration where the bank UI supports it.
4. You store a consent token — not the card PAN; operational details depend on your provider.
5. You initiate pulls when billing runs — amount within agreed bounds; bank approves or declines.
6. Webhooks update your billing system — success, failure, revocation.

Strong customer authentication happens at setup; subsequent pulls follow scheme and bank rules. Your provider should document which banks support your segment (retail vs business) and which VRP types (e.g. sweeping between own accounts vs merchant collection).

The Open Banking Implementation Entity publishes UK implementation guidance; treat bank lists as live data, not a one-time PDF.

VRP vs SEPA Direct Debit vs cards on file

Dimension	UK VRP	SEPA Direct Debit (EU)	Card on file
Amount flexibility	Variable within consent limits	Fixed or scheme rules; amendments vary	Variable
Customer setup	Bank app consent	Mandate + creditor ID	Card entry
Typical rails	Open banking consent	SEPA Core / B2B schemes	Card networks
Disputes	Bank/scheme rules differ from cards	Direct debit guarantee model	Chargebacks
Coverage	Per UK bank	Per debtor bank in SEPA	Global cards

Euro-area teams usually combine account verification, first pay by bank payment, then SEPA Direct Debit for renewals — see open banking providers for recurring transactions for regional rails. Do not assume a UK VRP product slides into Germany or France without a different mandate story.

Sweeping vs commercial VRP

UK discourse often splits:

• Sweeping — moving money between a customer’s own accounts (e.g. savings sweep), narrower commercial use.
• Commercial VRP — collecting to a merchant or biller within consent limits; relevant for subscriptions and utilities.

Your product and bank support determine which type you can ship. Billing platforms need commercial VRP (or equivalent) for merchant collection — confirm with providers explicitly, not via generic “VRP enabled” badges.

What to validate with open banking providers

Before marketing variable billing on bank rails:

Check	Why it matters
Bank list for your segment	Retail vs business accounts differ
Consent parameters exposed	Max amount, frequency, expiry
Webhook events for pull outcomes	Billing must retry or dunning
Revocation handling	Customer cancels in bank app
Settlement and reporting	Finance reconciliation
Pilot corridor	One bank + one plan tier first

Run sandbox scenarios: setup, successful pull, insufficient funds, limit breach, revocation. Compare providers on the same script — see how to shortlist open banking providers.

Sensible rollout for variable billing

1. Confirm UK (or supported) revenue share — VRP only where banks and providers align.
2. Pick one variable product — e.g. usage tier or monthly insurance premium.
3. Keep card fallback until pull success rates are measured.
4. Align dunning — map bank failure codes to your subscription logic.
5. Expand banks — after ops signs off reconciliation.

For EU variable amounts without UK VRP, plan SEPA mandate amendments, separate authorisations, or hybrid models with your payments lead — not a forced UK playbook.

Relationship to bank on file

Bank on file means you store a funding account relationship after verification or first payment — then charge again on bank rails. VRP is one way to implement repeat variable pulls in the UK; SEPA DD is the common EU pattern. Compare storage, consent, and economics in bank on file vs card on file.

Frequently Asked Questions

What are variable recurring payments?

Variable recurring payments are repeat charges from a customer’s bank account where the amount can change within limits the customer agreed when setting up consent — commonly associated with UK open banking VRP.

Where are variable recurring payments available?

Commercial VRP is primarily a UK open-banking development with bank-by-bank support. The euro area typically uses SEPA Direct Debit and pay-by-bank setup rather than a single EU product called VRP.

How are VRP and SEPA Direct Debit different?

VRP (UK) uses open-banking consent for variable pulls within limits. SEPA Direct Debit uses mandate-based collection in the euro area with scheme rules on amendments and notifications.

Can VRP replace cards for subscriptions?

For some UK customers and flows, yes as a complement. Most businesses keep cards during pilot and measure involuntary churn, coverage, and ops cost before shifting mix.

What is sweeping VRP?

Sweeping usually means moving money between a customer’s own accounts under consent — distinct from merchant collection VRP. Confirm which type your provider supports.

Do customers need to re-authenticate every month?

Not for every pull if consent is valid and within limits; setup requires bank authentication. Revoked or expired consent needs a new setup journey.

How do I choose a provider for VRP?

Filter on UK bank coverage for your segment, commercial VRP support, webhooks, and pilot references — use recurring transactions provider criteria and provider matchmaking.

Is VRP the same as pay by bank?

Pay by bank is often the first customer-facing payment; VRP is the repeat pull mechanism after consent. Same ecosystem, different product step.

Conclusion

Variable recurring payments address variable amounts on bank rails with upfront customer consent — most mature today in the UK VRP model, while EU teams usually pair verification, pay by bank, and SEPA Direct Debit. Validate bank lists, consent limits, and webhooks before you promise usage billing without cards. Pilot one product corridor, keep fallback payment methods, and expand on measured pull success and reconciliation — not on generic “VRP ready” marketing.