When it fires
POST /v1/partner/accounts/{accountId}/withdrawals was called within 24 hours of a change to the account’s destination.
Why it happens
Withdrawals only ever go to the address you registered for the user. Pausing them for 24 hours after the address changes means a leaked key cannot change the address and take the money out in one go. You also receive anaccount.destination_changed webhook, so an unexpected change can be caught in that window. Nothing was recorded.
How to fix
- Wait for the time in the
Retry-Afterheader, then send the withdrawal again with the sameIdempotency-Key. - If you did not make the change, suspend the account (
POST /v1/partner/accounts/{accountId}/suspend) and contact ZeroID support from the info button in the Kash web app → Feedback, with theaccountIdand the id of the key to revoke.
Response headers
Retry-After: <seconds>: how long until the hold ends, 24 hours after the destination change.