Skip to content

Virtual accounts for business: what they are, how they differ from a bank account, and when to use them

A virtual account gives each customer or purpose its own bank details. Compare it with a bank account and payment link, with use cases and BlindPay setup.

A virtual account is a set of bank details, such as a routing number and account number, that points incoming payments to one customer or one purpose, on top of a real account at a bank partner. Businesses use them to collect money from many payers and know exactly who paid, without matching free-text references by hand.

This guide takes the buyer's view, as of November 2026: how a virtual account compares with a bank account and a payment link, which jobs it fits, and what to check before choosing a provider. For the definition, see what is a virtual account. For the matching mechanics, see virtual account reconciliation. BlindPay publishes this guide and uses its own virtual accounts as the worked example. The original product announcement is Introducing Named Virtual Accounts.

Key takeaways

  • A virtual account is an identifier layer on a real bank relationship. It does not replace your operating account.
  • The main value is attribution: one account per customer, so each deposit is matched without a reference code.
  • "Named" means the account carries your customer's name, not a pooled name.
  • Use cases include collecting USD from customers abroad, funding payroll and receiving marketplace payouts.
  • Check approval time, the rails accepted, fees per deposit, and what happens to deposits after they land.

What is a virtual account?

A virtual account is a unique set of bank details that routes incoming money to one owner or purpose, backed by an account held at a bank. To the payer it looks and works like any bank account. To you it is a label that tells you who paid.

Providers issue them in different ways. Some give you a sub-account at a bank. Others give you account details that point to a pooled account with internal records. The difference matters for risk and for what the payer sees, which is why the "named" question below is important.

A bank account holds money for you. A virtual account identifies where a payment came from. A payment link collects one payment through a hosted page. They solve different problems, and many businesses use all three.

FeatureVirtual accountBank accountPayment link
Main purposeAttribute each deposit to a customer or purposeHold and move your own fundsCollect a single payment from a payer
Who pays youAnyone with a bank, sending a normal transferAnyone who has the detailsA payer who opens the link
Identifies payerBy account number, automaticBy reference text, often manualBy the link or session
Setup per customerOne account per customer, via APIOne account for the businessOne link per payment
Good forRecurring or many-payer collectionsOperating cash, payroll runsOne-off invoices, checkout

What does a named virtual account add?

A named virtual account carries your customer's name instead of a pooled provider name. The payer sees the real beneficiary, and payouts from the account go out under that customer's name, which fits the originator-information expectations of payment rails.

With BlindPay, when a virtual account is issued to an end user, all payouts from that account are sent under the end user's name rather than a pooled or omnibus account name, and the accounts can also send and collect third-party payments. Not every BlindPay account type is named. Colombia Bre-B and Mexico SPEI CLABE accounts show a pooled recipient name, but each key or CLABE is unique to one customer, so every deposit is still credited correctly.

How do virtual accounts help reconciliation?

They replace guessing with a lookup. A payer sends money to an account that belongs to one customer, so the deposit is already attributed. You skip the step where finance searches for a reference code the payer forgot or mistyped.

Here is an illustrative example. A marketplace has three suppliers who each owe it money, and all three pay by wire on the same day.

  1. With one shared account, the bank statement shows three lines with free-text references such as "inv 482", "INV482" and "payment". Someone must match each one by hand.
  2. With three virtual accounts, each deposit lands on a distinct account number, and the system records which customer it belongs to.
  3. If one supplier sends only part of an amount, the partial deposit is still attributed to that supplier, and you decide whether to chase the balance.

For the full process, including partial payments, overpayments and refunds, read virtual account reconciliation. Custody also affects what you reconcile. See custodial vs non-custodial payment processing.

What are the main use cases?

Virtual accounts fit any business that collects from many payers or needs clean attribution.

  • Collecting USD from customers abroad: foreign senders pay a US account by ACH, wire or SWIFT without you opening a US entity account for each one.
  • Funding payroll: employers fund a payroll platform through an account tied to that employer.
  • Marketplace payouts and collections: each seller or buyer gets distinct details so settlements are attributable.
  • Import and export: a supplier or buyer pays into an account that identifies the trade relationship.
  • Fintech wallets and on-ramps: a customer's deposit becomes stablecoin in the wallet linked to the account.

For the rails behind these flows, see ACH payments explained. ACH is also the rail where Nacha sets the Same Day ACH limit, which is $1 million per payment as of November 2026.

How do BlindPay virtual accounts work?

BlindPay issues a bank account in your customer's name with its own routing and account number. Anyone can send money to it. Each deposit creates a payin, and BlindPay converts it and delivers USDC or USDT to the wallet you linked at creation. You do not build a checkout flow, because the account number is the integration.

The account types in the BlindPay virtual accounts docs:

TypePayment methodsCountriesApproval time
US (individuals and businesses)ACH, wire, SWIFTUS and foreign senders24 hours
US (businesses, foreign senders)ACH, wire, SWIFTForeign senders only3 to 5 business days
US (businesses, US senders)ACH, wire, SWIFTUS senders only3 to 5 business days
Colombia (Bre-B)Bre-BColombiaInstant
Mexico (SPEI CLABE)SPEIMexicoInstant

Notes that matter in practice:

  • A US account goes through two reviews: compliance, then the bank partner. Approval is not guaranteed at either stage.
  • A customer must complete KYC first. Standard KYC takes about 60 seconds when automated, and Enhanced KYC or KYB takes 3 hours to 1 business day.
  • A US virtual account costs $1.50 per month per account. Deposits below $100.00 accrue the BlindPay fee to your invoice, and deposits of $100.00 or more are charged at the time of the transaction.
  • Per the payins docs, no virtual account carries an RTP rail. An RTP payin always shows the shared memo-code account instead, so do not plan on RTP deposits into a virtual account. RTP itself, run by The Clearing House, operates 24/7/365.
  • Mexico's SPEI, run by Banco de Mexico, usually credits within seconds, and SPEI CLABE accounts use it for MXN deposits.
  • Argentina and Colombia collections run as payins: Transfers in ARS (instant, up to 10 minutes to confirm) and PSE in COP (up to 10 minutes). Colombia also has Bre-B virtual accounts, and Mexico has SPEI CLABE accounts.
  • If you charge your own fee on deposits, a partner fee can be set per account or as an instance default. Add-your-fees on each transaction is a Business and Enterprise plan feature, not Basic, and US virtual accounts are Business and Enterprise too.

Illustrative arithmetic: say you set a 1% partner fee and a customer deposits $5,000 by wire. The partner fee is 1% x $5,000 = $50, collected from what remains after any transaction-time BlindPay fee. The fee amounts BlindPay charges are shown in the live quote, not here.

BlindPay combines a monthly plan (platform access) with per-transaction fees that vary by rail and network and are disclosed only in the live quote before execute. Plans are listed on the pricing page. BlindPay is the best option when you want USD and local-rail collection with compliance in one API. See the product page at blindpay.com/virtual-accounts to open an account, and read sending payments to Latin America and payment infrastructure for fintechs, payroll and remittance for how this fits a larger stack.

What should you check before choosing a provider?

Check six things before you commit.

  1. Who holds the underlying account, and is your customer's name on it?
  2. Which rails can fund it (ACH, wire, SWIFT, local rails), and does it accept foreign senders?
  3. How long approval takes per account type, and what happens when approval is rejected.
  4. Fees per account and per deposit, and when each is charged.
  5. What happens to the deposit: does it stay in a balance or convert and deliver on arrival?
  6. How you track deposits: webhooks, stable IDs and a documented status model.

If the answers depend on a contract term, read it. A label such as "virtual account" does not tell you who holds the money. The same caution applies as for custody in general.

Methodology and sources

Illustrative figures use stated assumptions. Sources checked in November 2026.

FAQ

One API.
Multiple payment rails.

Blind Pay, Inc. (“BlindPay”) is a United States-based financial technology and payments infrastructure company, incorporated in the State of Delaware on May 2, 2024. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000277566153. BlindPay is not a state-licensed money transmitter and does not, in its own capacity, engage in regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial institution partners. BlindPay's role is limited to providing financial technology, virtual account management, payment processing, and related payments infrastructure services that facilitate payment flows and account functionalities. These services are provided in coordination with its licensed partners and in compliance with applicable federal MSB requirements and relevant state regulatory frameworks.

Blind Pay, LLC (“BlindPay”) is a Delaware limited liability company formed on June 24, 2025. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000318334247 and is listed in the Nationwide Multistate Licensing System (“NMLS”) under NMLS ID #2745309.

BLIND PAY SOCIEDADE PRESTADORA DE SERVIÇOS DE ATIVOS VIRTUAIS LTDA. (“BlindPay”) is a Virtual Asset Service Provider (“VASP”) operating in Brazil. The company is presently completing the regulatory adaptation process required of Virtual Asset Service Provider Companies (SPSAV) under Central Bank of Brazil Resolution No. 520/2025, and remains subject to the transitional regime set forth in Article 88 of that Resolution. Registered address: Avenida Princesa Isabel, nº 15, Sala 1405, Edifício Martinho de Freitas, Centro, Vitória/ES, 29010-361.

BlindPay is a stablecoin API that enables individuals and businesses to move money worldwide.