One balance, many addresses.A spend account can have more than one active virtual account number, and exactly one of them is marked primary. Every VAN on the account credits the same balance — they exist so you can separate senders, such as payroll versus a specific customer, without splitting the funds.
How It Fits Together
Money in arrives through a VAN. Money out still leaves the spend account the same way it always has — gift card and virtual card funding, internal transfers, and withdrawals to a linked external account.Supported Rails
Credits sent to a virtual account number are accepted over four rails:What a Credit Looks Like
When funds arrive at a virtual account number, Fluz records a standard deposit against the destination spend account. The deposit’s funding source is the virtual account — not a bank card, bank account, or PayPal — because the money originated outside Fluz and was pushed in rather than pulled from a linked payment method. This means:- The credit appears in the same transaction and deposit history as any other deposit.
- There is no linked funding source object to reconcile against, and no backup card hold, because nothing was debited from the user.
- The deposit is attributable to the specific VAN that received it, so you can distinguish a payroll credit from a customer payment when a spend account has multiple VANs.
Retrieve a User’s Virtual Account Numbers
UsegetSpendAccountVirtualAccountNumbers to list the active VANs on a spend account. It returns every active VAN, one of which is flagged as primary.
Scope required: LIST_PAYMENT
Variables
Returns
[SpendAccountVirtualAccountNumber!]!. See the type reference for the full field list.
Displaying account numbers.A VAN’s full account number is sensitive. Mask it in list views and reveal the full value only on an explicit user action, the same way you would treat a card PAN. When a user needs to hand the details to a third party, prefer the generated PDF artifacts described in Virtual Account Documents over free-form copy.
Handing the Details to a Third Party
Rather than asking a user to transcribe a routing and account number into a payroll portal or send it to a counterparty by email, Fluz generates PDF artifacts on demand:
All three default to the spend account’s primary VAN when
virtualAccountNumberId is omitted, and all three require the LIST_PAYMENT scope.
See Virtual Account Documents for the full reference.
Requirements
- The user must have at least one active spend account.
- Reading virtual account numbers and generating documents both require the
LIST_PAYMENTscope on the user access token. - Virtual account numbers are provisioned by Fluz. They are not created through the API.
Related
Spend Accounts
The account that actually holds the balance.
Virtual Account Documents
Payment instructions, deposit forms, and status letters.
Deposit Funds
Pull funds in from a linked bank account or card.
Funding Sources
How Fluz classifies the money moving in.
Want to learn more? Speak with our experts for more info or to request a demo.