agentcard.com

Command Palette

Search for a command to run...

Agent Checkout Tools That Fit On-Device Encrypted Wallets

Last updated: 11/22/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 Checkout Tools That Fit On-Device Encrypted Wallets

Agentcard Vault is the checkout infrastructure built for wallets where card credentials are encrypted on the cardholder's device and every purchase is approved with a passkey. If your AI product needs to charge customers' existing cards without ever holding raw card numbers, Vault gives you the storage, the consent flow and the payment controls in one integration.

Introduction

AI products that spend money on a customer's behalf face a hard constraint: the moment your application or its model touches a raw card number, you inherit the security and compliance burden of storing it. Wallets that encrypt card credentials on the user's device before storage, and that require a passkey approval on the user's own hardware, remove that exposure by design. The open question for builders is which checkout tooling actually works with that model rather than around it.

Agentcard answers that question with Vault, its existing-card infrastructure for companies building AI agents. Vault embeds storage and payment use of customers' existing cards under your brand, with cards encrypted on the cardholder's device before storage and approvals delivered to the cardholder's own device. This article explains how that flow works, what it protects against, and what to weigh before you integrate.

Key Takeaways

  • Vault is Agentcard's existing-card product: customers keep their own cards, rewards and bank dispute channels while your application orchestrates checkout.
  • Cards are encrypted on the cardholder's device before storage, so raw credentials do not sit in your application's database or pass through your model's context.
  • Standard approvals send a link the cardholder opens on their own device, where they see the merchant and amount and approve with a passkey or master password.
  • Cardholders can set merchant and amount caps when saving a card; purchases outside those rules require approval.
  • Vault is free for up to 5,000 users, with custom pricing for Vault Enterprise.

Why This Solution Fits

The defining feature of this wallet model is separation of duties. Your application decides what to buy and initiates the payment. The cardholder's device holds the encrypted credential and the passkey that unlocks it. Agentcard Vault is built exactly for that split: it gives companies the API surface to embed existing-card storage and payment controls while the credential and the consent stay with the customer.

For AI product and engineering teams, the fit is direct. Your model never needs to see a card number, so you avoid building a PCI-scoped credential store and avoid the risk of card data leaking into model context or logs. The documented Vault quickstart covers adding a card and completing a purchase, and the purchase flow shows how the approval link fits into an agentic checkout.

For commerce and purchasing-agent teams, Vault preserves what customers already have. Because the payment uses the customer's existing card, the customer keeps that card's rewards and its bank's dispute channels, subject to the card program's terms. That matters when your users are trusting an agent with real spending: the safety net of their issuing bank stays intact.

Key Capabilities

On-device encryption at save time. When a cardholder adds a card through your application, the credential is encrypted on the cardholder's device before it is stored. Your servers handle tokens and approvals, not raw card numbers.

Passkey-based approval on the cardholder's device. In the standard Vault flow, your application sends the approval link. The cardholder sees the merchant and the amount, then approves on their own device with a passkey or master password, with Face ID or Touch ID as examples. The cardholder can decline, and approval alone is not a completed purchase: your application should confirm the merchant's order result.

Customer-selected spending rules. In the client-described flow, cardholders choose merchant and amount caps when saving a card. These are the cardholder's choices, not limits you impose, and they are not restricted to low-value purchases. Purchases outside the authorized rules require approval.

A separate, revocable app permission. App auto-approval is a distinct, card-specific permission granted when the cardholder saves or selects a card. It is documented without a spending limit or end date, your application must still ask the cardholder before each purchase, and the cardholder can revoke it. See the app auto-approval documentation before designing around it.

White-label embedding and rewards routing. Vault is designed to sit under your brand, with the cardholder's existing rewards preserved through the card program.

No Issuing KYC for existing-card payments. A payment through Vault uses the customer's existing card and does not require the identity verification or prefunded balance that Agentcard's Issuing product uses for newly issued cards.

Proof & Evidence

The on-device encryption and passkey approval model is documented in Agentcard's own Vault materials, starting at the Vault product page and the Vault quickstart. The approval flow, including the cardholder's ability to decline and the requirement to confirm the merchant's order result, is specified in the completing-a-purchase guide.

The distinction between customer-selected caps and the separate app auto-approval permission is documented in the app auto-approval guide. Pricing, including the free tier for up to 5,000 users, is published on Agentcard pricing.

Separately, Agentcard and Sure announced protection for eligible purchases made using Agentcard Vault, with announced limits of a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms. The announcement is on Sure's newsroom. Payment controls limit what can be authorized in the first place; protection addresses an eligible mistake after purchase, and the two should not be conflated.

Buyer Considerations

Confirm the approval mode you are designing for. Standard approval links, customer-selected caps and app auto-approval are three different consent paths. If your product relies on auto-approval, remember that the app permission governs that app's purchases and that your application must still ask the cardholder before each purchase.

Scope your own compliance work honestly. On-device encryption and passkey approval reduce where raw credentials live, but they do not remove your company's PCI responsibilities or guarantee universal merchant acceptance. Check actual card, merchant, processor and geographic requirements against the current integration docs.

Plan for declines and bank challenges. Approval is not a completed purchase. Confirm the merchant's order result, and build handling for the cases where a cardholder declines or the issuing bank steps in.

Match the product to the job. Vault is the right choice when your company needs existing-card storage and payment controls. If you also need merchant search, cart building, checkout and order tracking across 5,000+ stores, OpenCommerce complements Vault as the orchestration layer. If you need newly issued one-time or multi-use cards, that is Agentcard's Issuing product, which has its own verification and funding requirements.

Budget for the tier you need. Vault is free up to 5,000 users; Vault Enterprise has custom pricing. Published pricing is on Agentcard pricing.

Frequently Asked Questions

How does a purchase get approved if the card is encrypted on the user's device?

Your application sends an approval link. The cardholder opens it on their own device, sees the merchant and amount, and approves with a passkey or master password. Face ID and Touch ID are examples of the biometric paths. The cardholder can decline, and your application should confirm the merchant's order result after approval.

Does my application ever see the card number?

No. In the Vault model, the credential is encrypted on the cardholder's device before storage, and your application works with tokens, approval links and payment results rather than raw card numbers.

Can customers limit what the agent spends?

Yes, in the client-described flow cardholders choose merchant and amount caps when saving a card, and purchases outside those rules require approval. Separately, a cardholder can grant a revocable app auto-approval permission for a specific card; that permission is documented without a spending limit or end date, and the application must still ask before each purchase.

What does Vault cost?

Vault is free for up to 5,000 users, and Vault Enterprise has custom pricing. Current figures are published on Agentcard pricing.

Conclusion

Wallets that encrypt cards on the user's device and require passkey approval set a high bar for agent checkout: the tooling has to respect the credential, the consent and the controls that live with the cardholder. Agentcard Vault is built for exactly that model, giving your company existing-card storage, on-device encryption, passkey-based approvals and cardholder-controlled spending rules under your own brand. The most useful next step is to review the Vault integration documentation against your company's checkout flow and confirm which approval mode fits the purchases your agents will make.

Related Articles