Balances your users can trust, fiat and crypto side by side
One ledger for every user balance across fiat, stablecoins, and crypto: surfaced in-app in real time, reconciled against custodians, ready for the regulator.
Your app shows a balance. Can you prove it?
User balances derived from provider APIs are a liability.
Fiat sits with a banking partner, crypto with custodians, and the app stitches balances together from API calls. When providers disagree, users see wrong numbers, and safeguarding reviews turn into fire drills.
User balances are stitched from provider APIs instead of owned in one record.
Fiat and crypto live in separate systems that never quite agree.
Card spend, trades, and top-ups race each other, and balances drift.
Safeguarding and proof-of-funds requests require days of manual reconstruction.
_PROOF/ Consumer platforms surface Formance balances in-app: the ledger is the product, not just the back office.
Every user action, one balance
Top-ups, trades, and spend post to the same multi-asset account.
A top-up credits the user, a trade converts between assets atomically, and card spend debits with holds and captures, all against one account tree, reconciled continuously against banking partners and custodians.
See crypto neobanking on a live ledger.
Access a demo of a crypto neobanking flow of funds, on a live Formance ledger. Follow the flow step by step, and deploy the schema to your sandbox.
The primitives consumer platforms need
Built on the open-source Formance ledger.
Multi-asset user accounts, real-time balance queries, and continuous provider reconciliation, composed for consumer scale.
Fiat, stablecoins, and crypto in one account tree per user, with per-asset precision and one aggregated position.
one user, one record
Surface ledger balances directly in-app: the number users see is the system of record, not a cached copy.
ledger-backed UX
Read the API docsCard holds, captures, reversals, and asset conversions modeled as atomic transactions: no race conditions, no drift.
atomic conversions
Reconstruct user funds against segregated accounts at any timestamp, straight from the immutable log.
point-in-time proof
Consumer-grade, by design
A trade is one atomic conversion
Debit one asset, credit the other, capture the fee, together.
A single Numscript transaction converts a user's fiat into crypto and captures the platform fee, with no intermediate state where the user holds neither.
Try it in the PlaygroundTrusted by builders
“Formance enabled us to ship new lending products faster by providing a customizable foundation that let us reliably express the complexities of our flow of funds.”
Embedded finance · reconciliation across 14 countries
See customer story
“Formance is the foundation of our Financial OS, the open-source approach lets us retain control over this key component.”
Healthcare · Financial OS
“Formance helped us kick off our move into fintech, with robust infrastructure and intuitive developer tooling.”
Benefits · fintech infrastructure
Keep going
Everything you need to evaluate and build on Formance.
Crypto neobanking, answered
01 / CAN THE APP READ BALANCES FROM THE LEDGER DIRECTLY?
Yes. Balances are derived in real time from the transaction log and served over the API, so what users see is the system of record itself.
02 / HOW DO FIAT AND CRYPTO COEXIST?
Every asset lives in the same double-entry model with its own precision. A user's position aggregates across assets in one query, with no cross-system joins.
03 / WHAT ABOUT CARD AUTHORIZATIONS?
Holds, captures, reversals, and refunds are first-class transaction patterns, so spend flows post correctly even when settlement lags authorization.
04 / HOW DOES SAFEGUARDING WORK?
User funds map to segregated account trees reconciled against banking partners and custodians continuously: safeguarding reports reproduce for any date.
Ship balances you can stand behind
See how Formance fits your product: book a demo or start building.