The rule
Per PS-SOP §2.6 (“return-to-source”), withdrawals follow a cleared-deposit-source policy:- If the destination is a wallet that previously deposited into the platform and was AML-cleared, the withdrawal proceeds on the fast path.
- If the destination is new and the amount is below the EDD
threshold (default 5 000 USDC), the withdrawal is rejected
with
destination_not_cleared. - If the destination is new and the amount is at or above the
threshold, the withdrawal enters
MLRO_REVIEW.
How a deposit source becomes cleared
Every on-chain deposit triggers an AML screen on the depositing EOA. On a clean result the source is recorded as cleared and is immediately eligible as a withdrawal destination for the same vault. A failed screen leaves the source uncleared (fail-closed) and a withdrawal to that destination follows the EDD review path or is rejected per the rule above. On testnet the AML screen is suppressed (see Environments) so every deposit auto-clears for integration testing.Why
This is an AML countermeasure. A market maker who deposits from Wallet A cannot directly withdraw to Wallet B without first depositing from B at some earlier point.Listing your cleared sources
Withdrawal endpoints accept API-key auth (
X-Api-Key +
X-User-Wallet). Multi-wallet partner keys with
requirePerWalletKyc=false use the same flow — the FSM is identical
regardless of which sub-account the key acts on.MM & partner pattern
For market makers with a treasury wallet:- Small deposit from the treasury first (e.g. 100 USDC) seeds the cleared-source record.
- Subsequent withdrawals to the same wallet go through the fast path.
- For operational spread (multiple hot wallets), repeat for each.
When you hit EDD review
- Status:
MLRO_REVIEWfor up to 1 business day. - Reason:
new destination $X >= threshold $5000. - Contact onboarding pre-large-withdrawals to pre-clear new destinations.