You're viewing documentation for our latest API. This will not impact your integration, but you will need the documentation relevant to you. If you have an account with Checkout.com you have received an email confirming which version to use.
Occasionally, you may need to retry a payment or payment action (for example, void) due to a disrupted API call owing to a network error or timeout. Our payments endpoint supports idempotency, so you can safely retry requests without a duplicate payment taking place or a payment action being performed twice.
To perform an idempotent payment or payment action request, provide the Cko-Idempotency-Key HTTP header. Keys should be unique and will expire after 24 hours for production environments and 120 seconds for sandbox environments, after which the request will be processed as normal. We strongly recommend using V4 UUIDs.
Subsequent requests with the same key will return the same HTTP status code and response body as the first request, providing that it was processed successfully. If the first request could not be processed, for example due to a validation error, no idempotent result will be saved and the payment will be reattempted.
If we detect concurrent requests with the same idempotency key, only one request will be processed and the other requests will return a 429 Too many requests response. One scenario where this could occur is if you automatically retry a payment following a network issue, but the original request is still being processed. We recommend waiting for at least 30 seconds before attempting again.
curl-X POST https://api.sandbox.checkout.com/payments