Reuse the same key
Generate one unique key per intended operation and reuse it with byte-for-byte equivalent semantic parameters for every timeout, network retry, or process restart.
Developer preview API v1
Sandbox only. No real funds moved. No production access is granted here. Access requirements
Duplicate prevention
Retry the operation, not the intention
A stable operation identity is the boundary between safe replay and duplicate value movement.
Never repurpose a key
A key reused with different parameters fails with idempotency_conflict. A new key represents a genuinely new operation and can cause duplicate value movement if misused after ambiguity.
Persist before calling
Store the key and your operation reference durably before the first request. Preserve both in logs without credentials or customer-sensitive data, and reconcile unknown outcomes.