> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anchorage.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Any destination bank transfers

> Set up a permission group and API key to send USD to any bank accounts.

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](https://docs.anchorage.com/knowledge-base/platform/developers/move-money/setup/trusted-destinations) 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](https://docs.anchorage.com/knowledge-base/platform/developers/move-money/operate/track-status.md).

**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](https://mintcdn.com/deployment-4/A0-OzsewIDn-oDM8/knowledge-base/images/screenshots/any-destination-permission-group.png?fit=max\&auto=format\&n=A0-OzsewIDn-oDM8\&q=85\&s=9597a983915c923d132d5e6481580be1)

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](https://docs.anchorage.com/knowledge-base/platform/developers/api-keys.md) 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.

```json theme={null}
{
  "idempotentId": "{unique ID}",
  "source": {
    "id": "{source wallet ID}",
    "type": "WALLET"
  },
  "destination": {
    "type": "FIAT_INLINE",
    "details": {
      "purpose": "EXPENSES",
      "wire": {
        "memo": "{note to beneficiary}",
        "beneficiary": {
          "type": "BUSINESS",
          "entityName": "Acme Corp.",
          "account": "{account number}",
          "address": {
            "addressLine1": "{street address}",
            "city": "{city}",
            "state": "{state}",
            "zipCode": "{zip code}",
            "country": "US"
          }
        },
        "beneficiaryBank": {
          "name": "The Bank of New York Mellon",
          "code": "ABA",
          "id": "{9-digit routing number}",
          "address": {
            "addressLine1": "{street address}",
            "city": "{city}",
            "state": "{state}",
            "zipCode": "{zip code}",
            "country": "US"
          }
        }
      }
    }
  },
  "assetType": "USD",
  "amount": "{quantity}"
}
```

| Field | Description |
| :- | :- |
| `destination.type` | `FIAT_INLINE`. |
| `destination.details.purpose` | Required. See [`purpose` values](https://docs.anchorage.com/knowledge-base/platform/developers/move-money/transfer/usd/wire/domestic#purpose-values). |
| `destination.details.<rail>.memo` | Optional note to beneficiary, max 140 characters. |
| `destination.details.<rail>.beneficiary` | Account holder. `type` is `BUSINESS` (requires `entityName`) or `INDIVIDUAL` (requires `firstName` and `lastName`). `account` and `address` are always required. |
| `destination.details.<rail>.beneficiaryBank` | Recipient's bank. `code` is `ABA` (routing number in `id`) or `BIC` (SWIFT code in `id`). `name`, `id`, and `address` are always required. |
| `destination.details.<rail>.intermediaryBank` | Optional correspondent bank, for wires. Takes the same fields as `beneficiaryBank`, with `code` set to `ABA`. |
| `address` | `addressLine1`, `city`, `state`, `zipCode`, and `country` (ISO 3166-1 alpha-2) are required. `addressLine2` is optional. |

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](https://docs.anchorage.com/knowledge-base/platform/developers/move-money/operate/track-status.md).

## 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.

> [!WARNING]
>
> Any destination is less secure than trusted destinations, because an approved key can send funds to any bank account without per-destination approval.


## Related topics

- [ACH credit transfer](https://docs.anchorage.com/knowledge-base/platform/developers/move-money/transfer/usd/ach/credit.md)
- [Domestic wire transfer](https://docs.anchorage.com/knowledge-base/platform/developers/move-money/transfer/usd/wire/domestic.md)
- [International wire transfer](https://docs.anchorage.com/knowledge-base/platform/developers/move-money/transfer/usd/wire/international.md)
- [Transfers and withdrawals](https://docs.anchorage.com/knowledge-base/platform/developers/move-money/transfers-vs-withdrawals.md)
- [Trusted destinations](https://docs.anchorage.com/knowledge-base/platform/developers/move-money/setup/trusted-destinations.md)
