Skip to main content
New

This website is a design preview. Product capabilities shown are demonstrated in the IronLedge prototype console with simulated data. See the product tour

IronLedge

Variable Recurring PaymentsBeta

Recurring payments the customer can see and stop.

Variable Recurring Payments let a customer give a mandate with clear limits per payment and per period. The mandate, the amounts used and its status are visible to both sides.

What it does

Capabilities

Each item says whether it is shown in the prototype console today or is planned. Planned items are not available.

How it works

Four steps

  1. 01

    Agree the mandate

    State the limits and what the mandate is for.

  2. 02

    Customer authorises

    The customer approves the mandate at their bank.

  3. 03

    Collect within limits

    Take payments up to the agreed limits.

  4. 04

    Review or revoke

    Usage and status stay visible until the mandate ends.

In the console

Real screens from the prototype

Captured from the running prototype with simulated data.

VRP mandates (Payments), 1440x1000 capture of the IronLedge prototype with simulated data
VRP mandates

For developers

Request shape

An illustration of the kind of data involved. API reference and SDKs are not yet published, so no endpoints are listed.

Illustrative mandate shape

{
  "limits": { "perPayment": "500.00", "perMonth": "1200.00" },
  "currency": "GBP",
  "status": "active",
  "note": "Illustrative only - not a published endpoint"
}

UK context

Regulatory background

Variable recurring payments are an Open Banking capability in the UK. Which banks support which VRP use is set by the banks and Open Banking Limited, and is not claimed here.

General background, not legal advice. No authorisation or certification is claimed on this page.

Related

Used in these solutions