Virtual IBAN

Virtual IBAN Accounts

No scheme membership. One API. Launched under your brand.

Named, dedicated IBANs for your business and your customers — with SEPA and SWIFT rails for collections and payouts, multi-currency balances, and an API that opens accounts programmatically.

  • Dedicated named IBANs
  • SEPA & SWIFT rails
  • Multi-currency balances
  • API-first account opening
NetPay consoleVirtual IBAN / Production Live
Launch checklist
  1. Open accounts via API
  2. Share for collections
  3. Funds auto-reconcile
  4. Hold or pay out
  • PCI DSS Level 1 systems
  • Visa & Mastercard programs
  • 150+ countries
  • 35+ currencies
The problem

Launching payments usually means building a bank first.

The product is rarely the hard part. The dependencies are: scheme membership, a sponsor bank, a certified PCI environment and a stack of vendors, each with its own queue.

  • Scheme membership is a project in itself.

    Going to Visa or Mastercard directly means capital requirements, audits and a sponsor bank before a single card ships.

  • Compliance becomes a second product.

    PCI DSS, KYC, AML monitoring and disputes each need their own people, vendors and audit cycles.

  • Every vendor is another integration.

    Processor, ledger, KYC and payout providers each bring their own API, contract and failure modes.

Run it yourself

One program, two ways to launch it.

Launch virtual iban under your brand
Ready
Building it with a bankIdle: press Launch the program
  1. Apply for card scheme membership
  2. Negotiate a sponsor bank and BIN
  3. Build and certify a PCI DSS environment
  4. Integrate processor, KYC and ledger vendors
  5. Wait for scheme certification

Every dependency sits in another team's queue, and you still own the audits.

Launching it on NetPayIdle: press Launch the program
  1. Open accounts via API
  2. Share for collections
  3. Funds auto-reconcile
  4. Hold or pay out

Same program. One partner, one API and one contract.

Capabilities

Accounts infrastructure without the bank queue

Everything here runs on the same NetPay rails, API and dashboard.

Dedicated named IBANs

Issue IBANs in your customers' or entities' names for credible, self-reconciling collections.

SEPA & SWIFT rails

Receive and send over SEPA for euro payments and SWIFT for global transfers from every IBAN.

Multi-currency balances

Hold and settle in 35+ currencies behind a single account structure.

API-first account opening

Create accounts programmatically as part of your own onboarding flow.

Instant reconciliation

Every inbound payment lands on a unique IBAN, so attribution is automatic — no reference guessing.

Connected to cards

Pair IBAN accounts with card issuing so funds arrive, hold and spend on one platform.

How it works

How virtual IBANs work

A guided path. We carry the regulated heavy lifting so your team ships the product.

  1. Open accounts via API

    Create IBANs for your business, entities or end customers in your flow.

  2. Share for collections

    Customers pay into their dedicated IBAN over SEPA or SWIFT.

  3. Funds auto-reconcile

    Payments map to the right account instantly — webhooks notify your ledger.

  4. Hold or pay out

    Keep multi-currency balances or send payouts from the same accounts.

Who it's for

Built for teams that move money.

  • Fintechs & neobanks
  • Forex brokers
  • Marketplaces & PSPs
  • Remittance companies
  • Crypto platforms
  • Global trading businesses
Talk to our team
Teams using Virtual IBAN
In one sentenceWhat is a virtual IBAN?A virtual IBAN is a bank-account-style identifier that routes payments into an underlying master account while behaving like a dedicated account for the holder. Businesses use virtual IBANs to give every customer, entity or currency its own account number — making incoming payments self-reconciling and enabling named collections and payouts over SEPA and SWIFT without opening separate bank accounts for each need.
How we compare

How NetPay compares.

Every option gets you to a live program eventually. The rows show what each one asks of your team.

Capability NetPayBuild in-houseLegacy processor
Card scheme membership Not needed, we sponsorRequiredUsually required
PCI DSS scope On our Level 1 systemsYours to certifyShared with you
Cards, IBANs and payouts One platformSeparate vendorsCards only
Integration One REST API and webhooksSeveral vendor APIsBatch files, legacy APIs
Sandbox before launch Full sandboxBuild your ownLimited
Your brand Every card, app and statementYesOften co-branded
FAQ

The questions teams actually ask.

Ask our team
What is the difference between a virtual IBAN and a bank account?

A virtual IBAN routes into a master account rather than being a standalone deposit account, but for senders it looks and works like a normal account number. That structure lets a business create many dedicated IBANs quickly — per customer, per currency, per entity — without opening individual bank accounts.

Can I issue IBANs to my end customers?

Yes. The API supports creating dedicated IBANs for your users as part of your product, so each customer gets named account details inside your app.

Which payment rails are supported?

Accounts send and receive over SEPA for euros and SWIFT for international transfers, with settlement support across 35+ currencies.

How does reconciliation work with virtual IBANs?

Because every counterparty pays into a unique IBAN, inbound funds are attributed automatically. Webhooks push credit events to your systems in real time, eliminating manual matching.

Launch virtual iban under your brand.

Tell us what you're building and we'll scope the right program and rails with you.