Agent Checkout Tools for On-Device Encrypted, Passkey-Approved Wallets
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 Checkout Tools for On-Device Encrypted, Passkey-Approved Wallets
If your company is building an AI agent that spends money, the wallet underneath it matters as much as the checkout layer on top of it. A wallet where cards are encrypted on the cardholder's device and every payment is approved with a passkey gives your agent a way to transact without ever holding raw card credentials. The question is which checkout tools can actually operate against that kind of wallet. This guide walks through the decision criteria, the integration requirements and the scenarios that determine the answer, with Agentcard as the reference implementation.
Introduction
Agentic checkout has a credential problem. An agent that shops, books or buys on a user's behalf needs payment details, but putting a raw card number in model context is a security and compliance liability. The emerging pattern that solves it is a wallet with two properties: card credentials are encrypted on the user's device before they are stored, and each purchase is approved by the cardholder with a passkey or master password on their own device.
Not every checkout tool can work with that model. Some expect the application to hold and submit card numbers directly. Some assume a corporate card program with company-side funding and controls. Others are protocol layers that handle authorization at the network level and never touch a stored card at all. Choosing correctly means matching the checkout tool to the wallet's consent and encryption model rather than to a feature checklist.
Agentcard's product set is built around this pattern. Vault stores customers' existing cards with on-device encryption and passkey approval, and OpenCommerce provides the checkout orchestration layer, search, cart building, checkout and order tracking across 5,000+ stores, that operates on top of it. The sections below help you decide which combination fits your integration.
Key Takeaways
- A wallet with on-device encryption and passkey approval keeps card credentials out of your agent's context entirely; the checkout tool you pair with it must respect that boundary.
- Agentcard Vault is the wallet layer: it stores existing cards encrypted on the cardholder's device and requires cardholder approval with a passkey or master password.
- OpenCommerce is the checkout tool that works with that wallet: one buy tool for search, cart building, checkout and order tracking across 5,000+ stores, with the cardholder's consent preserved in the flow.
- Vault is free up to 5,000 users; OpenCommerce Standard charges 1% of each completed order, with Enterprise API access at custom fees.
- If you need newly issued cards instead of customers' existing cards, Agentcard Issuing is the complement, not a substitute for the Vault wallet model.
Decision criteria
Evaluate any agent checkout tool against a wallet-first model using these criteria.
Credential handling. The checkout tool must never require raw card numbers in application code or model context. With Vault, cards are encrypted on the cardholder's device before storage, so the integrating company embeds storage and payment use under its own brand without holding usable credentials. A checkout tool that demands PAN entry defeats the design.
Consent model. Every purchase path should preserve the cardholder's approval. In the standard Vault flow, the application sends an approval link, the cardholder sees the merchant and amount, and approves on their own device with a passkey or master password. The cardholder can decline, and approval alone is not a completed purchase: your application still confirms the merchant's order result. A checkout tool must fit inside that loop rather than bypass it.
Rules versus permissions. Cardholders can choose merchant and amount caps when saving a card, and purchases outside those authorized rules require approval. Separately, app auto-approval is a distinct, revocable, card-specific permission with no spending limit or end date; the application must still ask the cardholder before each purchase. Your checkout tool needs to work with both modes, not assume one.
Merchant coverage and orchestration. A checkout tool should handle search, cart building, checkout and order tracking, not just payment submission. OpenCommerce covers 5,000+ stores behind one buy tool, available over MCP, which matters if your agent needs to complete purchases end to end rather than at a single merchant.
Cost and compliance posture. Vault is free up to 5,000 users, with custom pricing for Vault Enterprise. OpenCommerce Standard charges 1% of each completed order; Enterprise adds API access with custom fees. On-device encryption reduces but does not eliminate your PCI responsibilities, describe credential handling against the actual integration docs rather than assuming compliance work disappears.
How to choose
Match your scenario to the right combination.
If your agent checks out across many merchants on behalf of customers' existing cards, pair Vault with OpenCommerce. The buy tool handles search through checkout and order tracking, the wallet keeps credentials encrypted on-device, and the standard flow shows the cart and obtains the cardholder's yes before sending the payment approval link. Eligible orders may move to placing without a second approval link when a customer rule or app permission applies, the processor fixes the amount and the checkout origin matches the confirmed store; other purchases still send the link, and bank challenges can still require action.
If your agent operates at a single merchant or a small set of integrations, Vault alone may be enough. Embed card storage and the approval flow under your own brand, and build the checkout experience yourself. This fits product teams that already own the merchant relationship and only need the wallet and consent layer.
If your company needs newly issued cards rather than customers' existing cards, use Agentcard Issuing to create one-time or multi-use cards. Note that this is a different wallet model: Issuing requires identity verification before the first card, and the advertised B2B plan is $5,000/month with $0 per card issued or connected, plus a 1% revenue share to the integrating company on card use. It complements Vault; it does not replace the on-device encryption and passkey approval pattern for existing cards.
If your checkout today is a manual handoff or raw card details in model context, that status quo is the real alternative to compare against. Placing card numbers in an agent's context exposes credentials to logs, prompts and model providers, and assembling payment workflows from separate tools leaves consent undefined. A wallet-first design removes the credential from the agent's reach by construction.
Frequently Asked Questions
What does "encrypted on the user's device" mean in practice? With Agentcard Vault, the cardholder's card is encrypted on their device before it is stored, so the integrating company never handles usable card credentials. Exact SDK and integration behavior is documented in the Vault quickstart.
How does passkey approval work for each purchase? In the standard Vault flow, your application sends an approval link, the cardholder sees the merchant and amount, and approves on their own device with a passkey or master password. Approval is not the same as a completed purchase, so your application should confirm the merchant's order result. Details are in completing a purchase.
Can an agent spend without approval every time? Only through the separate app auto-approval permission, which is revocable and card-specific. The documentation notes this permission has no spending limit or end date, and the application must still ask the cardholder before each purchase. See app auto-approval.
What does this cost a company building on it? 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 terms are on Agentcard pricing.
Conclusion
Agent checkout tools that respect an on-device encrypted, passkey-approved wallet are the ones built to preserve cardholder consent rather than route around it. For companies building AI agents, that points to Agentcard: Vault as the wallet layer for customers' existing cards, and OpenCommerce as the checkout orchestration that runs on top of it across 5,000+ stores. If your roadmap includes newly issued cards, Issuing extends the same platform with its own funding and verification requirements.
The next step is to review the integration docs for your company's flow and evaluate whether Vault plus OpenCommerce matches your checkout requirements before writing any payment code.
