Skip to content

/ MENU

  • ops@example.com
01 — Services

Four services.One double-entry core.

Payout rails, treasury, reconciliation and the compliance perimeter — sold as four integrations everywhere else, posted to one ledger here.

/payouts

Payout rails

/balances

Treasury & FX

/ledger

Reconciliation core

/compliance

Risk & compliance

02 — The service ledger

Four lines. Every one of them settles.

Take one service or all four — they post to the same core, so adding the next one is a scope change, not a migration.
/payouts

Payout rails

Push funds to 41 markets over the fastest local rail — Pix, SEPA Instant, FedNow, Faster Payments — from a single balance, with FX locked at quote time and the return code on the webhook.

0.4s

Median settlement

/balances

Treasury & FX

Hold, convert and sweep across 30+ currencies. Available, pending and reserved are separate views on the same balance, and every quote is one your finance team can hedge against.

10 bps

Over mid-market

/ledger

Reconciliation core

Every movement posts twice, as it clears. Statements, journals and audit exports read from the same double-entry core the money moved through — so the close is a query, not a project.

2×

Entries per movement

/compliance

Risk & compliance

KYB, sanctions screening and travel-rule messaging run inline on the payout path. A blocked transfer reverses through the same transaction that created it, so the books never sit unbalanced waiting on a review.

SOC 2

Type II, audited yearly

03 — One surface

Same client. Same core. Every service.

One key, one SDK, one set of webhooks. Adding treasury or compliance does not add a second integration — it adds routes to the one you already ship.
ledger — sandbox

# one call — the rail, the FX and both entries

$ ledger payouts create --amount 250000 --currency BRL --rail pix

202 accepted · quote locked at 5.4210 · fee 0.25%

✓ settled in 0.4s · transfer tr_8842

$ ledger entries list --transfer tr_8842

debit balance:BRL 250,000.00

credit payout:pix 250,000.00

✓ books agree — drift 0.00

04 — What ships with it

The service is the people too.

An API you can read is table stakes. What gets a platform live is the cut-over plan and the engineer who answers on a Saturday.
/01

Named solutions engineer

One engineer on your Slack Connect channel from first sandbox call to production volume — not a queue, not a rotation.

/02

Migration runbook

A cut-over plan per rail, dual-running against your current provider until both ledgers agree to the cent.

/03

Sandbox parity

Sandbox mirrors production rail for rail — including failure codes, cut-off times and return windows you can test against.

/04

24/7 payments ops

People watching the rails, not just the API. Fifteen-minute response on settlement incidents, every day of the year.

05 — Start with one

Take one service to production first.

Most platforms start on payouts and add treasury in the same quarter. Send your flow of funds and we'll map the sequence with you.