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.
| Scenario | Behavior |
|---|---|
| First request | Processed normally; response cached against the key |
| Retry with the same payload | Returns a 409 Conflict error |
Supported Endpoints
Idempotency is supported on all POST endpoints that create resources:
| Endpoint | Resource |
|---|---|
POST /v1/payments/charges | Payment charges |
POST /v1/payouts | Payouts |
POST /v1/transfers | Transfers |
GET, PUT, and DELETE requests are inherently idempotent and do not require idempotency keys.