Card permissions work anywhere cards are accepted. When your agent needs to buy from a website that does not have an API, it can drive a real browser session and fill in the checkout form with secure card numbers. This guide explains the end-to-end flow: saving a card, giving a card permission, and using a browser automation tool like Stagehand or Browser Use to complete the purchase.Documentation Index
Fetch the complete documentation index at: https://docs.crossmint.com/llms.txt
Use this file to discover all available pages before exploring further.
For supported merchants (Amazon, Shopify stores, US only), use Fast Checkout instead — it is a single API call with no browser needed.
How it works
The key idea: the agent never sees the user’s real card. It receives a scoped card permission — limited by amount, merchant, and duration — and pays using a secure one-time card number. If the card is compromised or the agent misbehaves, the blast radius is contained.Prerequisites
- A saved and verified card. See the Cards setup guide.
- An active card permission (order intent). See Give Card Permission.
- A browser automation tool: Stagehand or Browser Use.
Steps
Save a card and set up a card permission
The user saves their card via Crossmint’s PCI-compliant UI. The card is verified for agentic use, and a card permission is created with spending rules (amount, merchant, duration). The user approves via passkey.For the full setup, see:
Retrieve secure card numbers
When the agent is ready to make a purchase, it fetches the secure card numbers scoped to the specific merchant:Each credential fetch returns a fresh, merchant-scoped secure card number. If leaked, it cannot be reused at a different merchant.See Retrieve Secure Card Numbers for the full API reference.
Navigate the checkout with a browser automation tool
There are several ways to drive a checkout session, and the right one depends on your use case — direct DOM control, LLM-driven autonomous browsing, or your own framework. In every case the integration with Crossmint is the same: you fetch a fresh, merchant-scoped secure card number with the snippet above and feed those credentials into whichever tool runs the browser.
When to use Browser Checkout vs Fast Checkout
| Browser Checkout | Fast Checkout | |
|---|---|---|
| Coverage | Any website that accepts cards | Amazon, Shopify stores (US only) |
| How it works | Agent drives a real browser session | Single API call, no browser needed |
| Latency | Higher — page loads, form filling, CAPTCHA handling | Lower — direct API |
| Reliability | Can break when sites change their DOM | Stable API contract |
| Stablecoin support | No — cards only | Yes — can pay with stablecoins on card-only merchants |
Learn more
Cards quickstart
Full card flow: save, verify, give permission, and retrieve.
Fast Checkout
Skip the browser entirely for supported merchants.
How Agents Pay
The full mental model for agent payments.

