Variable Recurring Payments
VRP consents for recurring payments within agreed limits.
Variable Recurring Payments (VRP)
VRP consents allow a third-party payment service provider (PISP) to make multiple payments from a user's account within agreed parameters, without requiring individual authorisation for each payment.
Use Cases
- Sweeping — automatically moving funds between a user's own accounts (e.g. from a current account to a savings account)
- Subscription payments — recurring charges within agreed limits, replacing card-on-file
- Smart savings — automated transfers based on rules (e.g. round-up savings)
- Bill payments — variable-amount payments to the same payee (e.g. utility bills)
How VRP Differs from Regular Payments
With a regular Transaction Request, the user must authorise each individual payment. With VRP, the user authorises a consent that defines the rules (maximum amounts, frequency, payee) and the PISP can then initiate multiple payments within those rules without further user interaction.
Creating a VRP Consent
A VRP consent request includes limits that define the maximum amount and frequency of payments(see in API Explorer):
POST https://YOUR_OBP_HOST/obp/v5.1.0/consumer/vrp-consent-requests
{
"account_routing": {
"scheme": "AccountId",
"address": "ACCOUNT_ID"
},
"from_account": {
"bank_routing": {
"scheme": "BankId",
"address": "BANK_ID"
},
"account_routing": {
"scheme": "AccountId",
"address": "SOURCE_ACCOUNT_ID"
}
},
"to_account": {
"bank_routing": {
"scheme": "BankId",
"address": "TARGET_BANK_ID"
},
"account_routing": {
"scheme": "AccountId",
"address": "TARGET_ACCOUNT_ID"
}
},
"max_single_amount": 100,
"max_monthly_amount": 500,
"max_number_of_monthly_transactions": 10,
"valid_from": "2026-01-01T00:00:00Z",
"valid_to": "2026-12-31T23:59:59Z"
}Consent Parameters
| Parameter | Description |
|---|---|
max_single_amount | Maximum amount for any single payment |
max_monthly_amount | Maximum total amount that can be paid in a calendar month |
max_number_of_monthly_transactions | Maximum number of payments per month |
valid_from / valid_to | Time window during which the consent is active |
from_account | The user's account to debit |
to_account | The payee's account to credit |
VRP Consent Lifecycle
- The PISP creates a VRP consent request with the payment parameters
- The user reviews the limits (max single amount, monthly amount, frequency) and authorises(see in API Explorer)
- Once active, the PISP can initiate payments within the agreed limits without further user interaction
- Each payment is validated against the consent limits before execution
- The user can revoke the consent at any time from My Consents
Making Payments Under a VRP Consent
Once a VRP consent is active, the PISP initiates payments by including the consent JWT in the request header(see in API Explorer):
POST https://YOUR_OBP_HOST/obp/v6.0.0/banks/BANK_ID/accounts/ACCOUNT_ID/VIEW_ID/transaction-request-types/ACCOUNT/transaction-requests
Consent-JWT: YOUR_VRP_CONSENT_JWT
{
"to": {
"bank_id": "TARGET_BANK_ID",
"account_id": "TARGET_ACCOUNT_ID"
},
"value": {
"currency": "EUR",
"amount": "25.00"
},
"description": "VRP payment"
}The API validates each payment against the consent limits. If the payment exceeds the max_single_amount, would cause the monthly total to exceed max_monthly_amount, or would exceed the max_number_of_monthly_transactions, the request is rejected.
Revoking a VRP Consent
Users can revoke a VRP consent at any time. Once revoked, no further payments can be made under that consent. Outstanding payments are not affected.
Users can manage their consents in the portal under My Consents.
Related
- Consents — general consent mechanism and account access consents
- Transaction Requests — making individual payments
- Account Access — how Views control data access
- My Consents — manage your active consents
- VRP endpoints in the API Explorer
- Consent endpoints in the API Explorer