Create recurring top up
Create a recurring top up configuration.
For more information, refer to Create recurring top-ups.
The unique identifier of the balance account.
The details about the counterparty that is funding the top-up.
Your description for the recurring top-up.
Maximum length is 140 characters. If you set a longer description, it will be cut off at 140 characters.
A reference that is sent to the recipient. This reference is also sent in all webhooks related to the transfer, so you can use it to track statuses for both parties involved in the funds movement.
Supported characters: a-z, A-Z, 0-9.
The status of the recurring top-up. If not provided, by default, this is set to active.
Possible values:
-
active: the top up is enabled and funds will be pulled in.
-
inactive: the top up is disabled and cannot be triggered.
The currency and value to be added to the balance account, specified in minor units. This can be a fixed amount or a target amount.
The condition that triggers the top-up. This can be a recurring schedule or a minimum balance threshold.
After submitting a call, you receive a response message to inform you that your request was received and processed.
Depending on the HTTP status code of the response message, it is helpful to build some logic to handle any errors that a request or the system may return.
HTTP Responses
200 - OK
The request has succeeded.
400 - Bad Request
A problem reading or understanding the request.
401 - Unauthorized
Authentication required.
403 - Forbidden
Insufficient permissions to process the request.
422 - Unprocessable Entity
A request validation error.