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

# Overview

> Give each customer their own USD deposit instructions, all settling into one FBO wallet.

Named Virtual Accounts let you give each of your customers their own USD bank deposit instructions, all settling into a single wallet you hold with Anchorage Digital. This page covers who the program is for, how to get set up, and the building blocks you'll work with in the API.

> [!NOTE]
>
> Named Virtual Accounts are available only to licensed entities that maintain their own ledger. If you're not a licensed entity, or you'd rather rely on Anchorage Digital's ledger, we plan to launch Named Wallets for you. Named Wallets are coming soon.

## Building blocks

> [card] FBO wallet
>
> A for benefit of (FBO) wallet provisioned for your organization. It's the wallet your virtual accounts are created on, and where your customers' deposits settle.

> [card] Customer
>
> An individual or institution you onboard through the API. Each customer gets a `customerId` that you use to create their virtual accounts.

> [card] Named Virtual Account
>
> A set of USD bank deposit instructions linked to one customer and one FBO wallet. A customer can have as many virtual accounts as the limit agreed with Anchorage Digital.

## Get enabled

Our compliance team must approve your organization for the Named Virtual Accounts program before you can use it. Contact your Anchorage Digital account representative to start that review.

Once you're approved, we provision your FBO wallet, which can create passthrough virtual accounts. We also give you the `affiliateId` you'll pass when you create each customer.

Your API key needs two permissions:

| Permission | Used for |
| :- | :- |
| Onboarding | Creating and submitting customers |
| Virtual accounts | Creating and reading virtual accounts |

Grant **Virtual accounts** on the vault that holds your FBO wallet.

See [Permission groups](https://docs.anchorage.com/knowledge-base/platform/developers/permission-groups.md) to assign them, and [API keys](https://docs.anchorage.com/knowledge-base/platform/developers/api-keys.md) to create a key.

## How customers work

You create a customer with two API calls: one to begin the customer's application, and one to submit it. Because Named Virtual Accounts run on a reliance model, we rely on your own customer due diligence. A submitted customer is approved right away, with no separate screening step at Anchorage Digital.

Once a customer is approved, you can create virtual accounts for them. See [Create customers](https://docs.anchorage.com/knowledge-base/platform/developers/named-virtual-accounts/named-virtual-accounts-create-customers.md) and [Create virtual accounts](https://docs.anchorage.com/knowledge-base/platform/developers/named-virtual-accounts/named-virtual-accounts-create-virtual-accounts.md) for the full flow.

## How virtual accounts work

Every virtual account is a **passthrough** virtual account. It carries deposit instructions in your customer's name, and deposits to it settle into your FBO wallet.

A virtual account doesn't hold a balance. Funds sit in your FBO wallet, and your own ledger is the source of truth for what each customer holds, so reconciling deposits and withdrawals against each customer stays with you.

To receive funds, share a virtual account's bank details. See [Deposit](https://docs.anchorage.com/knowledge-base/platform/developers/named-virtual-accounts/named-virtual-accounts-deposit.md). To send funds, use the Transfers API with the virtual account's ID. See [Withdraw](https://docs.anchorage.com/knowledge-base/platform/developers/named-virtual-accounts/named-virtual-accounts-withdraw.md).

## Reconcile activity

Each fiat transaction on your FBO wallet carries the virtual account and customer it belongs to, so you can match it to your ledger.

* [`GET /v2/transactions`](https://docs.anchorage.com/knowledge-base/api-reference/v2/transactions/list-transactions) returns `virtualAccountId` and `customerId`. Transfers to another virtual account also carry `destinationVirtualAccountId`.
* Filter with `virtualAccountId` for one virtual account, or with `customerId` for one customer's virtual accounts.
* [Webhooks](https://docs.anchorage.com/knowledge-base/platform/developers/webhooks/webhooks-overview.md) for deposits, withdrawals, transfers, and ACH debits carry `virtualAccountId`.


## Related topics

- [Overview](https://docs.anchorage.com/knowledge-base/platform/developers/move-money/overview.md)
