01The operator console
One screen holds the whole program: 12,480 active vIBANs, €2.4M routed today, 8,912 credits auto-reconciled. Every row shows the IBAN, who it belongs to, its purpose tag, and today's incoming money. Search by IBAN, customer, or reference; export the book as CSV.
- Search across IBAN, customer, and reference
- Status per IBAN — active or paused, at a glance
- One-click CSV export of the full book
02A clean view for the payer
Customers see their own account details: the dedicated IBAN with a copy button, the BIC for transfers from outside SEPA, the bank's name and address, and a share button for whoever pays them. Every transfer to that IBAN lands in their balance already matched to them — the payer never types a reference.
03Bulk issue with a review step
A CSV of 2,400 payers uploads, validates — 2,400 valid, 0 errors — and previews the exact IBAN each row will get, reserved from the range at upload and assigned on issue. Configure the range, purpose tag, and reference prefix, then issue the whole batch in one action. The same operation runs over the API.
- Source, configure, review — with a draft to save between steps
- IBANs reserved up front, so nothing collides on issue
- A webhook per issued vIBAN, toggled per batch
04Statements the finance team opens
The period on screen holds €412,380.44 across 8,912 credits, 99.6% auto-reconciled — with the 34 manual cases and 12 returned payments counted rather than hidden. Every vIBAN exports its own statement as CSV or PDF, the whole period exports in one action, and monthly statements email themselves to the finance inbox on the 1st.
05Webhooks with delivery receipts
Every credit, return, issue, and pause is an event, and every event shows its delivery: status code, latency, and retry state per attempt. Deliveries are signed with HMAC-SHA256 and retried 6 times over 24 hours with exponential backoff — and a delivery that exhausts its retries gets a manual retry button, not a shrug.
- payment.incoming, payment.returned, viban.* — subscribed per endpoint
- Per-endpoint secrets; endpoints pause without being deleted
- 8,946 events in the last 24 h, 99.7% delivered — printed on the page
06The accounts behind the program
In the operator console, the receiving accounts behind the program are data, not tribal knowledge: one active account per currency, and retiring one promotes the next sibling automatically. Every change asks for a written reason and lands in the audit log.
07Per-payer IBANs
Every payer gets a dedicated IBAN, so every incoming payment names its sender before anyone looks at it. There is no reference field to mistype and no matching queue to work through. Identification is a property of the account number, not a process.
Each vIBAN carries a tag: rent-collection, subscriptions, marketplace-payouts, payroll. Flows stay separated at the account level, so reporting by purpose is a filter, not a project.
09Reconciliation by construction
When each payer pays into their own IBAN, an incoming credit can only mean one thing. In the demo period, 99.6% of 8,912 credits reconcile themselves — and the handful that cannot land in a manual queue instead of a mystery.
10One master account
Behind every vIBAN sits one real account. Funds concentrate automatically — no sub-account balances to sweep, no fragmentation to manage. The surface is thousands of addresses; the ledger is one.
11Dedicated IBAN ranges
vIBANs issue from dedicated ranges — the demo program runs under RO49 PRCT, with the free count per range shown at issue time. Ranges keep programs, brands, or entities cleanly separated while everything still routes into the master account.
12Per-payer history
Each vIBAN accumulates its own payment history, so a payer's record is complete by definition. A dispute or an audit starts from a filtered list, not an investigation.
Seller and tenant onboarding can mint a vIBAN as a step in the flow: create the account, hand over the IBAN, start collecting. The customer view ships whitelabel — the demo runs as Powered by Protocore; yours runs under your brand.
14Returns, counted
Some payments bounce — an account closed, details wrong. SEPA returns carry their reason code into a payment.returned event and their own count on the statements page — data with a cause attached, not mysteries. The edge case has a row, not a support thread.
15Pause without ceremony
A vIBAN pauses in one action, and the event stream records who paused it and from where. Paused reads as a status everywhere the IBAN appears — the book, the statements, the stream.
16Drafts before batches
A configured batch saves as a draft: source validated, range picked, nothing issued yet. The flow runs source, configure, review — so the irreversible click is the last one, on purpose.
17Allowances you can plan against
Issuing runs against a monthly allowance with the meter in view, and a batch states what it adds before you run it — 1,204 of 5,000 used, this batch makes it 3,604. Capacity is arithmetic, not an error message.
18Reference prefixes per batch
Each batch stamps its credits with a reference prefix — ARC-PAYOUT- in the demo — so downstream systems recognize their own flows on sight.
19Your ids travel with ours
Every payer row carries an external reference from your system — EXT-00311 in the demo — and it stays attached to the vIBAN. Lookups run on your identifiers, not just ours.
20Console and API are twins
Everything the console does, the API does — issue, pause, query, export. The CSV upload and the API call drive the same operation; the console is a client, not a special path.
21Test events before real money
Send a test event to any endpoint straight from the console. The integration proves itself against synthetic deliveries before the first real credit arrives.
22Endpoints with hygiene
Endpoints carry their own signing secrets and their own subscriptions, and they pause without being deleted — the demo keeps a paused staging endpoint right next to the active production one.
23Exports in two shapes
CSV for machines, PDF for people — per vIBAN or for the whole period. The export is designed to be imported, not re-typed.
24Statements on a schedule
Monthly statements email themselves to the finance address on the 1st. The routine report is a subscription, not a recurring task on someone's list.
25Filter the stream
Events filter by type, vIBAN, or reference; the console book searches by IBAN, customer, or reference. Finding one payment among thousands is a query with three entry points.
26Every change with a reason
Operator changes to the program — accounts, pauses, retirements — are reason-required and land in the audit log. The program's history explains itself in writing.