Kordio Ledger · Payment service providers

Ship the money core under your PSP stack.

For PSPs · gateways · acquirers · orchestration layers

Merchant balances, acquirer settlement, and reconciliation in one balanced journal, so every downstream system reads the same numbers instead of six vendors' versions of them.
  • Balanced by construction
  • Append-only journal
  • Multi-asset, multi-currency
Card payment at a terminal

This is Kordio Ledger, the record half of the platform. Kordio Control decides what your software may spend before it spends; the ledger keeps the books for what it did.

The friction

Where PSPs hit the ledger wall.

  1. 01

    Merchant balances live in six places.

    Acquirer batch files, gateway logs, treasury sheets, ops CSVs. None of them agree on the same day.

  2. 02

    Reconciliation is a spreadsheet job.

    Bank settlement, gateway captures, and merchant payouts get matched by hand at every close.

  3. 03

    Every new rail is another Postgres table.

    A new BIN sponsor, a new stablecoin, a new correspondent bank: each gets its own homegrown balances table, and none of them balance.

Why Kordio

Built for the way PSPs actually operate.

One ledger, every rail.
Bank ACH, card acquirer, and stablecoin flows land in one balanced journal, with per-currency invariants enforced at write time.
Merchant balances always current.
Merchant balances update the moment a posting commits, so the number you show is authoritative even at peak volume.
Reconciliation as a first-class primitive.
Load the acquirer's settlement snapshot, match against postings, mark reconciled. Runs are replayable if the numbers ever shift.

By the numbers

What "always balanced" looks like.

$0
Sandbox plan
100%
Balance invariants
5min
Signup to first API call
1API
Integration

Where to go next

Three questions, in the order people ask them.

Everything above is the ledger applied to payment service providers. These are the pages that answer whether it is right for you, and what it costs if it is.
What the ledger does
Balanced postings, reconciliation against what actually cleared, period close, and the reports finance asks for.
Build it, or buy it
When writing your own is the right call, the five signals it has run out, and the eight things that cost more than the schema.
What it costs
Priced on postings a month, not on seats. Free in test mode with no card, and every number published.

Ship a ledger you don't have to maintain.

One API. The journal is our problem to run. Your ops team gets their weekends back.