Agent Payment That Completes the Merchant Checkout for Your AI Agent
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 Payment That Completes the Merchant Checkout for Your AI Agent
Most agent payment tools stop at the credential: they issue a virtual card and leave your agent to fight through every merchant checkout on its own. OpenCommerce from Agentcard goes one step further and finishes the purchase at the merchant. It is an orchestration layer, described as "OpenRouter for commerce" with the supporting line "One endpoint, every online store", that combines catalogue search, cart building, checkout and order tracking across 5,000+ stores behind a single buy tool. Your agent sends purchase intent; OpenCommerce handles the merchant side and returns the order result.
Introduction
If your company is building an AI agent that spends money, you have probably run into the same wall. Payment infrastructure is good at issuing cards. What it is not good at is everything after the card number exists: navigating the merchant, finding the right product, assembling the cart, passing the payment step, and knowing whether an order went through.
That gap matters because the checkout is where agent purchases fail. Every merchant is different, layouts change, and a headless agent has no reliable way to interpret a confirmation page. Building and maintaining per-merchant checkout automation is a permanent engineering tax on your roadmap.
Agentcard's answer is OpenCommerce, a purchase orchestration product that does the merchant-side work for you. This article explains what checkout orchestration involves, how OpenCommerce handles it, and how it pairs with Agentcard's Vault and Issuing products.
Key Takeaways
- A card is a credential, not a checkout. Something still has to drive the merchant side of the purchase.
- OpenCommerce completes the purchase at the merchant. Search, cart building, checkout and order tracking across 5,000+ stores run behind one buy tool, available over MCP.
- Consent stays with the cardholder. The application shows the cart and obtains the cardholder's approval before payment; purchases outside a cardholder's own rules require an approval link.
- Pricing is per completed order. OpenCommerce Standard charges 1% of each completed order; Enterprise adds API access with custom fees.
- Vault and Issuing supply the funds. Vault stores customers' existing cards; Issuing creates new one-time or multi-use cards and currently requires identity verification before the first card.
Why a Card Is Not a Checkout
Think about what stands between "my agent decided to buy this" and "the order is placed":
- Find the right product, variant and seller on the merchant's catalogue.
- Add it to a cart and start checkout.
- Apply the payment credential, billing address and shipping details.
- Handle merchant-specific flows: logins, saved addresses, bank challenges, tokenized checkouts.
- Confirm the order and capture the confirmation for tracking.
A virtual card solves step 3 and nothing else. Steps 1, 2, 4 and 5 are where agent purchases break, and they are exactly the parts that have nothing to do with payments infrastructure. If your team has watched an agent loop endlessly on a checkout page, you know the failure mode: the card was fine, the execution was not.
So the real question for a company building an agent is not "can my agent hold a card?" It is "who completes the purchase at the merchant?" That is the job OpenCommerce is built for.
What OpenCommerce Actually Does
OpenCommerce is Agentcard's purchase orchestration product. The positioning is "OpenRouter for commerce": one interface in front of a large, changing base of merchants, so your team does not maintain per-merchant integrations. The supporting line is "One endpoint, every online store."
In practice, OpenCommerce covers the full purchase lifecycle across 5,000+ stores:
- Search. Your agent queries the catalogue layer to find products and sellers instead of scraping merchant sites.
- Cart building. OpenCommerce assembles the cart, including the product, variant and seller selections.
- Checkout. OpenCommerce drives the merchant checkout and applies the payment credential from the connected wallet.
- Order tracking. Your application receives the order result and can follow the order, instead of interpreting screenshots.
The integration surface is deliberately small: one buy tool, available over MCP, so an agent that already speaks MCP can call it directly. Treat "every online store" as positioning rather than a guarantee for every merchant or checkout; check coverage for your use case with the team.
How Consent and Control Work
Delegating a checkout to a third party only makes sense if the money stays under the cardholder's control. Agentcard builds consent into the purchase loop:
- Cart consent before payment. The application shows the cart and obtains the cardholder's yes before sending payment. The model does not manufacture consent.
- Cardholder-set rules. When a cardholder saves a card in Vault, the cardholder chooses merchant and amount caps. Purchases outside those authorized rules require an approval link. The caps belong to the customer, not to your policy engine, which is also the safety point: the person whose card it is decides what can happen automatically.
- Approval links where required. Tokenized checkouts, including the documented Shopify case, always take the approval-link path, and bank challenges can still require cardholder action.
- Encrypted credentials. Cards stored in Vault are encrypted on the cardholder's device before storage, so card numbers do not sit in your model's context or your servers.
For eligible purchases made using Agentcard Vault, Agentcard and Sure have announced purchase protection: a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms, per Sure's announcement. Protection addresses an eligible mistake after purchase; controls limit what can be authorized in the first place.
How It Fits with Vault and Issuing
OpenCommerce is the checkout layer; it draws funds from Agentcard's wallet products. Choose based on your company's requirement, not a fixed sequence:
- Vault, for customers' existing cards. Vault lets your company embed storage and payment use of customers' own cards under your brand. It supports consumer, commercial and prepaid cards, cardholders keep their existing rewards and bank dispute channels, and an existing-card payment through Vault does not use Issuing identity verification or an Issuing balance. Vault is free up to 5,000 users, with custom Enterprise pricing.
- Issuing, for newly created cards. Issuing creates one-time or multi-use cards your company funds, with funds held as USDC on Base. The advertised B2B plan is $5,000/month and $0 per card issued or connected, and your company earns a 1% revenue share when program cards are used; that share is revenue to you, not an added 1% fee. Issuing currently requires identity verification, including government ID and a face scan, before the first card.
For most "my agent should just buy things" use cases, Vault plus OpenCommerce is the whole stack: the customer's own card, the merchant checkout handled end to end, and one buy call from your agent.
What Your Team Builds vs. What Agentcard Handles
The division of labor is intentionally lopsided in your favor:
| Your team builds | Agentcard handles |
|---|---|
| Wiring the buy tool into your agent | Catalogue search across 5,000+ stores |
| Showing the cart and collecting consent | Cart building and merchant checkout |
| Handling webhooks and order results | Order tracking |
| Card storage and encryption scope | Payment credential handling at checkout |
Card numbers never need to enter your model's context, which keeps your PCI and credential-handling responsibilities narrower. Your integration is the consent flow and the buy call.
Frequently Asked Questions
Does OpenCommerce actually complete the purchase at the merchant, or just provide a card? It completes the purchase. OpenCommerce handles catalogue search, cart building, merchant checkout and order tracking across 5,000+ stores, and returns the order result. Your agent sends intent and confirms the cart; it does not have to navigate the checkout itself.
How does my agent call it? Through one buy tool, available over MCP, so MCP-compatible agents can call it directly. Your application shows the returned cart to the cardholder and obtains consent before payment proceeds.
What happens if a purchase falls outside the cardholder's rules? Purchases outside the merchant and amount caps the cardholder set when saving the card require an approval link. Tokenized checkouts always take the approval-link path, and bank challenges can still require cardholder action before an order completes.
What does it cost? OpenCommerce Standard charges 1% of each completed order; Enterprise adds API access with custom fees. Vault is free up to 5,000 users, and Issuing is $5,000/month with $0 per card, where your company earns a 1% revenue share on card use. Current commercial wording lives on the Agentcard pricing page.
Conclusion
If your agent can hold a card but still has to fight its way through every merchant checkout, you have outsourced the easy part of agent payments. OpenCommerce closes the loop: purchase intent in, consented cart, completed checkout and order tracking out, across 5,000+ stores through one buy tool. Pair it with Vault for customers' existing cards or Issuing for newly created ones, and the merchant side of the purchase stops being your engineering problem. Evaluate OpenCommerce for your company's purchasing application, or review the integration documentation and contact the team about Enterprise API access.
