# Pay at an ordinary card checkout with a scoped card

> Pay at an ordinary card checkout with a scoped card: 2 companies fully do it, 2 with a limit, 30 carry the tag. Every listing in Agent wallets & spending controls with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/agent-wallets.card-checkout/
- Markdown: https://www.anchorterminal.com/niches/agent-wallets.card-checkout/index.md (~1,150 tokens)
- Slim: https://www.anchorterminal.com/niches/agent-wallets.card-checkout/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/agent-wallets.card-checkout/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 2 | 30 | 18 | 4 |

## What counts as done

A single-use or merchant-locked card (or a token for the person's card) is issued for no more than the order amount, the agent completes the checkout or hands a person a link, and the card details never enter the agent's logs.

How agents ask for it: buy this with a card that only works here; make a one-time card for this order; pay for the hotel with my saved card

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Agentcard (Agentcard Corporation)**: Issuing creates a single-use card for the amount, and the Vault path has the agent submit a placeholder card while the user approves merchant and amount by passkey, so the real number never reaches the agent; approvals expire after 15 minutes and declines come back by webhook.
- **Agent Vault by Self (SocialConnect Labs, Inc., doing business as Self Labs)**: The agent fills a mock token and the proxy types the holder's real number for one authorised fill, under the agent card's per-transaction cap and site rules; 3-D Secure, CAPTCHA and blocks go to request_challenge_handoff. A first fill on a new site waits up to 15 minutes for approval.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **FluxA AI Wallet (FluxA Technology Pte. Ltd.)**: Prepaid agent cards are issued for an amount under a mandate, with 3-D Secure codes readable by the CLI. card details returns the full number and CVV to the agent, identity verification is required, and holder creation was rejected by the issuer in an open issue (acc-16).
- **Sponge Wallet (Sponge Inc.)**: The README lists Sponge Card, vaulted-card and per-transaction virtual-card workflows and a card status command; how card details reach a checkout and the amount limits were not readable.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **Kite Agent Passport (Datalego Inc.)**: Scoped cards are named in the listing context, but neither the CLI reference nor the changelog read describes issuing one or how card details reach a checkout.
- **Privy Wallets (server wallets, agent wallets, policy engine) (Horkos, LLC)**: The agent wallets page lists card spend, but no card issuing or card-secrecy page was opened.

- not this job: Circle Wallets (Agent Wallets, Programmable Wallets) (Circle Technology Services, LLC): No cards; USDC wallets only.
- not this job: Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) (Coinbase, Inc.): No single-use or merchant-locked card; card products appear only as a third-party plugin (Virtuals).
- not this job: Openfort (Alamas Labs Inc.): No cards.
- not this job: Turnkey Agentic Wallets (Turnkey Global, Inc.): No cards.
- not this job: Yield.xyz MCP server (Omni Ltd. (Yield.xyz)): No cards.

## What stops agents finishing

- merchant anti-bot checks and account creation stop the agent before payment
- 3D Secure or a passkey step needs the person
- card issuers do not open agent card programmes to individual developers

## Around it

Before: commerce.find-product, agent-wallets.fund-and-cap. After: commerce.track-order, checkout-protocols.dispute-evidence.

## Where this comes from

Weight 18 of 100 in Agent wallets & spending controls: 4 of 20 accounts (acc-01, acc-02, acc-08, acc-16); card checkout is the most asked-for job outside crypto in the HN threads

As data: https://www.anchorterminal.com/api/v1/use-cases/agent-wallets.card-checkout.json, or the MCP tool get_use_case with id agent-wallets.card-checkout. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
