_NEOBANKS/

The ledger behind the balance

Own your users' balances instead of renting them from a BaaS provider: real-time accounts, card flows, and safeguarding proofs on one system of record.

Book a demo Start building

deposit

user account

card spend

bank partner

_TRUSTED BY TEAMS MOVING MONEY/

_THE PROBLEM/

Your provider owns your source of truth

A neobank that cannot compute its own balances is an interface, not a bank.

Balances live in the BaaS platform, card events arrive out of order, and your database is a best-effort mirror. Every provider migration, product launch, and safeguarding review runs into the same wall: the record is not yours.

User balances are a mirror of provider APIs, not a record you own and can prove.

Authorization, settlement, and refund events race each other and drift out of order.

New products (pots, joint accounts, interest) wait on provider roadmaps.

Safeguarding reconciliations against the bank partner are manual and month-end.

_PROOF/ Neobanks run user accounts on Formance and surface ledger balances directly in-app.

_FLOW OF FUNDS/

Every account event, one record

Top-ups, card spend, and transfers post to accounts you own.

Deposits credit the user, card authorizations hold funds, captures settle them, and internal transfers move instantly, all in your ledger, reconciled continuously against the banking partner's statements.

safeguarding

deposittop-up in

user accountyour ledger

card spendhold → capture

bank partnerreconciled

_CAPABILITIES/

The primitives neobanks need

Built on the open-source Formance ledger.

Owned user accounts, card-native transaction patterns, and continuous partner reconciliation, composed for consumer banking.

_USER ACCOUNTS/

Balances derived from your own immutable log: real-time in-app, exact at any timestamp, independent of any provider.

provider-independent

_CARD FLOWS/

Authorizations, captures, reversals, and refunds as first-class patterns that stay consistent even out of order.

hold → capture native

_PRODUCT VELOCITY/

Pots, joint accounts, interest, and rewards modeled in Numscript: launch account features without waiting on a provider.

features in days

Read the Numscript docs

_PARTNER RECONCILIATION/

Continuous matching against bank partner statements with drift alerts, so safeguarding is a query, not a quarter-end project.

continuous safeguarding

_BY THE NUMBERS/

Banking-grade, by design

user balancesreal-timein-app · ledger-backed

transactions per second1000ssustained · per ledger

safeguarding reconciliationcontinuousdrift alerts

to launch account featuresdaysNumscript-modeled

_NUMSCRIPT/

A card authorization is a hold, not a guess

Reserve the funds now, settle the exact amount later.

An authorization moves funds into a hold account atomically; capture settles the final amount and releases the difference: no negative balances, no race conditions.

authorize.num

// Hold funds for a card authorization
vars {
  account $user
  monetary $auth_amount
}

send $auth_amount (
  source = $user
  destination = @holds:$user
)

// Later: capture settles from the hold,
// the remainder releases back to the user

_VOICES/

Trusted 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

_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/

_RESOURCES/

Keep going

Everything you need to evaluate and build on Formance.

_DOCS/

Read the documentation

Architecture guides, the Ledger and Connectivity references, and step-by-step quickstarts to ship in days.

_NUMSCRIPT/

Try Numscript

Model any flow of funds as deterministic, auditable transactions. Experiment live in the playground.

_STORIES/

Customer stories

See how fintechs, marketplaces and platforms run money movement on Formance in production.

FAQ

Neobank infrastructure, answered

01 / DOES FORMANCE REPLACE OUR BAAS PROVIDER?

No: it sits underneath as your system of record. Providers keep moving the money; you own the balances, the history, and the ability to switch.

02 / HOW DO OUT-OF-ORDER CARD EVENTS RESOLVE?

Holds, captures, reversals, and refunds are modeled as explicit transaction states, so late or duplicated webhooks reconcile deterministically instead of corrupting balances.

03 / CAN WE SURFACE LEDGER BALANCES IN THE APP?

Yes: balances are derived in real time and served over the API. What the user sees is the record itself, not a cache that drifts.

04 / HOW DOES SAFEGUARDING REPORTING WORK?

User funds map to segregated account trees reconciled continuously against partner statements. Safeguarding reports reproduce for any date from the immutable log.

_GET STARTED/

Own the record behind your product

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

Book a demo Start building