> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sumvin.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Card issuing

> The conceptual model behind Sumvin's card issuing surface — the card, its funding wallet, and its state.

# Card issuing

**Your** <Tooltip tip="Sumvin's portable, KYC-verified identity — Proof of Personhood." headline="Sigil" cta="Glossary →" href="/glossary">Sigil</Tooltip>**, on a Visa card.** Card issuing is part of <Tooltip tip="Sumvin's payments umbrella: ramps, card issuing, x402, and payment links." headline="Atomic Money" cta="Glossary →" href="/glossary">Atomic Money</Tooltip>, Sumvin's payments umbrella, and runs on **Visa Intelligent Commerce** — a user's verified Sumvin identity carried onto a Visa card, funded directly 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.              |

<Snippet file="product-term-disambiguation.mdx" />

## 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, the binding between the card and its funding wallet, and the binding to the user's Sigil.
* **Visa issuance partner** — the regulated issuer that runs the Visa rails. Issuance and the card transaction stream happen at the issuance partner.

## How it composes with other Sumvin primitives

Card state depends on the user's wider state:

* The user's <Tooltip tip="Know Your Customer — identity verification that feeds attestation claims onto credentials." headline="KYC" cta="Glossary →" href="/glossary">KYC</Tooltip> **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.

This means card issuing sits downstream of the onboarding state machine — the user passes through KYC and wallet creation before `card_setup` becomes reachable.

## See also

* [Card issuing overview](/products/card-issuing/overview) — product-level framing
* [Card management API](/products/card-issuing/card-management-api) — state transitions endpoint by endpoint
* [Funding wallets](/products/card-issuing/funding-wallets) — per-chain Safe setup for cards
* [Visa issuance rail](/products/card-issuing/visa-card-issuance) — the regulated issuance partner behind the Visa rails

## Referenced from

* [Onboarding state machine](/concepts/onboarding-state-machine)
* [Safes and identity](/concepts/safes-and-identity)
* [Crypto wallet card use case](/overview/use-cases/crypto-wallet-card)