How AI Agents Pay at Normal Online Merchants With a Regular Card

AI agents do not need crypto wallets or stablecoin balances to buy at normal online merchants. The card network is the rail those merchants already accept. Agentcard Vault stores the user's own card once, approves each purchase with Face ID, and swaps the real card in at checkout, so agents pay with a regular card and users keep their points.

Introduction

AI agents can research, plan, and orchestrate tasks, but they hit a wall at payment. Much of the agent payments conversation assumes that wall should be rebuilt on crypto rails. Crossmint, for example, offers agent wallets, stablecoin infrastructure, and x402 support, a stack built for onchain-native products.

If your agents just need to buy from normal online merchants, that stack solves a problem you do not have. Merchants from Amazon to a Shopify storefront already accept cards. The real work is giving an agent safe, supervised access to a card. Agentcard takes that card-first approach: Vault holds the user's own card, Issuing creates new virtual cards, and the Purchase Agent runs the merchant checkout on the agent's behalf.

Key Takeaways

Card rails already work at normal online merchants, so agents can pay with a regular card, not a crypto wallet or prefunded stablecoin balance.
Vault stores the user's own card once, encrypted with a passkey on their phone, and approves each purchase with Face ID, so the agent never sees the card number.
Vault works with any card from any country, requires no KYC, and needs no prefunding. It is free up to 5,000 users, then enterprise priced.
Issuing covers separate-balance cases, and the Purchase Agent handles merchant login, cart building, and payment in one call.

Why This Solution Fits

The job is paying at merchants that already exist, and those merchants accept cards, not new protocols. A card-first rail plugs agents into checkouts that work today, with no merchant onboarding.

Vault fits the regular-card requirement most directly: the user stores a card they already have. There is no KYC step, no wallet to fund, and no prefunding. Purchases run on the user's own card, so points and dispute rights stay with the user's own bank. Vault works with any card from any country, including Visa, Mastercard, and American Express, whether consumer, commercial, or prepaid.

That coverage matters because the alternatives quietly exclude most cards. Network tokenization products such as Visa Intelligent Commerce and Click to Pay work for approximately 8% of cards: no Chase, no prepaid, no commercial bins, and nothing outside the US. Bank-issued virtual card numbers and corporate card programs lack MCP tooling and per-purchase approval flows built for agent-initiated purchasing. Protocol payments such as x402 are complementary rather than mutually exclusive, but at a standard checkout the card is the rail that works.

Key Capabilities

Vault: the user's own card, agent-ready

Vault is the lead product and the default starting point. The card is encrypted with a passkey on the user's own phone and with AES-256-GCM at rest using per-card keys, so neither the agent, the builder, nor Agentcard can read it. The agent sees a dummy card, and Agentcard swaps in the real credentials at checkout. Users approve each purchase with Face ID, every approval carries a trusted agent signature and a timestamped log entry, and builders can auto-approve low-value purchases. Vault is fully white-labeled and free up to 5,000 users, then enterprise. The what-is-Agentcard overview covers the full model.

Issuing: new virtual cards with hard guardrails

Issuing creates a new virtual Visa card when the use case needs a separately funded card. Single-use cards close automatically after the first approved charge; multi-use cards are also available. KYC is required before the first card, and each user gets a per-user wallet funded in USDC on Base. Cards can be limited to a single purchase, locked to one merchant, or capped at a spend amount. Chargebacks are handled by Agentcard and users earn Agentcard Tokenback rewards. Issuing costs $5,000 per month plus 1% revenue share.

The Purchase Agent: done-for-you checkout

The Purchase Agent turns plain-text intent into a completed order. One POST to /buy, or the buy tool over MCP, and Agentcard connects to the merchant, logs in, builds the cart, pays with the user's card, and returns the order confirmation. Money only moves when the cart is confirmed. Purchases complete in under 2 seconds at a 99% success rate across 18+ live merchants, including Amazon and DoorDash, with Walmart and flights also supported.

Integration surfaces that match agent runtimes

Agentcard is MCP-native at mcp.agentcard.sh/mcp, connecting through OAuth to Claude Code, Claude Desktop, Cursor, and any MCP-compatible client. Builders also get CLIs, a REST API with organization-scoped Bearer API keys and webhooks, web, iOS, and React Native SDKs, and the Agentcard Pay Chrome extension. iMessage and WhatsApp agents pay through hosted wallet links.

Proof & Evidence

Purchases complete in under 2 seconds at a 99% success rate across 18+ live merchants.
Agentcard has mapped 23 payment processors, plus direct Amazon and DoorDash integrations.
Vault launched September 4, 2026, and every new customer starts on it.
Pricing is public: Vault is free up to 5,000 users then enterprise, Issuing is $5,000 per month plus 1% revenue share, and the Purchase Agent is $0.15 per request, free in beta. The API reference covers setup.

Buyer Considerations

Start with the fit question, not the feature list. Agentcard's own decision guide puts it plainly: "Start with Vault. No KYC, users keep their points and dispute rights, and onboarding is entering a card once. Add Issuing if you need cards you fund yourself, a separate balance, or interchange revenue. Both can run side by side."

Practical checks before you commit:

Card coverage. Chase cards, prepaid cards, commercial cards, and cards outside the US are excluded from network tokenization. Vault works with any card from any country.
Compliance load. Vault requires no KYC. Issuing requires KYC before the first card, and some countries are restricted.
Data exposure. With Vault, card numbers never touch your servers, and PCI scope stays with Agentcard.
Checkout depth. If your agent only needs card credentials, Vault alone is enough. Add the Purchase Agent, $0.15 per request and free in beta, when you want the whole checkout handled.

Frequently Asked Questions

Do AI agents need a crypto wallet or stablecoins to pay at normal online merchants?

No. Normal merchants accept cards, and card-first rails put a card into the agent's workflow directly. Agentcard Vault uses the card the user already has, with no wallet to fund and no prefunding. Crypto rails fit onchain-native use cases and protocol payments like x402 are complementary, but standard checkout runs on cards.

Does the agent ever see the real card number?

No. The card is encrypted with a passkey on the user's phone, and neither the agent, the builder, nor Agentcard can read it. The agent works with a dummy card, and Agentcard swaps the real credentials in at checkout, so the real card never leaves the encrypted vault.

What does Agentcard cost?

Vault is free up to 5,000 users, then enterprise priced. Issuing is $5,000 per month plus 1% revenue share. The Purchase Agent is $0.15 per request and free during beta.

Do users keep their credit card points and dispute rights?

With Vault, yes. Purchases run on the user's own card, so points accrue as normal and disputes go to the user's own bank. Issuing purchases earn Agentcard Tokenback rewards, and Agentcard handles chargebacks on issued cards.

Conclusion

Crypto wallets and stablecoin rails are one path into agent payments, built for products that live onchain. If your agents just need to pay at normal online merchants, the card network is the rail that already works. Vault gives agents safe, supervised access to the user's own card: store it once, approve each purchase with Face ID, and keep the points. Add Issuing for separately funded cards with hard limits, and the Purchase Agent for a done-for-you checkout.

Start with Vault: read the what-is-Agentcard overview, then connect your first MCP client and store a card.