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.

LiveAdmin portal, money queue411 settled
Money
Money queue
Accounts
Transactions
Reconciliation
Compliance
Applications
Cases
Screening
Risk
Institution
Safeguarding
Reporting
Staff
Money Queue
Settled today
2,841,902.44EUR
411 instructions
In flight
118,420.30EUR
9 instructions
Held for review
2,400.00EUR
1 instruction
Safeguarding buffer
94,120.00EUR
Requirement met
CounterpartyAccountAmountStatus
Hanseatic Werke GmbHDE893000-48,250.00EURSettled
Northwind Trading LtdGB296819126,400.00GBPSettled
Van Dijk Logistiek BVNL914300-9,120.55EURSubmittedSettled
Atelier Rouvier SARLFR142606-2,400.00EURHeld review
Clonmel Foods DACIE29567873,890.10EURApproved
Most recent 5 of 1,284

What 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 R2

Product accounts with per-currency wallets, opened through either portal, with balances projected from entries rather than stored and corrected.

Payment Accounts

C2 K9 M1

Accounts 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 M4

An 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 M5

Wallets per currency on one account, and conversion between them priced and posted as a transaction like any other.

Direct Debit and Mandates

M7

Mandates held against a party, with collections, returns and mandate lifecycle.

Card Acquiring

M6

Acquiring integration, merchant settlement, and scheme files reconciled against your own ledger.

Digital Assets

M8 K13

Digital assets ledgered beside fiat on the same book, with Travel Rule obligations run as a control rather than bolted on.

Fees and Pricing

R3

Tariffs, 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.

LivePosting a transferBalanced
AccountSideAmount
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
Sum, per currency
Balanced
0.00EUR
RefusedThe same four entries with the fee credit removed. The set sums to 12.50EUR and 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.

LivePipeline evaluation, party 88411 case opened
idv.verify
INLINE
412 ms
Pass
sanctions.screen
INLINE
230 ms
Pass
kyb.structure
INLINE
918 ms
Review
risk.input
INLINE
64 ms
Pass
risk.appetite
INLINE
88 ms
Pass
limits.check
CACHED
31 ms
Pass
customer.standing
CACHED
22 ms
Pass
Case openedOne case against 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.

LiveDaily safeguarding reconciliationRequirement met
Safeguarded balances against the requirementMet, with a buffer
Safeguarding requirement
3,418,220.55EUR
Held in safeguarded accounts
3,512,340.55EUR

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

49

Across eight families, in the order money moves.

In Every Deployment

31

The 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

29

Transaction Families

9

UI Components

131

API Endpoints

114

Frequently Asked Questions

Do we deploy this ourselves, or do you run it?
You deploy it. Corlayr is software: it runs in your infrastructure, your customers' data stays in your database in the jurisdiction you chose, and we have no route into it. That also means we are not a banking partner sitting in the middle of your business.
Can we buy part of it?
Yes. Thirty-one modules are in every deployment because the rest depend on them; the other eighteen are licensable. An institution that does not acquire cards does not carry card acquiring.
What does it cost?
It depends on which modules you take and how many entities you run. There is no per-transaction fee, because a core banking system that charges you more for succeeding is a system you will eventually want to leave.
Can we extend it?
Both portals are built on the same public API an integrator gets, so there is no privileged internal route. Controls, questionnaires and risk cards are configuration rather than code, and provider integrations are a declared capability with an adapter behind it.
How do we get our existing book onto it?
Through the same API, with the ledger in manual mode while the rails are still being connected. An officer books the movement, the ledger posts it, and when the rail is live the identical entry is produced automatically. There is no cutover weekend.
Will this survive an audit?
That is what it is built for. Every state change is hash-chained and append-only, the database refuses an update on the evidence table, and the chain head is anchored outside the system. An examiner asking what a record said at a point in time gets an answer rather than a reconstruction.

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.

LiveForty-five minutesOn your own data
  1. 01Post your own entries and watch the balance follow
  2. 02Run your thresholds until one of them refuses
  3. 03Open the case that refusal creates, and resolve it
  4. 04Take the console and try to change the record