Guides
Idempotency
Idempotency
Money-moving operations accept an optional Idempotency-Key header. Reusing the same key with the same payload returns the original result instead of creating duplicate charges.
When to use it
| Policy | Meaning |
|---|---|
required | Header mandatory |
recommended | Strongly advised for checkout and payment links |
none | Reads and listings |
Generate a unique key per user intent (UUID recommended). Retries for the same intent should reuse the key.
Example
Send the request to {docsEnv.apiBaseUrl}:
Code
Use Sandbox or test keys in this environment.
Next steps
- API Reference — idempotency policy per operation
- Errors — failure codes
- Getting started — first API call
Last modified on