Payout idempotency

Created by Mayank Singhal, Modified on Sat, 11 Jul at 6:34 PM by Mayank Singhal

Question:


If we retry a payout creation call (network timeout, our system crashes), does the provider create a duplicate payout or return the existing one? What field controls idempotency? (Header idempotency_key? Field external_id? None?)

Answer:

Idempotent by design. Every POST/PUT requires an Idempotency-Key HTTP header (unique per logical attempt, e.g. a UUID). 

Retrying payout creation with the same key and same request returns the original payout's stored response unchanged (flagged with an Idempotency-Replayed: true header) — no duplicate is created. 

Reusing that key with a different request body is rejected (422); retrying while the first call is still processing returns 409. Keys are scoped per organization and expire after 24h by default.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article