Skip to main content
POST
Trigger Recurring Payment
Trigger a charge on an active ADHOC subscription. The API call initiates the payment — the actual payment outcome (success, failure, or cancellation) is delivered asynchronously via webhooks, at which point the order and payment records are created in the system.
This endpoint only supports ADHOC subscriptions. The subscription must have an active mandate before a recurring payment can be triggered.

Path Parameters

string
required
The unique identifier (uid) of the subscription.

Request Body

number
Amount to charge for this recurring execution. If not provided, the subscription’s billing_amount is used. Must be less than or equal to the subscription’s billing_amount.
string
Your reference for this charge: 1–50 letters, numbers and hyphens. It becomes this debit’s payment_id, so the outcome comes back under your own reference. Must be unique across your orders, including failed ones. If omitted, a payment_id is generated with a REC- prefix.

Response Fields

string
The subscription identifier.
string
Identifier of this debit: the reference_id you sent, or one generated with a REC- prefix. Store it against your order: when the debit’s outcome arrives, its payment carries this value as merchant_reference_id in the Payment Successful and Payment Failed webhooks, and as reference_id in Get Subscription Payments. A retried debit has -attempt-1, -attempt-2, and so on appended. It is not the ID of a payment record, so Get Payment does not accept it.
number
The amount charged for this recurring payment.
string
Status of the API call. success means the payment was initiated — not that it has been captured.