/// vIBAN · Reconciliation

Reconciliation by construction

When every payer pays into their own IBAN, an incoming payment can only mean one thing. The matching problem does not get solved — it stops existing.

1
Master account
Per-payer
Automatic reconciliation
Bulk
IBAN issuing
Tagged
Rent · subs · payouts
/// 01

One account, thousands of addresses

Behind the scenes there is one master account. On the surface, each payer, tenant, or subscriber gets a dedicated virtual IBAN. Money lands in the master account either way — but it arrives pre-labeled with who sent it and what it is for.

/// 02

Built for platforms

Issuing happens in bulk, not one form at a time — a marketplace onboarding a thousand sellers mints a thousand IBANs in one operation. Purpose tags keep flows separated: rent here, subscriptions there, marketplace payouts in their own lane.

  • [ 01 ]Bulk issuing via console or API
  • [ 02 ]Purpose-tagged IBANs for clean flow separation
  • [ 03 ]Per-payer history without a matching engine
/// In the product
The console — every virtual IBAN, tagged and reconciled.
The payer's view — a dedicated IBAN that is theirs alone.
Availability

Available standalone or whitelabel — issue under your brand.

Pick a product. Or take the core.

Everything above runs in production demos we can walk you through — standalone, whitelabel, or as one platform. Tell us what you're building and we'll show you the shortest path to it.

Contact us