Product engine
Cards
A card-issuing engine for stablecoin-funded programs. It orchestrates virtual cards across the issuers and processors you choose, integrates tokenization, evaluates each authorization against the spend controls you set, and exposes the card lifecycle through APIs, all on the same ledger as the rest of the stack.
What it includes
- Virtual card orchestration across your programs.
- Issuer and processor connectors, ours or your own.
- Tokenization integration for stored credentials.
- A spend-control rules engine evaluated at authorization.
- Card lifecycle APIs for issue, freeze, replace and close.
On one ledger with the rest of the stack
When an authorization arrives from the processor, the engine evaluates it against your spend-control rules (MCC, geo, velocity, per-card limits) and the available balance on the cardholder's ledger account, then approves or declines on that basis. Because the funding balance is read from the same ledger every other engine posts to, an authorization cannot approve spend the account does not have, and a settled card transaction lands as a posting against that account rather than a number in a separate card system to reconcile later.
The full card lifecycle stays in one place: issue, freeze, replace and close all run through the lifecycle APIs and write to the same record, so a frozen card stops authorizing the moment the state changes and the audit trail for a program reads end to end.