Skip to main content
An internal crypto transfer moves digital assets between wallets you own at Anchorage Digital, without quorum approval on each request. No allowlisting or AML information is required. To send to an allowlisted address outside Anchorage Digital, see External transfer. POST /v2/transfers requires the Transfer funds permission and an Ed25519 request signature.

Send an internal transfer

Set both source.type and destination.type to WALLET.

Fields

Response

A successful request returns 201 with a transferId and status:

Transfer behavior

These behaviors apply to both internal and external crypto transfers. Queuing — Up to 50 transfer requests from the same source wallet can be queued at once. Transfers for the same asset on the same blockchain process one at a time; others stay QUEUED until the prior transfer completes or fails. Transfers on different wallets or different blockchains can process in parallel. Transfers expire 24 hours after initiation. useGasStation — If true, Anchorage Digital’s gas station pays network fees for supported assets and organizations. Processing is slightly slower, since Anchorage Digital prefunds the originating wallet before executing the transfer. deductFeeFromAmountIfSameType To transfer a full balance of an asset whose fee is paid in the same asset (for example, BTC), set deductFeeFromAmountIfSameType: true. When the source is a walletId, fees are deducted from that wallet; when the source is a vaultId, fees come from the vault’s default wallet (isDefault: true).

Troubleshooting

Common request-level failures: the source wallet doesn’t exist or doesn’t support the asset, the amount exceeds available funds, the destination doesn’t support the asset, or the key lacks permissions for the source vault. After a request succeeds, the transfer can still fail at execution if there are insufficient funds to cover the network fee at broadcast time or there’s a blockchain-level failure.