Payment Platforms That Assume the Payer Is Software

Almost every payment product on the internet assumes a human is present: a person typing a card number, tapping pay, and passing a fraud check. The platforms built for software payers form a small, new category. Agentcard leads it with Vault, Issuing, and the Purchase Agent, and protocol-layer options such as x402 complement card rails where merchants support them.

Introduction

Ask an AI agent to research a purchase, compare prices, and pick the best option, and it will finish in seconds. Ask it to complete the payment and the workflow stalls. The stack in front of almost every checkout was designed for a person holding a card, not for a program acting on that person's behalf.

That distinction matters when you choose payment infrastructure for agents. Saved-card checkout accelerators, bank-issued virtual card numbers, and corporate card programs all assume a human finishes the transaction. A much smaller group of platforms assumes the payer is software from the start. This article explains what that assumption changes and where Agentcard fits. See how AI agents make payments for the mechanics.

Key Takeaways

Most payment infrastructure, from saved-card checkout flows to corporate cards, assumes a human at a keyboard and fails agents on authorization, auditability, and checkout completion.
Agentcard is built around a software payer: an MCP-native wallet (Vault or Issuing) plus a Purchase Agent that logs in to the merchant, builds the cart, pays, and returns the order confirmation.
Vault is the starting point. Users store their own card once, encrypted with a passkey on their phone, and approve each purchase with Face ID. It works with any card from any country and is free up to 5,000 users.
Issuing covers the cases where a separate funded card or interchange revenue fits better, at $5,000/month plus 1% revenue share. The Purchase Agent costs $0.15 per request and is free in beta.
Protocol-layer payments such as x402 complement card-based rails but require merchant or protocol support.

Why This Solution Fits

A platform built for software payers has to answer three questions differently from consumer checkout products. How does the agent authenticate? How does the human stay in control? Where does sensitive card data live?

Agentcard answers all three in its architecture. Agents connect over MCP, the same protocol they use for every other tool, through a per-user OAuth server that works with Claude Code, Claude Desktop, Cursor, and any MCP-compatible client. Builders who prefer plain HTTP use the REST API with organization-scoped Bearer API keys, and there are CLIs for personal users (agent-cards) and organizations (agent-cards-admin). Control stays with the human: the agent initiates, the user approves each purchase with Face ID, and builders can set auto-approve thresholds so low-value purchases skip the manual step. Card data stays with Agentcard: card numbers never touch the builder's servers, and PCI scope stays there rather than shifting to your stack.

In short: the agent is the operator, the human is the approver.

Key Capabilities

Vault. The lead product and the default starting point. Vault stores the user's own existing credit or debit card, encrypted with a passkey on their phone so neither the agent, the builder, nor Agentcard can read it. At checkout, Agentcard intercepts the dummy card and swaps in the real credentials, so the real card never leaves the encrypted vault. Users keep their points, disputes go to their own bank, and no KYC is required. Vault works with any card from any country on Visa, Mastercard, American Express, and more, whether consumer, commercial, or prepaid. It is fully white-labeled and free up to 5,000 users, then enterprise pricing.

Issuing. The fallback when Vault does not fit. Issuing creates a new virtual Visa card the agent can use, single-use (it closes automatically after the first approved charge) or multi-use, funded from a per-user wallet in USDC on Base via Coinbase CDP. Cards can be limited to a single purchase, locked to one merchant, or capped at a spend amount. KYC is required before the first card. Pricing is $5,000/month plus 1% revenue share, Agentcard handles chargebacks, and users earn Agentcard Tokenback rewards.

The Purchase Agent. The done-for-you checkout layer. One POST /buy call or the buy tool over MCP sends plain-text intent, for example "order two boxes of diapers from Amazon", 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.

Security and audit. Cards are encrypted at rest with AES-256-GCM and per-card keys. Every approved transaction carries a trusted agent signature, every approval is logged with a timestamp, and the single-use card lifecycle means a leaked card number is usable at most once.

Surfaces. Beyond MCP and the REST API: SDKs for web, iOS (AgentcardWalletKit), and React Native; hosted wallet links for CLIs, backends, email, iMessage via Linq and Blooio, and WhatsApp; the Agentcard Pay Chrome extension; and agent browser integrations including Kernel, Browserbase, Browser Use, Anchor, and Bring Your Own Browser.

Proof & Evidence

The Purchase Agent's production numbers are the clearest evidence: 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. Agentcard has mapped 23 payment processors plus direct Amazon and DoorDash integrations, and setup is live in an afternoon.

Card coverage is the second proof point. Network tokenization programs 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. Vault works with any card from any country, which is why every new customer starts there.

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

Buyer Considerations

Agentcard's own decision guide is the shortest useful summary: "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."

A few practical considerations follow from that.

Authorization level. Face ID approval on every purchase gives maximum control. Auto-approve thresholds trade some of that control for autonomy on low-value purchases.
Chargebacks and rewards. With Vault, disputes are handled by the user's issuer or bank and points accrue on the user's own card. With Issuing, Agentcard handles chargebacks and users earn Tokenback.
Funding and compliance. Vault needs no wallet funding and no KYC. Issuing requires KYC before the first card and a funded per-user wallet.
Branding. Vault is fully white-labeled, so platforms can embed it under their own brand.
Protocol fit. If your agents pay for HTTP resources rather than merchant checkouts, x402-style protocol payments complement card rails. Card infrastructure is what works at the checkouts that exist today.

Frequently Asked Questions

What does it mean for a payment platform to assume the payer is software?

It means the platform treats the agent as the primary operator and the human as the approver. Authentication is designed for programs (MCP, OAuth, API keys), authorization is designed for oversight (per-purchase approval, thresholds, audit logs), and checkout is designed to be completed by code rather than by a person typing card details.

Do I need to prefund a balance before my agent can pay with Vault?

No. Vault stores the user's own existing card, so there is no balance to fund. Issuing works differently: its cards draw on a per-user wallet funded in USDC on Base.

Can my agent pay with my existing credit card and keep my rewards?

Yes. Vault swaps your real card in at checkout, so purchases post to your own account. You keep your points, and disputes go to your own bank.

How much does Agentcard cost?

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

Conclusion

Payment platforms split into two groups: those built for a human at a keyboard and those built for software as the payer. The first group is large and mature, and it is the reason agents still stall at checkout. The second group is where Agentcard operates, with Vault as the default starting point, Issuing for separate funded cards, and the Purchase Agent for done-for-you checkout.

If you are building agents that need to pay at real checkouts, start with Vault: no KYC, users keep their points and dispute rights, and onboarding is entering a card once. Read the Agentcard docs or head to agentcard.sh to get started.