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

# Cards

> Issue debit cards, decision authorizations in real time, and reconcile transactions against internal accounts.

You can issue debit cards backed by an
internal account, decision authorizations in real time against that
account's balance, and reconcile every pull, clearing, and refund against
the same ledger you already use for payouts.

Cards have no PIN set by default. Until a cardholder sets one, they can enter any PIN at a payment terminal, or skip PIN entry if the terminal allows it.

Once a PIN is set, the cardholder must enter the correct PIN for transactions that use PIN verification. Setting a PIN does not require PIN entry for every purchase; transactions that do not request a PIN continue to work without one.

See [Card PINs](https://docs.lightspark.com/cards/card-management/pins.md) to let cardholders set, change, or unblock a PIN.

![](https://docs.lightspark.com/images/icons/lightning.svg)

Real-time decisioning

Authorizations are checked against the bound internal account at auth
time, so the funding source and the card share a single source of
truth.

![](https://docs.lightspark.com/images/icons/shield.svg)

No PAN in your stack

The full PAN and CVV are rendered directly to the cardholder through
the issuer's iframe. Card credentials never cross your servers.

## Card lifecycle at a glance

A card moves through six states:

| State | Meaning |
| - | - |
| `PENDING_KYC` | Cardholder has not finished KYC; the card cannot transact yet. |
| `PROCESSING` | Card has been requested and is being provisioned with the issuer. |
| `PENDING_AUTH` | Issuer provisioning is complete; USDB Embedded Wallet funding requires delegated signing authorization. |
| `ACTIVE` | Card is live and can authorize transactions. |
| `FROZEN` | Card is temporarily disabled. New authorizations are declined; in-flight settlements continue. |
| `CLOSED` | Card is permanently closed. Terminal, irreversible. |

Every transition emits a `CARD.STATUS_CHANGE` webhook so you can mirror
state changes into your application.

## What's covered in this tab

> [card] [Quickstart](https://docs.lightspark.com/cards/quickstart.md)
>
> Issue your first card, simulate an authorization, and watch it
> reconcile against an internal account.

> [card] [Card management](https://docs.lightspark.com/cards/card-management/issuing-cards.md)
>
> Issue cards, bind a funding source, freeze, unfreeze, and close.

> [card] [Transactions & reconciliation](https://docs.lightspark.com/cards/transactions/reconciliation.md)
>
> The relationship between authorizations, pulls, clearings, and
> refunds — and how to surface exceptions.

> [card] [Sandbox testing](https://docs.lightspark.com/cards/platform-tools/sandbox-testing.md)
>
> Drive deterministic outcomes with the magic-value suffix tables.

> [card] [Card design guidelines](https://docs.lightspark.com/cards/card-design/guidelines.md)
>
> Specs, templates, and rules for designing a physical card and its
> digital wallet art.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.