receiverAccountId, or by your own receiverExternalId if you set one on the account. There are two endpoints, differing only in how you denominate the amount.
Fiat vs crypto
Both settle on-chain and return a
transactionHash.
Prerequisites
The sender account must be verified. For self-custody senders, the wallet must also be active with an allowance to the orchestration wallet — see Approving transfers without gas.Create a fiat transfer
Response
/transfers/crypto, sending chain + asset instead of currency (and the response omits fiatOrigin).
Choosing which asset it settles in
A fiat amount has to become a specific token on a specific chain. While your tenant holds one asset for that currency,currency alone is enough and Venly picks it.
If your tenant holds the same currency on more than one chain — USDC on Base and Avalanche, both USD — that’s ambiguous, so name the pair:
Status lifecycle
A transfer’sstatus is PENDING → COMPLETED, or FAILED (with an errorMessage). Settlement is on-chain, so poll Get a transfer — or List transfers, filtering by accountRole (SENDER/RECEIVER) and status.
Idempotency
Every transfer takes a uniqueidempotencyKey; retrying with the same key returns the original transfer instead of sending again. See Safe retries with idempotency keys.
Next steps
Create a crypto transfer
The endpoint reference and full schema.
Supported assets
Which chains and assets your tenant can settle in.