Skip to main content
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.
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

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.

Customer

An individual or institution you onboard through the API. Each customer gets a customerId that you use to create their virtual accounts.

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: Grant Virtual accounts on the vault that holds your FBO wallet. See Permission groups to assign them, and API keys 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 and Create virtual accounts 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. To send funds, use the Transfers API with the virtual account’s ID. See Withdraw.

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 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 for deposits, withdrawals, transfers, and ACH debits carry virtualAccountId.