On a deposit
A held deposit sits inKYT_PENDING. From there it moves on when the check passes (a bank deposit to a fiat account completes, any other goes back to PENDING), or moves to KYT_REJECTED. A crypto inbound can also end FAILED during the review.
KYT_REJECTED is not FAILED. A failure is technical, and this is a decision. Keeping them apart is what makes the record readable afterwards. Only a return moves it, to REFUNDED. A rejection is never withdrawn, so a rejected deposit is never credited.
On a payout
A held payout sits inKYT_PENDING, or in IN_REVIEW when the hold is a manual check rather than an automatic one.
Both reach you only on payout.status_changed. See Payouts.
The hold that waits on you
A compliance check can also ask for something instead of deciding. The movement is then held on a request for information, not on a running check. The payout or deposit reportsstatus of NEEDS_ACTION, and a payout also carries an rfi object with the request and its deadline. The stage underneath does not change. The movement continues from there when the request closes.
A request holds only what it names. One anchored to a payout holds that payout, and the sub-client’s other movements continue. One about the sub-client holds their verification, not a movement.
Who releases it
A check or a reviewer. The exception is a request for information: you end that hold by answering it. No endpoint releases a hold, and retrying the movement does not change one. What you can do:- Show it as pending, not as failed and not as done.
- Answer the request when
statusreadsNEEDS_ACTION. It is the only hold your integration can lift. - Do not retry. Retrying with the same idempotency key returns the same held movement; retrying with a fresh one creates a second one that will be held for the same reason.