FaucetPay merchant callbacks and the retry schedule
The token is single use and they retry at fixed intervals, so check your own order first and answer 200 before verifying again.
Tagged “retries”
3 entries
Idempotency keys on a FaucetPay v2 payout
Generate the key and save it on the claim row before you call send, then reuse it on every retry. Generating it at call time is the same as having none.
Idempotency keys on every operation that moves money
A caller-supplied key with a unique index turns every retry, refresh and double-click into a no-op. The single most valuable column in a payments schema.