Everything a licensed institution runs on, in your own infrastructure.
A white-label core banking system for electronic money institutions, payment institutions and banks. 49 modules on one book of record, with your brand on the admin portal and the client portal.
| Counterparty | Account | Amount | Status |
|---|---|---|---|
| Hanseatic Werke GmbH | DE893000 | -48,250.00EUR | Settled |
| Northwind Trading Ltd | GB296819 | 126,400.00GBP | Settled |
| Van Dijk Logistiek BV | NL914300 | -9,120.55EUR | SubmittedSettled |
| Atelier Rouvier SARL | FR142606 | -2,400.00EUR | Held review |
| Clonmel Foods DAC | IE295678 | 73,890.10EUR | Approved |
Built for the licence you hold.
The obligations differ, the core does not. Each of these is a configuration of one system rather than a separate product with its own data model.
Electronic Money Institutions
Issue e-money, hold client funds, and prove daily that what you safeguard matches what you owe.
For EMIsPayment Institutions
Move money for customers without issuing e-money, with the same evidence trail behind every instruction.
For PIsBanks
A core of record with treasury, a general ledger that ties, and the audit trail an examiner asks for.
For BanksCard Acquirers
Merchant settlement, scheme reconciliation, and fees priced and recorded with the reasoning behind them.
For AcquirersDigital Asset Businesses
Ledger digital assets beside fiat on one book, with Travel Rule obligations handled as a control.
For VASPsMulti-entity Groups
Several licences, several jurisdictions, one operating model and settlement between the entities.
For GroupsWhat you can offer your customers.
The product lines the system supports, above the nine transaction families they are made of. Each one names the modules that do it.
E-money Accounts and Wallets
C1 C2 R2Product accounts with per-currency wallets, opened through either portal, with balances projected from entries rather than stored and corrected.
Payment Accounts
C2 K9 M1Accounts that hold and move money without issuing e-money, with the same ledger, limits and restrictions behind them.
Payments In and Out
M1 M2 M3 M4An instruction state machine with a deadline on every state, suspense and release for money that arrives unattributed, and rail adapters behind it.
Multi-currency and FX
C2 M5Wallets per currency on one account, and conversion between them priced and posted as a transaction like any other.
Direct Debit and Mandates
M7Mandates held against a party, with collections, returns and mandate lifecycle.
Card Acquiring
M6Acquiring integration, merchant settlement, and scheme files reconciled against your own ledger.
Digital Assets
M8 K13Digital assets ledgered beside fiat on the same book, with Travel Rule obligations run as a control rather than bolted on.
Fees and Pricing
R3Tariffs, quotes and charges, with the reasoning behind each charge recorded so you can answer why a customer paid what they paid.
C1 Ledger
An unbalanced entry is not an error to handle. It never exists.
A transfer moves the money and prices it in the same transaction, so the wallet debit, the settlement credit and both sides of the fee post together or not at all. Remove one and the set no longer sums to zero.
What happens then is the point. There is no partial write, nothing queued for the morning, and nothing for an operator to find and reverse. The transaction is refused at commit.
| Account | Side | Amount |
|---|---|---|
Client wallet, Northwind Trading | Debit | -24,500.00EUR |
Settlement, safeguarded | Credit | 24,500.00EUR |
Client wallet, Northwind Trading | Debit | -12.50EUR |
Fee income | Credit | 12.50EUR |
ledger.trial_balance_zero rejects the transaction before it commits. There is no partial write to clean up.K1 and K11
Seven controls, and any one of them can stop the line.
Each returns an outcome the engine records against the evaluation: pass, fail, review, error, skipped or not applicable. A control that could not reach a verdict is an error, and nobody proceeds on the strength of a timeout.
A review opens one case per subject per control, assigns it, and waits for a person with a name. It lapses on its own when the control stops objecting.
kyb.structure, assigned to the compliance queue. One case per subject per control, so a second evaluation adds a sighting rather than a duplicate, and it lapses on its own when the control stops objecting.R2 Safeguarding
Client money, reconciled against what you actually hold.
The requirement is derived from the ledger the payments moved through and compared with the balances in the safeguarding accounts every day. A shortfall arrives as an alert with a figure attached, which is some months earlier than it would otherwise arrive.
The run reports a heartbeat, so a reconciliation that stops raises an alert of its own. A check that silently stopped looks exactly like one that keeps passing.
The run reports a heartbeat. A reconciliation that stops is raised as its own alert by ops.job_heartbeats, because a check that silently stopped running looks exactly like a check that keeps passing.
One system instead of five and a spreadsheet.
Most institutions this size run a ledger in one place, onboarding in another, screening at a vendor, reconciliation in a spreadsheet, and the regulatory return in whatever the consultant sent back. Every join between them is a place the numbers can disagree, and every disagreement is yours to explain.
Corlayr is the join. A control writes to the same evidence store the ledger writes to, the safeguarding figure is derived from the entries the payments made, and the return is computed from the book rather than assembled next to it.
- One book. Balances, safeguarding and the trial balance all replay from the same entries, so they cannot drift apart between reports.
- One record of who did what. An officer’s decision, a control’s outcome and a customer’s answer land in the same hash-chained log.
- One API. Both portals are built on it, so there is nothing an integrator is locked out of that our own screens use.
- One set of tokens. Every surface a customer or an officer sees is themed from the same values.
One book of record
Nothing here is kept in a second place.
Balances, the safeguarding position and the trial balance all replay from one ledger, so they cannot drift apart between one report and the next.
Modules
49Across eight families, in the order money moves.
In Every Deployment
31The other 18 are licensable.
Two portals, one public API.
Both of our own screens are built on the API an integrator gets, so there is no privileged internal route and nothing you are locked out of.
Ledger Tables
29Transaction Families
9UI Components
131API Endpoints
114Frequently Asked Questions
Do we deploy this ourselves, or do you run it?
Can we buy part of it?
What does it cost?
Can we extend it?
How do we get our existing book onto it?
Will this survive an audit?
Book a Demo
Bring your licence conditions. We will go through them.
Forty-five minutes against your own regime and your own transaction set, not a recorded tour of somebody else’s.
- 01Post your own entries and watch the balance follow
- 02Run your thresholds until one of them refuses
- 03Open the case that refusal creates, and resolve it
- 04Take the console and try to change the record