Table of contents

Delayed capture of payments

You can control how long it takes GOV.UK Pay to take (‘capture’) a payment from your user’s bank account after your Payment Service Provider (PSP) has authorised that payment.

You may want to use delayed capture if you need time to do your own anti-fraud checks on payments, or check that users are eligible for your service.

During the delay, your user’s available bank balance is reduced by the payment amount.

To use this feature, include "delayed_capture": true in the body of a Create new payment request.

The user experience matches the current payment flow. Once the user selects Confirm on the Confirm your details page:

  • the payment status will change to capturable
  • your service can call the POST /v1/payments/{paymentId}/capture endpoint to send a delayed capture request

Refer to the API browser or the Swagger file for more information.

There are 4 possible responses:

Response Code Meaning
204 Capture request accepted
404 paymentId does not exist
409 Capture request rejected
500 Downstream error

Your service must send the delayed capture request within 48 hours of the payment creation, regardless of how long the user takes to complete the payment flow. Otherwise, it will expire.

If your service has enabled payment receipt emails, GOV.UK Pay will send a payment receipt email to the user once your service’s capture request is received and accepted.

See the capture URL for a payment

If a payment is available for capture, you can see its capture URL in responses to API calls. For example:

  • GET /v1/payments/{paymentID}

  • GET /v1/payments

The "__links" object will contain:`

"capture": {
"href": "<PAYMENT-ID>/capture",
    "method": "POST"

If the payment is not available for capture, the "__links" object will contain:

"capture": null