string|IO
FAQ

Questions, answered.

The ones design partners ask first.

What does the dual ledger actually guarantee? +
That a settlement batch closes and pays only when both sides reconcile to zero. Net payable is a derived sum over open items, never a stored, mutable number — so there's nothing to drift, and any cycle replays to the same cent.
Is StringIO live? +
StringIO is pre-GA and onboarding design partners. Much of the platform is wired and tested today (tokenization, the rules engine, disputes); some pieces — like the Trust Core scoring model — are still in design, and we label them that way.
What does "become the acquirer, not a hop" mean? +
Payrithm composes the scheme message itself — a real ISO 8583 or ISO 20022 authorization — as the acquiring participant, rather than forwarding to someone else who does. Eight of a closed twenty-one-rail set are wired today.
How does the PAN stay out of my stack? +
Kosha tokenizes at the edge and Token Vault holds custody, so you work in tokens, not PANs. Revealing a PAN goes through a gated, audited path — which is what shrinks your PCI scope.
Can I take just one primitive? +
Yes. Compose issuing, acquiring or money movement on its own — or all three. They share one ledger, so adding the next one later doesn't mean another reconciliation.

Still curious? Ask.