_CRYPTO PAYROLL/

Pay global teams in stablecoins, account for every cent

Run batch payouts across chains and currencies with exactly-once guarantees, attributed float, and books that close themselves.

Book a demo Start building

employer funding

payroll float

batch payout

off-ramp

_TRUSTED BY TEAMS MOVING MONEY/

_THE PROBLEM/

A payroll run is a thousand payments that must all be right

Batch payouts across providers were not designed for retries.

Employer funds arrive in one currency, sit as float across providers, and leave as hundreds of payouts across chains and rails. One failed retry double-pays someone; one missed payout is a support escalation, and the float is earning yield nobody can attribute.

Batch payouts fail partially, and retries risk paying someone twice.

Employer float is scattered across providers with no unified cash position.

Yield earned on float cannot be attributed back to the employers who funded it.

Every payout rail (chains, banks, local partners) has its own integration and its own failure modes.

_PROOF/ Payroll platforms run stablecoin compensation on Formance, every payout exactly-once.

_FLOW OF FUNDS/

One funding, a thousand exact payouts

Employer money in, attributed float, per-employee payouts out.

The employer funds the run, the float holds attributed balances per employer, and the batch fans out to per-employee payouts across rails: each one idempotent, each one traceable back to its funding.

exactly-once payouts

employer fundingrun financed

payroll floatattributed per employer

batch payoutper-employee, idempotent

off-ramplocal currency out

_CAPABILITIES/

The primitives payroll platforms need

Built on the open-source Formance ledger.

Idempotent batch execution, attributed float, and multi-rail payout connectivity, composed for global compensation.

_BATCH PAYOUTS/

Fan a payroll run out to hundreds of payouts, each an idempotent transaction: retries can never double-pay.

exactly-once

_ATTRIBUTED FLOAT/

Track each employer's share of pooled float in real time, including the yield it earns while it waits.

yield attribution

_MULTI-RAIL PAYOUTS/

Pay out over chains, banks, and local partners through one schema: a new corridor is a connector, not a build.

one schema, every rail

_PAYROLL REPORTING/

Reconstruct any run (who was paid what, when, from which funding) at any timestamp, straight from the log.

full run traceability

Read the Numscript docs

_BY THE NUMBERS/

Payroll-grade, by design

every payoutexactly-onceidempotent · replay-safe

float attribution100%per employer · incl. yield

payout railanychains · banks · local partners

run visibilityreal-timeper employee · per run

_NUMSCRIPT/

A payout that cannot double-pay

Idempotent by construction, not by best effort.

Each payout in the run is its own Numscript transaction with a deterministic reference: replaying the batch skips what already executed instead of paying it again.

payout.num

// Pay one employee from the employer's attributed float
vars {
  account $employer
  account $employee
  monetary $net_salary
  monetary $platform_fee
}

send $net_salary (
  source = @float:$employer
  destination = $employee
)

send $platform_fee (
  source = @float:$employer
  destination = @platform:fees
)

_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

Crypto payroll, answered

01 / WHAT HAPPENS IF A BATCH FAILS HALFWAY?

Each payout is an idempotent transaction. Re-running the batch executes only what has not settled: no double pays, no manual diffing of who got paid.

02 / CAN EMPLOYERS SEE THEIR FLOAT?

Yes. Pooled float is sub-ledgered per employer, so every employer's cash position, including the yield it earns, is exact and queryable in real time.

03 / HOW DO CONTRACTOR AND EMPLOYEE FLOWS DIFFER?

Both are transaction patterns on the same ledger: different account trees, withholding logic, and reporting, with the same guarantees underneath.

04 / WHICH PAYOUT RAILS ARE SUPPORTED?

Stablecoin transfers, bank rails, and local payout partners normalize into one schema through Connectivity; adding one is configuration, not code.

_GET STARTED/

Run payroll you can replay safely

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

Book a demo Start building