> This page is for version v2 (default).
> For other versions, use one of these documentation indexes:
> - v2 (default): https://developers.clearpay.co.uk/v-2/llms.txt
> - v1: https://developers.clearpay.co.uk/v-1/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.clearpay.co.uk/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.clearpay.co.uk/_mcp/server.

# Authorise Recurring Payment (Deferred Capture)

> **The Readme API Simulator includes form elements for both required and optional body params. If not populated with values, Readme sends empty strings to the Afterpay Online API. Any optional parameter that is validated against a model will need to have all of its required sub-params populated with non-empty values.**
>
> Therefore, to avoid receiving unexpected "400" responses from Clearpay, please fill out all the simulation form fields with valid values. This is particularly important for the `amount` and `currency` sub-params of the `amount`, `taxAmount` and `shippingAmount` params.

> **Note**
>
> This operation is [idempotent](/idempotent-requests) based on the `requestId` (if provided), which allows for the safe retry of requests, guaranteeing the payment operation is only performed once.

> **Note**
>
> The customer's payment plan starts at the time of auth approval.

## Approved Response (201)

If payment is approved by Clearpay, returns a [Payment object](/payment-object) in response, with a `status` of "APPROVED" and a `paymentState` of "AUTH_APPROVED".

## Declined Response (402)

If payment is declined by Clearpay, for example, if invalid card details were entered, returns a [Payment object](/payment-object) in response, with a `status` of "DECLINED".

Please advise the customer to contact the Clearpay Customer Service team for more information.

## Connection Timeouts

| Timeout | Time (Seconds) |
| :------ | :------------- |
| Open    | 10             |
| Read    | 70             |

## Errors

In addition to the [PUT/POST Errors](/put-post-errors) applicable to all POST endpoints, the following errors are specific to Authorize Recurring Payment (Deferred Capture):

| HTTP Status Code              | errorCode        | Description                                                                              |
| :---------------------------- | :--------------- | :--------------------------------------------------------------------------------------- |
| **402**  Payment Required     | `invalid_token`  | The billing agreement token is invalid, expired, completed, or does not exist.           |
| **403**  Forbidden            | `forbidden`      | Access is forbidden. Recurring payments product must be enabled on the merchant account. |
| **422**  Unprocessable Entity | `invalid_object` | One or more required fields were missing or invalid.                                     |

## Recurring Payments Documentation

* [Recurring Payments](/recurring-payments)
  * [Store Clearpay as a Payment Method](/store-clearpay-as-a-payment-method)
  * [Checkout and Store Clearpay as Payment Method](checkout-and-store-clearpay-as-payment-method)
  * [Create Recurring Payment](/create-recurring-payment)
* [Recurring Payments Flow](/recurring-payments-flow)
  * [Setup Billing Agreement Approval](/setup-billing-agreement-approval)
  * [Create Billing Agreement](/create-billing-agreement)
  * [Get Billing Agreement](/get-billing-agreement)
  * [Cancel Billing Agreement](/cancel-billing-agreement)
  * [Create Recurring Payment (Immediate Capture)](/create-recurring-payment-immediate-capture)
  * [Authorise Recurring Payment (Deferred Capture)](/authorise-recurring-payment-deferred-capture)