Skip to main content
With any destination, you send USD to a bank account by including the beneficiary and bank details in the transfer request itself. The account doesn’t need to be saved as a trusted destination first.

Set up the permission group

Create a permission group dedicated to any destination transfers. A permission group can’t use any destination and trusted destinations at the same time, so keep trusted destination transfers in a separate permission group and API key.
1

Create a permission group

In the web dashboard, select Developers, then Permission groups, and create a new group.
2

Grant vault permissions

Under the vault permissions, select Transfer funds for all vaults, or for only the vaults that should send these transfers. Also select Read for the same vaults so the key can check balances and track transfer status.
3

Allow any destination

Turn on Transfers outside Anchorage, then select Any destination.
Permission group transfer settings with Transfers outside Anchorage turned on, Any destination selected, and a daily amount limit

Any destination selected under Transfers outside Anchorage

4

Set a daily limit

Next to Set a daily amount limit, select Edit and enter a limit. It’s required for any destination and is currently capped at $10 million. The limit applies across all keys in the group over a rolling 24-hour window. If you need a higher limit, contact your Anchorage Digital relationship manager.
5

Submit for approval

Select Save, then endorse the change in the iOS app—quorum approval is required. Anchorage Digital then reviews and approves the permission group before you can use it.

Set up the API key

Create an API key against the permission group once it’s approved. A public key is mandatory for any destination keys.
1

Generate a key pair

Generate an Ed25519 key pair. See API keys for a generator and a Python script.
2

Create the API key

In the Developers, then API 2.0 section of the web dashboard, select Create API key. Select the any destination permission group and paste your public key.
3

Submit for approval

Follow the prompts to submit biometric approval—quorum approval is required. Anchorage Digital then reviews and approves the key. Requests made with the key fail until both approvals are complete.

Send a transfer

Call POST /v2/transfers with an Ed25519 request signature. Set destination.type to FIAT_INLINE and put the payment details in destination.details. Don’t send destination.id. destination.details carries one payment rail object, such as wire, with the beneficiary and their bank. The example below sends by wire.
Don’t send assetParametersFiatTrustedDestination with a FIAT_INLINE destination. Set purpose and memo inside destination.details instead. A successful request returns 201 with a transferId and status, the same as other transfers. Track it through the transactions API. See Track movement status.

Limits and reviews

  • Daily limit: each permission group can currently send up to $10 million in a rolling 24-hour window. Once a group reaches its limit, further transfers return 400 until enough of the window passes. To request a higher limit, contact your Anchorage Digital relationship manager.
  • Manual review: Anchorage Digital holds a transfer for review when it exceeds a per-payment threshold or when screening flags the beneficiary. The transfer continues once it’s approved.
Any destination is less secure than trusted destinations, because an approved key can send funds to any bank account without per-destination approval.