Idempotency

Safely retry requests without moving money twice.

Networks fail. A request can time out after Syper has processed it. Idempotency lets you retry without creating a second payment or transfer.

How it works

1. Generate a unique key (for example a UUID) for each logical operation.
2. Send it with the write request.
3. If you retry with the same key and the same parameters, Syper returns the original result instead of repeating the operation.
4. Reusing a key with different parameters is rejected.

When to use it

Use an idempotency key on every request that creates or changes money movement or account state. This matters most for machines and agents, which retry automatically — a robot on an unstable connection should never pay twice.

Header name, key format, and retention are documented in the Idempotency API reference.