A dedicated IBAN for every customer you serve.
Give each merchant, client or account its own EUR or GBP account number in its own legal name. Funds arrive in pooled, segregated accounts; the sub-ledger knows exactly whose they are.
Available to verified businesses only.
Issue a virtual IBAN
Sample dataShared account numbers break reconciliation.
- Shared account numbers force payers to type a reference, and a meaningful share of transfers arrive with it missing or wrong.
- Unmatched credits sit in a suspense account until someone investigates by hand.
- Opening a real bank account per customer is slow and does not scale.
Four steps, no manual matching.
Issue
Call POST /collection-accounts with your customer's KYB ID. A virtual IBAN is created and mapped to that customer.
Share
Show the IBAN on invoices, in your dashboard, or in onboarding emails. It never changes.
Receive
The payer sends a SEPA or Faster Payments transfer. Funds land in the pooled account.
Credit
Shield screens the payment, the sub-ledger credits the right account, and credit.settled fires.
Everything you need, nothing you have to build.
EUR and GBP account numbers
EU-issued EUR IBANs and UK GBP account details, from one integration.
Named accounts
Each IBAN is labelled with the account holder's legal name, so payer banks show the right beneficiary.
Instant issuance
Accounts are created synchronously in the API response.
Persistent or one-time
Persistent for customer accounts; one-time for orders (see Checkout).
Per-account rules
First-party-only, min/max amounts, allowed currencies, allowed payer countries.
Freeze and close
Freeze an IBAN instantly; closed IBANs return any later credits automatically.
Statements per account
Daily CAMT.053 and CSV per virtual account.
Hierarchies
Group accounts under merchants, regions or business units for reporting.
Create a collection account
Idempotent POST, synchronous response, signed webhook. Full details in the API reference.
No IBAN is issued before the account holder passes KYB. Every inbound credit passes through Shield before it reaches a balance.
curl https://api.neofin.tech/v1/collection-accounts \
-H "Authorization: Bearer $NEO_API_KEY" \
-H "Idempotency-Key: 7f1c2e4a-9b0d-4c55-a1e3-2d6f0b9c8e11" \
-H "Content-Type: application/json" \
-d '{
"currency": "EUR",
"holder": {
"type": "business",
"legal_name": "Helios Merchants B.V.",
"kyb_id": "kyb_31QZ"
},
"external_ref": "mch_8F2K91",
"rules": {
"first_party_only": true,
"max_credit_amount": 5000000
},
"labels": { "region": "NL" }
}'{
"id": "ca_9Hc2LmQ",
"object": "collection_account",
"status": "active",
"currency": "EUR",
"iban": "FR7630004012773091526107",
"bic": "NEOFFRP1",
"holder": {
"type": "business",
"legal_name": "Helios Merchants B.V.",
"kyb_id": "kyb_31QZ"
},
"external_ref": "mch_8F2K91",
"rules": { "first_party_only": true, "max_credit_amount": 5000000 },
"labels": { "region": "NL" },
"created_at": "2026-11-05T14:02:11Z"
}{
"id": "ev_5Tq81",
"type": "credit.settled",
"created_at": "2026-11-05T14:02:13Z",
"data": {
"id": "cr_2Kd9xZ",
"collection_account": "ca_9Hc2LmQ",
"external_ref": "mch_8F2K91",
"amount": 1240000,
"currency": "EUR",
"rail": "sepa",
"payer": {
"name": "Kestrel Logistics GmbH",
"iban": "DE89 •••• •••• •••• 3000 00",
"country": "DE"
},
"shield": {
"name_match": "exact",
"score": 1.0,
"screening": "clear",
"decision": "accept"
},
"remittance_info": "INV-2291",
"settled_at": "2026-11-05T14:02:13Z"
}
}Questions we get about Collect.
Is this a real IBAN?
Yes. It is a valid, routable IBAN that payers' banks accept like any other. It belongs to a pooled account held with our regulated banking partner, and our ledger attributes funds to your customer.
Whose name appears to the payer?
The account holder name configured on the virtual account. Names are verified against the holder's KYB record before the account is activated.
How many IBANs can I issue?
Launch includes 250 active virtual IBANs and Scale includes 2,500. Institutional plans are unlimited. Additional IBANs are billed per account on Launch and Scale.
Can I issue IBANs to consumers?
No. NEO Collect is offered to verified businesses and to the businesses they serve. Consumer end users are supported only within approved programmes that have passed enhanced due diligence.
What happens if someone pays a closed IBAN?
The credit is returned to the sender and a credit.returned webhook fires with the reason account_closed.
Which payment rails are supported?
SEPA Credit Transfer and SEPA Instant for EUR, Faster Payments for GBP, and BLINC for transfers between BLINC members.
Issue your first virtual IBAN this week.
Sandbox access is immediate. Live accounts follow KYB review of your business.