Skip to content
_CRYPTO NEOBANKS/

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.

top-up
user balance
trade / spend
providers
_THE PROBLEM/

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.

01

User balances are stitched from provider APIs instead of owned in one record.

02

Fiat and crypto live in separate systems that never quite agree.

03

Card spend, trades, and top-ups race each other, and balances drift.

04

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.

_FLOW OF FUNDS/

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.

real-time balances
top-upfiat in
user balancemulti-asset account
trade / spendconvert · card
providersbanks · custodians
_CAPABILITIES/

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.

_MULTI-ASSET ACCOUNTS/

Fiat, stablecoins, and crypto in one account tree per user, with per-asset precision and one aggregated position.

one user, one record

_REAL-TIME BALANCE API/

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 docs
_SPEND & TRADE FLOWS/

Card holds, captures, reversals, and asset conversions modeled as atomic transactions: no race conditions, no drift.

atomic conversions

_SAFEGUARDING REPORTS/

Reconstruct user funds against segregated accounts at any timestamp, straight from the immutable log.

point-in-time proof

_BY THE NUMBERS/

Consumer-grade, by design

balance per user1fiat + crypto · unified
in-app balancesreal-timeledger-backed
transactions per second1000ssustained · per ledger
safeguarding history100%immutable · point-in-time
_NUMSCRIPT/

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.

trade.num
// Convert user fiat to BTC with a platform fee
vars {
  account $user
  monetary $eur_amount
  monetary $btc_amount
  monetary $fee
}

// 1. Debit fiat, fee captured
send $eur_amount (
  source = $user
  destination = @trading:float
)
send $fee (
  source = @trading:float
  destination = @platform:fees
)

// 2. Credit the purchased BTC
send $btc_amount (
  source = @trading:btc
  destination = $user
)
_VOICES/

Trusted by builders

LiberisLiberis
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
DoctolibDoctolib
Formance is the foundation of our Financial OS, the open-source approach lets us retain control over this key component.

Healthcare · Financial OS

PayflipPayflip
Formance helped us kick off our move into fintech, with robust infrastructure and intuitive developer tooling.

Benefits · fintech infrastructure

_TRUST/

Built for regulated money.

Enterprise controls, the certifications auditors ask for, and an immutable record, out of the box.

See our trust center
THE COMPLIANCE STACK
IAM, RBAC & SSO
Non-repudiation
Audit logs
Observability & monitoring
Real-time events
Admin console
_AUDIT-LOG/ NON-REPUDIATION

09:41:07Z AUDIT gateway POST /api/ledger/v2/main/transactions 200 sub:ops@acme.io

09:41:09Z LOG id:4093 NEW_TRANSACTION ledger:main

09:41:12Z LOG id:4094 SET_METADATA ledger:main

09:41:15Z LOG id:4095 REVERTED_TRANSACTION ledger:main

09:41:18Z AUDIT gateway GET /api/ledger/v2/main/logs 200 sub:audit@acme.io

CERTIFICATIONS
AICPA SOC IICERTIFIED
ISO 27001CERTIFIED
DORACOMPLIANT
REGULATORY FRAMEWORKS
EMIFCAMTLNYDFS Trust CharterOCC CharterMiCAGENIUS
_ATTESTED/
FAQ

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.

_GET STARTED/

Ship balances you can stand behind

See how Formance fits your product: book a demo or start building.