Skip to content
_CRYPTO PAYMENTS/

Move money through stablecoins without losing the trail

Orchestrate fiat-to-stablecoin-to-fiat corridors as atomic multi-hop flows, with FX, fees, and gas accounted for end to end.

pay-in
on-ramp
corridor
payout
_THE PROBLEM/

The corridor is fast. The accounting is not.

On-chain confirmation is not settlement.

A cross-border payment crosses banks, ramps, and chains, each hop with its own rate, fee, and timing. Hard-coded logic breaks mid-corridor, funds sit in limbo, and no one can trace a cent end to end.

01

Multi-hop flows stall mid-corridor, leaving funds in limbo with no recorded state.

02

FX rates, ramp fees, and gas are hard-coded, so revenue capture breaks at scale.

03

On-chain confirmation gets booked as settlement when fiat has not actually landed.

04

Per-corridor compliance reporting means reconstructing flows across three systems.

_PROOF/ Payment companies run the stablecoin corridor on Formance, every hop posted to one auditable flow.

_FLOW OF FUNDS/

Fiat in, stablecoin across, fiat out

One flow, every hop accounted, end to end.

Pay-in lands in local fiat, the on-ramp converts to stablecoin, the corridor moves value across chains, and the off-ramp pays out in destination currency. Each hop is a double-entry posting in the same traceable flow.

end-to-end traceability
pay-inlocal fiat collected
on-rampfiat → stablecoin
corridorcross-chain transfer
payoutdestination fiat
_CAPABILITIES/

The primitives payment corridors need

Built on the open-source Formance ledger.

Multi-hop orchestration, declarative FX and fee capture, and ramp connectivity, composed for hybrid money movement.

_MULTI-HOP ORCHESTRATION/

Compose corridors as durable workflows: each hop atomic, a failed step reversing the flow safely instead of stranding funds.

atomic, reversible

_FX & FEE CAPTURE/

Conversion rates, spreads, ramp fees, and gas modeled declaratively per hop, so revenue is captured by construction.

declarative capture

Read the Numscript docs
_SETTLEMENT STATES/

Distinguish initiated, confirmed, and settled per rail, so books reflect where money actually is, not where a webhook said it was.

true settlement

_RAMP CONNECTIVITY/

Normalize banks, PSPs, on/off-ramps, and chains into one schema: adding a corridor partner is a connector, not a rewrite.

one schema, every rail

_BY THE NUMBERS/

Corridor-grade, by design

hop traceability100%end-to-end · per corridor
funds in limbo0atomic · reversible flows
rail or chainanybanks · ramps · stablecoins
corridor visibilityreal-timeper hop · per currency
_NUMSCRIPT/

A hop is a transaction, not a webhook

Convert, capture the spread, and move on — atomically.

A single Numscript transaction books the on-ramp conversion: fiat leaves the collection account, stablecoin enters the corridor float, and the FX spread is captured in the same operation.

onramp.num
// Book an on-ramp conversion with FX spread capture
vars {
  monetary $fiat_in
  monetary $stable_out
  monetary $spread
}

// 1. Fiat leaves the pay-in account
send $fiat_in (
  source = @payin:eur
  destination = @ramp:provider
)

// 2. Stablecoin enters the corridor, spread captured
send $stable_out (
  source = @ramp:provider
  destination = @corridor:usdc
)
send $spread (
  source = @ramp:provider
  destination = @platform:fx-revenue
)
_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 payments, answered

01 / WHAT HAPPENS WHEN A HOP FAILS?

Corridors run as durable workflows: each hop is atomic, and a failure reverses the completed legs safely instead of leaving funds stranded between systems.

02 / HOW DO YOU HANDLE ON-CHAIN VS FIAT SETTLEMENT TIMING?

The ledger models settlement states per rail (initiated, confirmed, settled), so a chain confirmation never gets booked as landed fiat.

03 / CAN I TRACE A PAYMENT END TO END?

Yes. Every hop posts to the same flow with shared metadata, so any payment reconstructs from pay-in to payout, for support, compliance, or the regulator.

04 / HOW DO I ADD A NEW CORRIDOR?

Ramps, banks, and chains normalize into one schema. A new corridor partner is a connector configuration, and your flow logic stays untouched.

_GET STARTED/

Corridors you can account for

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