_ACQUIRING/

Merchant settlement that adds up, every day

Run fee schedules, rolling reserves, and payout cycles on a ledger that keeps every merchant's position exact — through chargebacks, refunds, and everything else.

Book a demo Start building

capture

fee split

reserve

payout

_TRUSTED BY TEAMS MOVING MONEY/

_THE PROBLEM/

A merchant balance is a moving target

Captures, refunds, chargebacks, and reserves all pull in different directions.

Every merchant's payable is captures minus fees, minus refunds, minus chargebacks, minus the rolling reserve, computed across processors and settlement files that disagree. Get it wrong and you pay out money you do not have.

Merchant payables are computed in batch jobs that nobody can audit after the fact.

Fee schedules (per merchant, per method, per volume tier) live in brittle application code.

Chargebacks and refunds land after payout, driving merchant balances negative.

Rolling reserves are tracked in spreadsheets next to the real books.

_PROOF/ Acquirers and payment facilitators run merchant settlement on Formance, every payout derived, never estimated.

_FLOW OF FUNDS/

From shopper capture to merchant payout

Fees, reserve, and payable split at capture: payout is just a query.

Each capture credits the merchant's payable net of fees, sets aside the rolling reserve, and the payout cycle simply pays what the ledger says. Refunds and chargebacks debit the same accounts, so the position is always current.

merchant position

captureshopper payment

fee splitschedule applied

reserverolling hold

payoutmerchant settled

_CAPABILITIES/

The primitives acquirers need

Built on the open-source Formance ledger.

Declarative fee schedules, native reserve management, and processor reconciliation, composed for merchant settlement.

_MERCHANT ACCOUNTS/

A payable position per merchant derived from every capture, refund, and chargeback: exact at any moment, auditable forever.

derived payables

_FEE SCHEDULES/

Per-merchant, per-method, tiered pricing declared in Numscript and applied at capture, not reconstructed in a batch job.

declarative pricing

Read the Numscript docs

_ROLLING RESERVES/

Reserves held, released, and drawn as ledger transactions with their own account trees and release schedules.

native reserves

_PROCESSOR RECONCILIATION/

Settlement files from processors and schemes match continuously against ledger state, with breaks flagged same-day.

same-day breaks

_BY THE NUMBERS/

Settlement-grade, by design

merchant positionsexactreal-time · per merchant

fee scheduleanyper method · tiered

payout cyclesdailyderived · not batch-computed

settlement breakssame-daycontinuous matching

_NUMSCRIPT/

The split happens at capture

Fees and reserve are accounting, not a nightly job.

One Numscript transaction credits the merchant net of the fee schedule and sets aside the rolling reserve; the payout cycle later pays exactly what the ledger holds.

capture.num

// Split a shopper capture: fees, reserve, payable
vars {
  account $merchant
  monetary $captured
}

send $captured (
  source = @world
  destination = {
    2.9% to @platform:fees
    5% to @reserve:$merchant
    remaining to @payable:$merchant
  }
)

_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

Acquiring, answered

01 / HOW ARE CHARGEBACKS HANDLED AFTER PAYOUT?

Chargebacks debit the merchant's payable (or reserve) as ledger transactions. If the position goes negative, it nets against future captures, tracked rather than lost.

02 / CAN FEE SCHEDULES DIFFER PER MERCHANT?

Yes: pricing is declared per merchant, per payment method, and per volume tier, and applied atomically at capture. Changing a schedule is configuration, not a migration.

03 / HOW DO ROLLING RESERVES RELEASE?

Reserves are held in per-merchant accounts with release schedules run as workflows: held, released, and drawn amounts are all auditable ledger history.

04 / WHAT ABOUT MULTIPLE PROCESSORS?

Captures and settlement files from every processor normalize into one schema, so merchant positions aggregate across processors and reconcile continuously.

_GET STARTED/

Pay out what you can prove

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

Book a demo Start building