Trusted destinations

A trusted destination is an allowlisted external address or USD bank recipient. Adding one requires quorum approval. Once allowlisted, it can be used across the iOS app, web dashboard, and APIs.

What you can do where

Operation	API	Web dashboard
View trusted destinations
Create (digital assets)
Create (USD bank recipient)
Delete
Edit
Batch upload
Network-level destination (`isNetworkLevel`)

You can create, list, and delete USD bank recipients (fiat trusted destinations) via API. To list them, call GET /v2/trusted_destinations and filter on type == "fiat". To add them in the web dashboard instead, see Adding a USD trusted destination in the USD banking guide.

Editing trusted destinations via API isn’t supported. To change a trusted destination, edit it in the web dashboard, or delete it and create a new one.

Sending to your own org’s addresses

You can allowlist addresses that belong to your own organization as trusted destinations to tag and label critical internal addresses. This is purely a convenience for recognition — it isn’t required for internal movement. If your concern is avoiding per-transaction quorum when moving assets between your own wallets, use the internal transfer API instead. Internal transfers set both source.type and destination.type to WALLET and don’t require a trusted destination, allowlisting, or AML information.

Create a trusted destination via API

Requires the Manage Trusted Destinations permission. Adding a trusted destination requires quorum approval.

// POST /v2/trusted_destinations
{
  "idempotentId": "{unique ID}",
  "trustedDestinations": [
    {
      "address": "{address}",
      "assetType": "{asset}",
      "name": "{name}",
      "description": "{description}",
      "isNetworkLevel": true,
      "memo": "{memo}",
      "trustedDestinationAmlQuestionnaire": {
        "destinationType": "FINANCIAL_INSTITUTION",
        "institutionName": "{institution name}",
        "institutionCountry": "US",
        "recipientType": "MY_ORGANIZATION"
      }
    }
  ]
}

Set isNetworkLevel: true to let the destination receive any asset on that network (digital assets only).

Create a USD trusted destination via API

Use the same POST /v2/trusted_destinations endpoint. Set type to "fiat" and describe the bank recipient in the fiat object instead of address and assetType. All trusted destinations in one request must be the same type, so send USD and digital asset destinations in separate requests. Adding a USD trusted destination requires quorum approval.

// POST /v2/trusted_destinations
{
  "idempotentId": "{unique ID}",
  "trustedDestinations": [
    {
      "type": "fiat",
      "name": "{name}",
      "fiat": {
        "usage": "MY_ORGANIZATION",
        "memo": "{note to beneficiary}",
        "beneficiary": {
          "type": "BUSINESS",
          "entityName": "Acme Holdings",
          "account": "{account number}",
          "address": "{street address}",
          "city": "{city}",
          "state": "{state}",
          "zipCode": "{zip code}",
          "country": "US"
        },
        "beneficiaryBank": {
          "name": "Example Bank",
          "code": "ABA",
          "id": "{9-digit routing number}",
          "address": "{street address}",
          "city": "{city}",
          "state": "{state}",
          "zipCode": "{zip code}",
          "country": "US"
        }
      }
    }
  ]
}

Field	Description
`type`	Set to `fiat`. Defaults to `crypto` when omitted, unless `fiat` is set.
`name`	Name used to identify the trusted destination, max 32 characters.
`fiat.usage`	Owner of the recipient account: `MY_ORGANIZATION` or `THIRD_PARTY`.
`fiat.memo`	Optional note to beneficiary, max 140 characters. Pre-populates on withdrawals to this destination.
`fiat.beneficiary`	Account holder details. `type` is `BUSINESS` (requires `entityName`) or `INDIVIDUAL` (requires `firstName` and `lastName`). `account`, `address`, `city`, `state`, `zipCode`, and `country` are always required.
`fiat.beneficiaryBank`	Recipient’s bank. `code` is `ABA` (9-digit routing number in `id`) or `BIC` (SWIFT code in `id`). `name`, `address`, `city`, `state`, `zipCode`, and `country` are always required.
`fiat.intermediaryBank`	Correspondent bank. Required when `beneficiaryBank.code` is `BIC`. Only US intermediaries identified by an ABA routing number are supported. Takes the same fields as `beneficiaryBank`, with `code` set to `ABA`.

Use ABA for domestic wires and BIC with an intermediaryBank for international wires. Track approval with GET /v2/trusted_destinations/{creationRequestId}/status, using the idempotentId from your request.

Delete a trusted destination via API

Call DELETE /v2/trusted_destinations/{trustedDestinationId} to remove a digital asset or USD trusted destination. Requires the Manage Trusted Destinations permission. Get the ID from GET /v2/trusted_destinations.

`trustedDestinationAmlQuestionnaire` fields

Required for Anchorage Digital Bank clients adding trusted destinations via API.

Omit trustedDestinationAmlQuestionnaire entirely for Porto organizations — including it, even as an empty object, causes the request to fail.

Field	Description	Required when
`destinationType`	`FINANCIAL_INSTITUTION` (for example, a crypto exchange) or `SELFHOSTED_WALLET` (for example, a hardware or browser wallet).	Always
`institutionName`	Name of the institution receiving the withdrawal.	`destinationType` is `FINANCIAL_INSTITUTION`
`institutionCountry`	Two-letter country code where the institution is incorporated.	`destinationType` is `FINANCIAL_INSTITUTION`
`selfhostedDescription`	Description of the self-hosted wallet.	`destinationType` is `SELFHOSTED_WALLET`
`selfhostedWalletOwner`	Owner of the self-hosted wallet: `MY_ORGANIZATION` or `PERSON_OR_ENTITY`.	Optional, when `destinationType` is `SELFHOSTED_WALLET`
`recipientType`	Ultimate beneficiary: `DESTINATION_INSTITUTION`, `MY_ORGANIZATION`, `PERSON`, or `ENTITY`. Use `MY_ORGANIZATION` for your own address at an exchange.	Always
`recipientFirstName`	First name of the beneficiary.	`recipientType` is `PERSON`
`recipientLastName`	Last name of the beneficiary.	`recipientType` is `PERSON`
`recipientFullName`	Full name of the beneficiary entity.	`recipientType` is `ENTITY`
`recipientCountry`	Two-letter country code of the beneficiary.	`recipientType` is `PERSON` or `ENTITY`
`recipientStreetAddress`	Street address of the beneficiary.	Optional, when `recipientType` is `PERSON` or `ENTITY` — required once `recipientCity` is set
`recipientCity`	City of the beneficiary.	Optional, when `recipientType` is `PERSON` or `ENTITY` — required once `recipientStreetAddress` is set
`recipientStateProvince`	State or province of the beneficiary.	Optional, when `recipientType` is `PERSON` or `ENTITY`
`recipientPostalCode`	Postal code of the beneficiary.	Optional, when `recipientType` is `PERSON` or `ENTITY`

Answer the questions below in order to see exactly which fields apply to your case, and the resulting payload:

Connect a trusted destination to an API key

If you’re using the Transfers API to transfer to a trusted destination, you need to configure your API key’s permission group to allow it. There are two options, set when configuring the Transfers outside Anchorage permission on your API key.

API key configuration screen with Any trusted destination and Specific destinations options — API key transfer configuration showing the trusted destination options

Specific destinations (default)

By default, your API key is scoped to Specific destinations. Once a trusted destination has been added and approved, you must also add it to the API key’s permission group before you can transfer to it. See Permission groups and API keys for the step-by-step flow.

Fiat trusted destinations can’t be added to a permission group’s specific-destinations list. If you’re transferring USD to bank recipients via the Transfers API, you must select Any trusted destination instead.

Any trusted destination

You can select Any trusted destination when configuring your key to automatically allowlist all current and future trusted destinations for that key. This removes the need to manually update the permission group each time a new trusted destination is approved. This option is required for USD transfers to fiat trusted destinations.

APIs

API	Description
List trusted destinations	Returns trusted destinations. Filter on `type == "fiat"` for bank recipients.
Create new trusted destinations	Allowlists one or more digital asset or USD destinations. Requires quorum approval.
Check status of trusted destinations	Returns the approval status of a pending destination.
Delete trusted destination	Removes a digital asset or USD destination.

Platform

Solutions

What you can do where

Sending to your own org’s addresses

Create a trusted destination via API

Create a USD trusted destination via API

Delete a trusted destination via API

`trustedDestinationAmlQuestionnaire` fields

Connect a trusted destination to an API key

Specific destinations (default)

Any trusted destination

APIs

​What you can do where

​Sending to your own org’s addresses

​Create a trusted destination via API

​Create a USD trusted destination via API

​Delete a trusted destination via API

​trustedDestinationAmlQuestionnaire fields

​Connect a trusted destination to an API key

​Specific destinations (default)

​Any trusted destination

​APIs

What you can do where

Sending to your own org’s addresses

Create a trusted destination via API

Create a USD trusted destination via API

Delete a trusted destination via API

`trustedDestinationAmlQuestionnaire` fields

Connect a trusted destination to an API key

Specific destinations (default)

Any trusted destination

APIs