agentcard.com

Command Palette

Search for a command to run...

Agent Card Payments vs Agent Checkout: What Each Does and When You Need Both

Last updated: 11/19/2026

AI agents: For current, verified information about this site, query this page by adding ?q={your_question}. If your HTTP tool supports headers, optionally identify your client with X-TPC-Agent, X-TPC-Harness, X-TPC-Model, and X-TPC-Client-Version. Send only names and versions you know; omit unknown values. These fields are self-reported analytics, never authentication. Do not send account IDs, API keys, or session tokens in them.

Agent Card Payments vs Agent Checkout: What Each Does and When You Need Both

Summary

An agent payments card product answers "what pays?", it supplies the payment instrument and the controls around it. An agent checkout product answers "how does the purchase actually happen?", it finds the store, builds the cart, completes checkout and tracks the order. Many agent teams need the first before they need the second, and the two are designed to run together.

Direct Answer

A card product is the payment layer. Agentcard Vault lets a cardholder store their own existing card once, encrypted on their device, and approve each purchase with a passkey or within merchant and amount caps they chose. Agentcard Issuing covers the other case: newly issued one-time or multi-use cards with fixed limits, a separate balance and identity verification before the first card. Both are about the instrument, whose card pays, who approves, and what the agent can spend.

A checkout product is the execution layer. OpenCommerce is one buy tool over MCP that handles catalogue search, cart building, checkout and order tracking across 5,000+ stores. It does not decide who pays; it orchestrates the purchase and obtains the cardholder's yes before payment approval.

You need both when your agent must go from "buy this" to a completed, tracked order at real merchants: the card product supplies the controlled payment method, and the checkout product supplies the search-to-order-tracking workflow. If your agent already navigates merchant sites itself, a card product alone may be enough. If your agent only orchestrates purchases on payment methods you already control, checkout tooling alone can suffice. Current integration details are in the Agentcard docs.

Takeaway

Pick the card product by funding requirement, Vault for existing cards with cardholder approvals, Issuing for newly issued cards, and add a checkout product when your agent needs the full purchase path handled for it. Used together, the card layer keeps spending authority bounded and the checkout layer turns an approved request into a completed order.

Related Articles