Dedicated named IBANs
Issue IBANs in your customers' or entities' names for credible, self-reconciling collections.
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.
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.
Going to Visa or Mastercard directly means capital requirements, audits and a sponsor bank before a single card ships.
PCI DSS, KYC, AML monitoring and disputes each need their own people, vendors and audit cycles.
Processor, ledger, KYC and payout providers each bring their own API, contract and failure modes.
Every dependency sits in another team's queue, and you still own the audits.
Same program. One partner, one API and one contract.
Everything here runs on the same NetPay rails, API and dashboard.
Issue IBANs in your customers' or entities' names for credible, self-reconciling collections.
Receive and send over SEPA for euro payments and SWIFT for global transfers from every IBAN.
Hold and settle in 35+ currencies behind a single account structure.
Create accounts programmatically as part of your own onboarding flow.
Every inbound payment lands on a unique IBAN, so attribution is automatic — no reference guessing.
Pair IBAN accounts with card issuing so funds arrive, hold and spend on one platform.
A guided path. We carry the regulated heavy lifting so your team ships the product.
Create IBANs for your business, entities or end customers in your flow.
Customers pay into their dedicated IBAN over SEPA or SWIFT.
Payments map to the right account instantly — webhooks notify your ledger.
Keep multi-currency balances or send payouts from the same accounts.

Every option gets you to a live program eventually. The rows show what each one asks of your team.
| Capability | NetPay | Build in-house | Legacy processor |
|---|---|---|---|
| Card scheme membership | Not needed, we sponsor | Required | Usually required |
| PCI DSS scope | On our Level 1 systems | Yours to certify | Shared with you |
| Cards, IBANs and payouts | One platform | Separate vendors | Cards only |
| Integration | One REST API and webhooks | Several vendor APIs | Batch files, legacy APIs |
| Sandbox before launch | Full sandbox | Build your own | Limited |
| Your brand | Every card, app and statement | Yes | Often co-branded |
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.
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.
Accounts send and receive over SEPA for euros and SWIFT for international transfers, with settlement support across 35+ currencies.
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.
Tell us what you're building and we'll scope the right program and rails with you.