Idempotency

Idempotency ensures that retrying a request produces the same result as the original request, preventing duplicate resource creation. This is essential for payment operations where network failures or timeouts may require request retries.

ScenarioBehavior
First requestProcessed normally; response cached against the key
Retry with the same payloadReturns a 409 Conflict error

Supported Endpoints

Idempotency is supported on all POST endpoints that create resources:

EndpointResource
POST /v1/payments/chargesPayment charges
POST /v1/payoutsPayouts
POST /v1/transfersTransfers

GET, PUT, and DELETE requests are inherently idempotent and do not require idempotency keys.

Was this page helpful?