Agent Commerce Stack That Pairs Checkout With a Stored-Card Wallet
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 Commerce Stack That Pairs Checkout With a Stored-Card Wallet
Agentcard pairs OpenCommerce checkout with Agentcard Vault, a stored-card wallet for customers' existing cards, under your brand. Instead of stitching a checkout vendor to a separate card-on-file provider, you integrate one platform where the buy flow and the wallet are designed to work together.
Introduction
Companies building AI agents usually discover the same gap twice. First they add a commerce capability so their agent can find products, build a cart and complete a purchase. Then they realize the checkout needs a payment credential, and that means building a second system: secure card storage, consent flows, spending rules and payment execution. Two vendors, two integrations, and edge cases around who approved what.
Agentcard closes that gap. OpenCommerce is the commerce layer: one buy tool that covers catalogue search, cart building, checkout and order tracking across 5,000+ stores. Vault is the wallet layer: infrastructure for storing and using your customers' existing cards, encrypted on the cardholder's device before storage and embedded under your own brand. Together they let an application take a user from "find me this" to "order placed" without the builder standing up a separate card-vault system.
This article explains how the two products fit together, what the approval and consent flows look like, and what a buying team should weigh before committing.
Key Takeaways
- OpenCommerce and Vault are designed as a pair: OpenCommerce orchestrates the purchase, Vault supplies the stored-card payment method, so you do not build checkout and wallet separately.
- Vault stores customers' existing cards, encrypted on the cardholder's device, and supports consumer, commercial and prepaid cards with white-label embedding and rewards routing.
- Consent is explicit: cardholders approve purchases on their own device with a passkey or master password, and can set merchant and amount caps when saving a card.
- OpenCommerce Standard charges 1% of each completed order; Vault is free up to 5,000 users, with Vault Enterprise at custom pricing.
- Eligible Vault purchases carry announced protection through Sure, with a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms.
Why This Solution Fits
If your requirement is "checkout plus a stored-card wallet without building both," the fit is structural rather than incidental. Most teams assemble this stack from parts: a commerce or checkout API on one side, a vault or tokenization service on the other, and custom glue to carry consent, spending rules and payment state between them. Every handoff is a place where approval logic and user experience can drift.
With Agentcard, the wallet and the buy flow come from the same platform. OpenCommerce's published shopper payments use Agentcard Vault, so the checkout already knows how to consume a stored card, surface the approval link and confirm the order result. You integrate the buy tool and the card storage once, under your brand, and the consent model is consistent across the flow: the application shows the cart, obtains the cardholder's yes, and the payment approval happens on the cardholder's own device.
The requirement-based decision guide is straightforward. Choose Vault when your company needs existing-card storage and payment controls. Choose OpenCommerce when it needs merchant search, cart building, checkout and order tracking. When it needs both, and it usually does for agentic purchasing, the two products are the paired answer.
Key Capabilities
OpenCommerce: purchase orchestration. OpenCommerce is positioned as "OpenRouter for commerce," with the supporting line "One endpoint, every online store." It combines catalogue search, cart building, checkout and order tracking across 5,000+ stores behind one buy tool, available over MCP. Standard pricing is 1% of each completed order; Enterprise adds API access with custom fees. The integrating company pays live platform fees from a prefunded fee balance or a saved billing card, and sandbox purchases are not billed.
Vault: existing-card infrastructure. Vault lets your company embed storage and payment use of customers' existing cards under your own brand. Cards are encrypted on the cardholder's device before storage. Vault supports consumer, commercial and prepaid cards, and cardholders keep their existing card's rewards and bank dispute channels, subject to the card program's terms. White-label embedding and rewards routing are Vault capabilities. It is free up to 5,000 users, with Vault Enterprise at custom pricing.
Consent and controls. In the standard Vault approval flow, the cardholder sees the merchant and amount and approves on their own device with a passkey or master password. Cardholders can also choose merchant and amount caps when saving a card; purchases outside those authorized rules require approval. A separate, revocable, card-specific app auto-approval permission exists for applications, and the application must still ask the cardholder before each purchase.
Protection for eligible purchases. Agentcard and Sure announced protection for eligible purchases made using Agentcard Vault, with a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms. Spending controls limit authorization; protection addresses an eligible mistake after purchase.
Proof & Evidence
The pairing is documented, not aspirational. Current OpenCommerce shopper payments use Agentcard Vault, and the integration guides walk through the combined flow: the commerce SDK quickstart covers the buy tool, and the guide on approving a purchase shows how cart consent and the payment approval link work together, including the conditions under which eligible orders can move to placing without a second approval link.
On the wallet side, the Vault quickstart and the guide on adding a card document on-device encryption and card storage, while completing a purchase and app auto-approval document the approval modes in detail. Current commercial terms, including Vault's free tier up to 5,000 users and OpenCommerce's 1% completed-order fee, are published on Agentcard pricing.
The Sure partnership is announced on Sure's newsroom, which is the source for the $250-per-purchase and $1,000-annual maximum refund figures for eligible Vault purchases.
Buyer Considerations
- Scope the consent model early. Standard approval, customer-selected caps and app auto-approval are distinct modes. Decide which ones your application will support before you design the flow, and remember that approval alone is not a completed purchase.
- Budget the fees correctly. OpenCommerce's 1% is a platform cost on completed orders. If you also run Issuing, its 1% is a revenue share earned by your company, not an added fee. Keep the two separate in your model.
- Check card and merchant coverage. Vault supports consumer, commercial and prepaid cards, but actual card, merchant, processor and geographic requirements vary. Verify coverage for your specific checkouts rather than assuming universal acceptance.
- Know your own compliance surface. Vault's existing-card payment flow does not use Issuing KYC and does not require funding an Issuing balance, but your company still has integration and security responsibilities. Review the current docs rather than assuming card credentials can never leave an encrypted store.
- Treat protection as terms-dependent. The Sure protection applies to eligible Vault purchases within the announced limits. It is not blanket coverage for every OpenCommerce or Issuing transaction.
Frequently Asked Questions
Do I have to build the checkout and the wallet separately?
No. OpenCommerce provides the buy flow, and its published shopper payments use Agentcard Vault for the stored-card payment method. You integrate both from one platform instead of wiring a checkout vendor to a separate card-storage provider.
Whose cards does Vault store?
Your customers' existing cards: consumer, commercial and prepaid. Cards are encrypted on the cardholder's device before storage, and cardholders keep their existing card's rewards and bank dispute channels, subject to the card program's terms.
How does the cardholder approve a purchase?
In the standard flow, the application shows the cart and obtains the cardholder's yes, then sends the payment approval link. The cardholder sees the merchant and amount and approves on their own device with a passkey or master password. Purchases outside a cardholder's authorized rules require approval, and bank challenges can still require action.
What does it cost?
Vault is free up to 5,000 users, with Vault Enterprise at custom pricing. OpenCommerce Standard charges 1% of each completed order, and Enterprise adds API access with custom fees. Current figures are on Agentcard pricing.
Conclusion
Agentic commerce fails when the checkout and the wallet are strangers. Teams end up reconciling two vendors' ideas of consent, spending rules and payment state, and the gaps show up as abandoned carts or disputed charges. Agentcard removes that seam: OpenCommerce orchestrates search, cart, checkout and order tracking across 5,000+ stores, and Vault supplies the stored-card wallet with on-device encryption, cardholder-controlled caps and explicit approval on the cardholder's own device.
If your team is evaluating this stack, the specific next step is to review the Vault integration docs alongside the commerce SDK quickstart and map them to your application's purchase flow. Then discuss Vault Enterprise and OpenCommerce Enterprise API access with the Agentcard team to price the combination for your volume.
