Know who paid. Know what it’s for.
Give each payer a number under your USD bank account. Match incoming payments to customers, invoices, and contracts.
- Kestrel Freight•••• 04124,250.00
- Baltra Logistics•••• 037712,900.00
- Indus Textiles•••• 02913,180.00
Who it’s for
- Finance teams collecting from many payers without matching wires by hand
- Platforms reconciling by purpose inside each customer’s own account (third-party funds flow)
A number per purpose, one real account underneath.
CapabilitiesGive payers clear instructions and your finance team a payment reference that carries through to the ledger.
One place for the balance
Each number sits under a USD bank account titled to its owner.
A reference your payer can reuse
One number per payer, contract, or invoice run. The number is the reference.
The same receiving rails
The payer uses any rail the parent account supports.
From issued number to cash applied.
ExampleAn illustrative logistics platform collects freight payments from 200 shippers.
Issue a number per shipper
Assign each shipper a number linked to their customer record.
Share it once
The shipper saves the number as the payee.
Screen the incoming payment
Screening runs first; a flag holds the payment for a named analyst.
Apply the payment
The payment posts against the shipper and identifies the receivable for your finance team.
Two hundred shippers, one screen.
In the consoleMany references. One balance.
A number per purpose. One account underneath.
DevelopersWorkflow example, not executable API code. Integration details are scoped to your account and enabled products.
1. Choose the receiving USD bank account. 2. Assign a virtual account number to a payer or purpose. 3. Share the payment instructions. 4. Match the incoming payment to its reference.
Answers before you ask
FAQAren’t virtual accounts the pooled structure Infinite argues against?
The glossary describes a provider holding many customers’ money under virtual numbers in its own name. On Infinite the account underneath is a real USD bank account titled to its owner, and a customer whose money it is gets their own. Virtual accounts reconcile payments within an account; they don’t replace one.
Is the payer screened?
Yes, before funds move, the same way a payout recipient is: sanctions and watchlists, the network’s own counterparty record, and a hold for a named analyst when something trips. The checks are described on Stablecoin Compliance.
When should I open a USD bank account instead?
When the balance belongs to someone else: that customer gets their own USD bank account under third-party funds flow. Virtual accounts reconcile inbound payments, per purpose, into an account whose balance is yours (or a customer’s own account).
How do virtual accounts relate to payment links?
A virtual account is a standing number a payer keeps paying; a payment link is a one-off request for a set amount. Both reconcile into the same USD bank account.
What happens to a payment that does not match?
A payment into a virtual account always carries its purpose, so it can’t go unmatched. One that trips screening or hits a closed number holds for your team.