Informational only. Withdrawals are not limited to addresses
that previously deposited. There is no
destination_not_cleared
rejection, and
withdrawing to a new destination does not by itself send a withdrawal
to review. To restrict where a wallet can withdraw, use the
address whitelist.How a source gets listed
A deposit into your vault from an external wallet records the address that funded it, and that address is AML-screened. When the screen passes, the address is listed with aclearedAt timestamp. An address
that fails the screen is not listed.
Listing your deposit sources
Requires the
portfolio:read scope. Multi-wallet partner keys also
send the X-User-Wallet header naming the acting
wallet. The wallet must also have completed ID verification: below
that, the call answers 403 with withdraw_kyc_tier_required
(partner-backed sub-accounts with requirePerWalletKyc=false are
exempt). Rate limit: 60 requests per minute per wallet.sourceAddress— the address that deposited into your vault and passed the AML screen. Returned in EIP-55 checksum case; compare case-insensitively.firstSeenAt— timestamp of the first deposit observed from this source. The list is ordered newest first by this field.clearedAt— timestamp of the AML clear.
What does send a withdrawal to review
Whether a withdrawal is approved, rejected or held forMLRO_REVIEW
is decided per request, and deposit history plays no part in it:
Rejections come back in the response body as
status: "rejected" with
a code. A held withdrawal enters MLRO_REVIEW and waits for a
compliance decision; see the
state machine.