Skip to main content
A trusted destination is an external address or bank recipient your organization has added to its allowlist of approved recipients. Adding a trusted destination requires quorum approval up front, before any funds move to it. Once approved, you can withdraw to that destination without collecting a separate quorum approval for each transaction when using the API. You can also configure a policy to only allow withdrawals to trusted destinations — turning the allowlist into a hard control rather than just a convenience. To block withdrawals to one-time (non-allowlisted) addresses entirely, ask your sales or client experience support to enable the trusted-destinations-only control for your organization. Adding a trusted destination follows your default administrator policy unless a custom trusted destination policy is configured — see Managing administrator policy rules.
Adding a trusted destination requires biometric approval in the iOS app and quorum approval. Only administrators with trusted destination management permissions can add or remove trusted destinations.

​
Crypto trusted destinations

Trusted destinations for crypto are per-network. The same address on Ethereum and on Base are two separate trusted destinations, so add one for each network you’ll withdraw to. A withdrawal can fail if the address is allowlisted on a different network than the one you’re sending on. Smart-contract and program addresses can also be added as trusted destinations. Self-service whitelisting for program-derived (off-curve) addresses is coming soon — for now, contact your client experience team to add one on your behalf.

​
Adding a single crypto trusted destination

1

Open trusted destinations

In Settings, under Trusted addresses, select Trusted destinations, then select Add.
2

Select single address

Select Add single address.
3

Enter address details

Select the asset, enter the address, provide a name and description, then select Continue.
4

Fill out the form

Complete the address details form and select Continue. Optionally add a comment.
5

Confirm and approve

Review the operation details and select Confirm and submit for approval. Complete the endorsement process in the Anchorage Digital iOS app.
The AML field on a trusted destination isn’t set during setup. It populates at withdrawal time from the latest prior transaction to that address and asset, so it can be empty on your first withdrawal and fills in automatically on subsequent ones.

​
Adding multiple crypto trusted destinations

1

Open trusted destinations

In Settings, under Trusted addresses, select Trusted destinations, then select Add.
2

Select bulk upload

Select Upload multiple from file.
3

Download and complete the template

Download the provided Excel spreadsheet template and fill it out in your preferred spreadsheet editor (Excel or Google Sheets). Save the completed file as a CSV.
4

Upload the CSV

Upload your completed CSV file to the web dashboard.
5

Review and submit

Review the list of trusted destinations, make any necessary adjustments, and select Submit for approval. Complete the endorsement process in the iOS app.

​
Template fields

The required fields above match the ones marked with a red asterisk in the downloadable template.
After uploading, Anchorage Digital parses the file and lets you review results and address any warnings or errors. If unresolvable errors are found, you’ll need to correct and re-upload the file.

​
USD trusted destinations

For USD withdrawals, you add the recipient’s bank information as a trusted destination. See USD withdrawals for the step-by-step process.

​
Sending to your own org’s addresses

You can add addresses that belong to your own organization as trusted destinations to tag and remember critical internal addresses. This is entirely optional — you don’t need a trusted destination to send to your own vaults. When withdrawing to an address your organization already controls, select the destination type that fits your workflow:
Withdrawal dialog with Another Vault highlighted in the Destination type dropdown

Select Another Vault to send directly to one of your own vaults

  • Another Vault — sends to one of your own vaults directly. No trusted destination setup or per-request quorum approval is needed, making this the simplest path for routine internal movement.
Withdrawal dialog with Trusted Destination highlighted in the Destination type dropdown

Select Trusted Destination to send to a pre-approved address you've labeled

  • Trusted Destination — sends to a pre-approved, labeled address. Use this when you’ve added your own org’s address as a trusted destination so your team can recognize it by name during future withdrawals.
If you’re integrating via API and want to avoid per-transaction quorum for internal movements, use the internal transfer API — it moves assets between your own wallets without allowlisting or quorum approval.

​
After you submit

Adding or removing a trusted destination goes through two stages: your own quorum approves it, then Anchorage Digital reviews it. Our review usually finishes within 15 to 20 minutes of quorum being met, and often sooner. Because the two stages run back to back, the wall-clock time from initiation to completion depends mostly on how quickly your approvers act. A request that looks slow has often been waiting on the last approver rather than on us — check the operation’s status before escalating.

​
Exporting trusted destinations

To get a full list of your organization’s trusted sources and trusted destinations, ask your client experience team or email accountexecutive@anchorage.com. A self-serve export isn’t available today, so we produce the list for you.

​
Removing trusted destinations

1

Navigate to trusted destinations

In Settings, under Trusted addresses, select Trusted destinations.
2

Select the destination

Select the three-dot menu next to the trusted destination you want to remove.
3

Confirm removal

Select Remove. Biometric approval in the iOS app is required. Once quorum is met, Anchorage Digital will review the operation.