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

# Create a card

> Issue cards backed by the user's Agentcard wallet — verify identity, wire up the agent, and fund the balance.

The create card flow issues virtual cards backed by the user's own Agentcard
wallet balance. It's the path for **multi-use cards** and for users whose bank
card can't be [attached](/companies/guides/attach-card-overview) — the user
verifies their identity once, tops up their wallet, and their agent creates
cards against that balance.

Because real money sits in the wallet, this path requires identity
verification (KYC) before funding. Both happen inside your own app — you build
the screens, Agentcard runs the checks and the payment.

## The flow you implement

Four steps, in order. Each page contains a paste-ready instruction block for
your coding agent plus the underlying API calls.

<Steps>
  <Step title="User authentication">
    Connect the user to Agentcard from inside your own app. Your backend
    triggers a one-time code and receives the user's `user_id` and connection
    tokens — no redirects, no hosted sign-in page.
    [Implement user authentication →](/companies/api/user-authentication)
  </Step>

  <Step title="KYC">
    Verify the user's identity: upload the front and back of their ID, confirm
    the extracted details, and run a short face scan. Ask for the ID photos
    first — the upload responses prefill the details form.
    [Implement identity verification →](/companies/api/identity-verification)
  </Step>

  <Step title="MCP server">
    Point your agent at the Agentcard MCP server with the user's connection
    token. The card tools load automatically — `create_card` issues cards
    against the wallet balance.
    [Wire up the MCP server →](/companies/guides/mcp-server)
  </Step>

  <Step title="Funding a wallet">
    When the balance is short, create a funding session and hand the user a
    checkout link — Apple Pay, Google Pay, or card. Funding reuses the
    completed KYC; an unverified user is refused with `kyc_required`.
    [Implement wallet funding →](/companies/guides/funding-a-wallet)
  </Step>
</Steps>

## When to use which flow

Use **create card** for balance-funded spending: multi-use cards, prepaid
spend limits, or users without an eligible bank card. If the user can share an
eligible **US-issued consumer Visa** or consumer **Mastercard**, the
[attach flow](/companies/guides/attach-card-overview) skips KYC and funding
entirely.

Everything works in test mode first — simulated identity verdicts, simulated
funding, no real money. See [Testing cards in staging](/companies/testing).