virtualAccountId. You need an API key with the Transfer funds permission, and the request must carry an Ed25519 signature. See Request signing.
Staging uses the
USD_R asset type and https://api.anchorage-staging.com/v2. Production uses USD and https://api.anchorage.com/v2. The example below shows the staging value.Create a transfer from a virtual account
POST /v2/transfers
Set source.type to WALLET, source.id to your FBO wallet’s ID, and source.virtualAccountId to the virtual account the withdrawal belongs to. Set destination.type to TRUSTED_DESTINATION and destination.id to a USD trusted destination, and include assetParametersFiatTrustedDestination. See Create a transfer request for the full reference.
To pay out to your customer’s bank account, add it as a USD trusted destination first. To move funds to another virtual account, see Transfer to another virtual account.
Request
Response
Fields
We don’t track a balance for each virtual account, so we can’t stop a withdrawal that exceeds what your customer holds. Check the customer’s balance on your own ledger before you submit the transfer.
Transfer to another virtual account
To move USD to another virtual account, setdestination.type to WALLET, destination.id to the destination wallet’s ID, and destination.virtualAccountId to the receiving virtual account. Leave out assetParametersFiatTrustedDestination.
Request body
Track the transfer
Transfers are queued and processed in the order we receive them. Check a transfer’s status with Get transfer by ID, or subscribe to webhooks instead of polling. To list transfers for one virtual account, callGET /v2/transfers with the virtualAccountId query parameter, or with customerId for every virtual account a customer owns.