Three primitives.
One ledger.
Issuing, acquiring and money movement — composed against a single canonical ledger. Take one, or all three; every program and every rail reconciles to the same truth.
- 01→Issuing
Compose the program. Don't integrate a processor.
Credit, debit, prepaid, fleet, benefit, loyalty — every program on one ledger, with PAN that never crosses your stack. Each program runs the same dual ledger: an authorization side that reconciles to a settlement side, hold-for-hold.
- 02→Acquiring · Payrithm
Become the acquirer, not a hop to one.
Payrithm composes the scheme message itself — a real ISO 8583 or ISO 20022 authorization, as the acquiring participant. One integration for cards, wallets and net-banking. 8 of 21 rails wired today.
- 03→Money movement
Every rail behind one transaction.
ACH, RTP, FedNow, SEPA, Pix and cross-border SWIFT — routed to the cheapest, fastest or most reliable rail, with durable at-most-once egress and one ledger behind all of it.
Composed, not stitched.
One typed model
Cards, authorizations, settlements, ledger entries, disputes and rails — one typed domain model the whole platform reconciles to.
Add-ons inherit it
Kosha, Token Vault, Trust Core, the rules engine and disputes all read and write the same ledger — no adapters, no schema drift.
Deterministic & replayable
Every decision is a typed posting you can replay to the cent — the difference between a ledger and a log.
Pre-GA, by design
We're onboarding design partners. What's wired today is wired honestly; what's designed is labelled as such.