Solutions Core Banking

Modular, complete core banking.

For banks, fintechs, payment institutions and direct-credit companies (SCDs): the whole operation recorded, controlled, and auditable, in one place.

What is included

Every layer of the operation.

Ledger (Midaz)
Accounts, balances, and the double-entry accounting record of every movement. A complete, immutable history. Multi-currency and multi-asset, natively.
Account structure
Sub-entities created with data independence and financial separation between them.
N:N transactions
Movement across multiple sources and destinations in a single atomic event, for pass-throughs, splits, and settlement between several parties.
Transaction controls
Deterministic verification before every entry, with configurable limits, velocity, and authorization rules.
Fees
Pricing by product, customer, or transaction type, with an accounting entry on every charge.
CRM
Individual and corporate customer data integrated with the accounts, with sensitive fields encrypted.
Reporting
Regulatory, accounting, and operational reports from configurable templates, with filing deadlines tracked.
Interfaces
Pix, boleto, TED, and bill payment integrated with the ledger, through Lerian's own messaging or a third party's.

Migration

Shadow ledger
Lerian's ledger operates alongside your core, mirroring every movement in double entry. Nothing changes for the end customer, and you compare the two side by side.
Phased migration
Once the two match, you start moving: one product, one portfolio or one channel at a time. Whatever has not moved yet stays on your current core, integrated over API and messaging.
Cutover
The legacy is switched off once the whole operation is on Lerian.

Midaz

Published under the Elastic License 2.0, with public code on GitHub.

Go, PostgreSQL, Valkey, RabbitMQ
A stack with no legacy dependencies, scaling horizontally per service.
Versioned REST API
Errors in the RFC 9457 format, idempotent operations by key, bearer token authentication.
Events in CloudEvents
Native publishing on every transaction and state change, consumable by your pipeline.
Atomic balance per account
Race conditions handled at the source, with no table locks and no inconsistency under high concurrency.
Self-reconciliation
A background worker detects and corrects balance drift with no manual intervention.
Official Helm and Terraform
Versioned deployment on Kubernetes, from local environment to production.

Leave your details and Lerian will get in touch to work out the best way to serve your operation.