Card issuing
A Sumvin card is a Visa card issued to a user, funded from a Sumvin-managed smart account, and managed through the Platform API. The conceptual model is three pieces: a card record, a funding wallet, and a state.The pieces
| Piece | Description |
|---|---|
| Card | The issued card itself. Carries identifying metadata — last 4, brand, expiry, state. |
| Funding wallet | A Safe on the card’s chain. Value in the funding wallet is what the card draws on. |
| State | The card’s lifecycle status — active, frozen, lost, stolen, terminated. |
Who manages what
- Partner — drives lifecycle transitions (freeze, unfreeze, report lost, report stolen, activate) through the Platform API. Manages the funding wallet’s balance.
- Sumvin — holds the card record, the state machine, and the binding between the card and its funding wallet.
- Baanx — external card issuer handling the Visa rails. Issuance and the card transaction stream happen at Baanx.
How it composes with other Sumvin primitives
Card state depends on the user’s wider state:- The user’s status must be verified before a card can be issued.
- The funding wallet (a Safe on the card’s chain) must exist and be deployed.
- Balance on the funding wallet is what authorises transactions — there is no credit line on the Sumvin side.
card_setup becomes reachable.
See also
- Card issuing overview — product-level framing
- Card management API — state transitions endpoint by endpoint
- Funding wallets — per-chain Safe setup for cards
- Baanx issuance — the external issuance rail