string|IO
Issuing

Compose the program.
Don't integrate a processor.

Credit, debit, prepaid, fleet, benefit, loyalty — every program composed 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.

string|IOcredit · virtual
4929 •••• •••• 1729
A. RIVERAvalid 04/29

Programs are composed, not bought.

Express controls, limits, MCC locks and earn rules as data — issue virtual instantly, physical on the same model. The cardholder ledger reconciles auth-side to settlement-side on every cycle, so the balance you show is the balance that's true.

Every program type

Credit, debit, prepaid, fleet & fuel, benefit (HSA/FSA/LSA), loyalty and co-brand — one ledger underneath all of them.

PAN never crosses your stack

Tokenized at the edge by Kosha — you hold tokens, not PANs, and your PCI scope shrinks with you.

Auth ↔ settlement

Every program runs the dual ledger: held funds reconcile to cleared, hold-for-hold, with no drift between the two sides.

Controls as code

Limits, MCC locks, velocity and earn rules expressed as data — change behaviour without filing a ticket.

Compose your program.