Draft Authorise Recurring Payment (Deferred Capture)
Draft Authorise Recurring Payment (Deferred Capture)
Draft Authorise Recurring Payment (Deferred Capture)
Once a recurring payment has been created, it must be authorised. The authorisation uses a Billing Agreement as the payment method. This endpoint determines the order approval status.
If the order is approved, the Auth (authorisation) has an expiration date and time. This information is returned in the events list for the AUTH_APPROVED payment event.
The process starts with this post:
POST /v2/recurring-payments/auth
Sample Request
Request Parameters
Example Request Body
Responses
Unprocessable Entity reasons - 422 in the table above
Example Responses
201 Response
400 Response
401 Response
Declined Payment
If the payment is declined by Clearpay, it returns a Payment object in response, with a status of “DECLINED”. For example, if invalid card details were entered.
This occurs if the billing agreement token is invalid, expired, completed, or does not exist.
405 Response
406 Response
415 Response
The create checkout request could not be processed for one of these reasons:
500 Response
Response Schema
Enumerated Values
The payment is captured in the same way as any other standard payment is captured. See the Deferred Capture topic for more details
To do any of the above operations, you must be authenticated by MerchantAuthentication.