Idempotency for refunds, voids, and captures

You can now use idempotency with post-authorisation operations. The /refunds, /voids, and /captures endpoints support the standard Idempotency-Key header so you can safely retry requests without creating duplicate financial actions. You can send a unique Idempotency-Key header with your POST request. If a timeout occurs, resend the exact same request with the same key. we will return the stored result without calling the payment processor again. For implementation guidance, see Idempotent Requests.