Variable Recurring Payments (VRP) is a UK Open Banking payment-initiation standard that lets a customer authorize a trusted third party, via a single long-lived consent, to initiate a series of payments of varying amounts within agreed limits. It extends the OBIE Payment Initiation API beyond one-off payments to consented, parameter-bounded recurring payments — first for sweeping between a customer's own accounts, and increasingly for commercial "me-to-business" use cases as an account-to-account alternative to card-on-file and direct debit.
Variable Recurring Payments
Variable Recurring Payments (VRP) is the part of the UK Open Banking standard that turns payment initiation from a one-off action into a consented, bounded, ongoing capability. With a single long-lived consent, a customer authorizes a trusted provider to initiate a series of payments of varying amounts within limits they set — a maximum per payment, a periodic cap, an expiry — without re-authenticating each time.
- A long-lived, parameter-bounded consent - Unlike a single PIS payment, one VRP consent covers many future payments, each validated against the agreed constraints, giving the user control without the friction of per-payment strong customer authentication.
- Sweeping first, commerce next - Mandated first for sweeping (moving money between a customer’s own accounts), VRP is expanding into commercial VRP as an account-to-account rival to card-on-file, subscriptions, and direct debit — the retail payments frontier of UK open banking.
- The action surface an agent needs - VRP is precisely the write capability that lets a third party — or an autonomous agent — do something under standing, revocable authority, rather than merely read an account.
VRP is the reason the UK sector looks different from read-only regimes when I score it: because the mandate includes real write surfaces, idempotency keys and action-class semantics appear across UK banks where Australia’s CDR, a data-sharing regime, has none. For anyone modeling agentic finance, VRP is the most important payment primitive in open banking — a standing, bounded authorization is exactly the shape of permission an agent needs to move money safely, and the UK is the market that standardized it first.
Referenced in API Evangelist papers
This standard shows up in my published research. These reports read the machine-readable evidence provider by provider — and put this standard in the context of a real sector.
The State of UK Banking APIs
The UK's write/action surface — the payment-initiation capability that let UK agents act on accounts, giving the sector idempotency coverage read-only regimes lack.
Governed by these regulations
A standard is the machine-readable contract; a regulation is the law that requires it. These are the regulations that mandate or drive this standard, catalogued at regulations.apievangelist.com.
Revised Payment Services Directive (PSD2)
The directive whose payment-initiation mandate this UK Open Banking capability extends.
