Virtual Accounts & vIBAN Architecture for Inbound Collections
Automating straight-through payment reconciliation, customer-specific collection routing, and omnibus balance segregation with virtual accounts.
The Mechanics of Virtual Account Shadow Routing
A sponsor bank issues a routing range (e.g., dedicated routing number or IBAN prefix) that maps directly to the fintech's master account. When an incoming payment hits any virtual account in that range, funds settle into the master account while transaction webhooks pass the specific virtual account number to internal systems.
Managing Virtual Balances vs Master Physical Balances
The internal ledger maintains virtual accounts as individual balance sheets for each customer. The sum of all virtual account balances plus unallocated suspense funds must precisely equal the settled cash balance of the physical omnibus account.
Automated vIBAN Invariant Attestation with the NAYA Proof Engine
The NAYA Proof Engine ingests bank webhook streams and statement files, matches virtual account settlements to internal customer subledgers, and outputs cryptographic proof that physical omnibus funds equal total customer virtual liabilities.
Frequently Asked Questions
Common questions about this topic
QCan Virtual Accounts hold a balance?
Technically, no. The Internal Ledger associated with that Virtual Account holds the balance. The Virtual Account itself is just a "Router" or "Address." The money sits in the Master Account.
QDo vIBANs work for payouts (sending money)?
Yes. When sending money, the bank can "Mask" the sender details. The recipient sees the payment coming from Name: Your Company, with Account: vIBAN-123, even though the funds physically left the Master Account. This prevents the recipient from seeing your main treasury account number.
Get technical insights weekly
Join 4,000+ fintech engineers receiving our best operational patterns.