Recurring payments
Make repeat payments easier to manage.
Capabilities
Recurring flag
Recurring token
Repeat payment workflow
Callback notifications
How a recurring flow works
- 01
Initialise
Create the customer's first payment with
recurring: true. The customer completes it in the normal way, including any authentication."recurring": true - 02
Store the reference
The callback for the approved payment includes a
recurringToken. Store it against the customer in your system. It is a reference, not card data. - 03
Charge again
When your billing logic decides a payment is due, create a new payment and pass the stored
recurringToken."recurringToken": "…" - 04
Reconcile
Each repeat payment has its own token and status, delivered by callback and retrievable through the API.
What stays in your system
Rainbow Pay executes repeat payments; your platform owns the billing schedule, the customer's agreement to be charged, and what happens when a repeat payment is declined. That keeps pricing, plans and customer communication in the product you already run.
Make sure customers agree to repeat payments in clear terms before the first payment, and give them a straightforward way to cancel.
Scope of the recurring feature
The recurring feature provides the flag, the token and the repeat-payment call described above. Subscription invoicing, automated retry schedules (dunning), card account updater services and network tokenisation are not part of the published feature set. If your model depends on any of these, discuss it with us before you integrate.
Recurring payments are available for eligible payment configurations. Availability is subject to merchant eligibility, integration configuration and market support.
Related products
Ready to discuss your payment setup?
Tell us how your business accepts payments today and what you need from your next payment integration.