IBAN Services · Gemba via financeb2b
Dedicated IBANs so your international counterparties pay you like a local.
Get a UK sort code and account number, a Eurozone IBAN, and a US routing number — all linked to one Gemba business account. Unlimited virtual IBANs for client or project segregation.
3
primary account types (GBP, EUR, USD)
∞
virtual IBANs per account
Real-time
webhook notifications per receipt
FCA
authorised · FRN 804853
§ 01 — Account types
Three primary receiving accounts
Each Gemba business account comes with GBP, EUR, and USD account details by default. These are dedicated to your entity — not shared with other customers.
GBP Account
UK Sort Code + Account Number
20-00-00 · 12345678
- ✓ Faster Payments (in/out, instant)
- ✓ BACS Credit (receive salary, invoices)
- ✓ BACS Direct Debit origination
- ✓ CHAPS same-day high-value
- ✓ Virtual IBANs available on top
EUR Account
IBAN (GB-prefix, SEPA-eligible)
GB29 NWBK 6016 1331 9268 19
- ✓ SEPA Credit Transfer (receive D+1)
- ✓ SCT Instant (near-instant receipt)
- ✓ SEPA Direct Debit (SDD Core)
- ✓ SWIFT inbound (EUR)
- ✓ Virtual IBANs in EUR available
USD Account
US Routing + Account Number
026073150 · 4567890123
- ✓ ACH Credit (receive from US payers)
- ✓ Fedwire domestic wire receipt
- ✓ SWIFT inbound (USD)
- ✓ Marketplace payouts (Amazon US, etc.)
- ✗ ACH Debit origination — not supported
Account numbers shown are illustrative examples only. Your actual account details are issued upon onboarding.
§ 02 — Virtual IBANs
Unlimited virtual IBANs for client, project, or entity segregation
A virtual IBAN (vIBAN) is a unique account identifier that routes inbound payments to your master account, tagged with the vIBAN reference. You can issue as many as you need.
| Feature | Specification | Detail |
|---|---|---|
| vIBAN Setup | ||
Issuance |
Instant · API or dashboard | Create a vIBAN in seconds from the Gemba dashboard. Assign a label (client name, project code, entity name). The vIBAN is immediately live for receiving payments. |
Quantity limit |
Unlimited | No hard limit on the number of vIBANs per account. Suitable for payroll bureaus with hundreds of employer clients or e-commerce businesses with multiple storefronts. |
Currencies available |
GBP · EUR | GBP vIBANs have dedicated sort code + account number. EUR vIBANs have dedicated IBAN. USD vIBANs are on request — contact financeb2b for availability. |
| Payment Identification | ||
Webhook on receipt |
Real-time · API | Each inbound payment triggers a webhook containing: vIBAN identifier, sender name, sender account, amount, currency, timestamp, payment reference. Plug directly into your reconciliation system. |
Dashboard visibility |
Per vIBAN filter | Filter transaction history by vIBAN in the Gemba dashboard. Export by vIBAN for client reporting or audit purposes. |
Sender information |
Full originator detail | Inbound Faster Payments and SEPA payments include originator name and account details in the webhook payload. BACS credits include Bacs reference field. |
| Fund Flow | ||
Settlement destination |
Master account wallet | All vIBAN receipts settle into your master GBP or EUR wallet. Funds are not siloed — vIBANs are identification layers, not separate accounts. Check if this meets your client money separation requirements. |
Automated sweeps |
Via API | Use the Gemba API to trigger automated payments from the master account based on vIBAN receipt webhooks. Example: client payment received → auto-trigger payroll payout batch. |
§ 03 — Use cases
Who uses dedicated and virtual IBANs
Use case A
Payroll bureaus — one vIBAN per client
Issue a dedicated UK account (sort code + number) to each employer client. Clients fund their payroll by transferring to "their" account. The webhook tags each receipt with the client identifier. You reconcile automatically without manual bank statement matching. Scales from 10 clients to 1,000+ without additional overhead.
Use case B
E-commerce — one vIBAN per marketplace
Receive Amazon UK payouts to one account, Amazon DE to a EUR vIBAN, eBay US to your USD account. Each marketplace deposits to a distinct account identifier — no guesswork about which platform sent what. Eliminates the need for separate bank accounts across multiple markets.
Use case C
Accounting firms — one vIBAN per entity
Manage incoming payments for multiple client entities through a single Gemba account. Each entity has its own receiving account details. Client funds are identified, tagged, and reportable separately — without operating separate bank accounts for each client.
Use case D
Software platforms — embed via API
Platforms can programmatically create vIBANs for their end customers via the Gemba API. Each platform customer gets a unique receiving account. Inbound payments route through to your master account with customer ID tagging. Enables embedded banking features without a full banking licence.
§ 04 — Important limitations
Three things that trip people up
01
vIBANs aren't separate legal accounts
A virtual IBAN is an identification layer — it routes to your master account. This means funds from multiple vIBANs commingle in your master wallet. If you need strict legal separation of client funds (e.g., for FCA-regulated client money rules, or solicitor accounts), vIBANs alone don't satisfy that requirement. You need separate Gemba accounts or confirmation from your compliance team that commingled vIBANs meet your specific obligations.
02
IBAN discrimination in EU
Your EUR IBAN has a GB prefix. Under EU regulations (SEPA Payment Accounts Directive), payers cannot legally reject payments solely because of the IBAN country prefix. But some European businesses — particularly in Germany and Netherlands — still do so in practice, often due to outdated systems or misunderstanding of the rules. Technically illegal but it happens. Worth flagging to EU counterparties if they have trouble accepting your IBAN.
03
Outbound payments use master account
Virtual IBANs are receive-only. You cannot send a payment "from" a vIBAN — all outbound payments originate from your master account (or whichever wallet you choose). The sending account reference your counterparty sees will be your main Gemba account details, not the vIBAN. If you need outbound payments to appear to originate from a specific sub-account identifier, that's a separate discussion about how the payment reference field is used.
Get your dedicated GBP, EUR, and USD accounts.
Plus unlimited virtual IBANs from day one. Onboarding takes 3–5 days.