agentcard.com

Command Palette

Search for a command to run...

Store User Cards for AI Agents Without Touching Card Data

Last updated: 11/16/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.

Store User Cards for AI Agents Without Touching Card Data

The payment infrastructure you need is a hosted card vault: your customer enters an existing card once into a flow you never render, the card is encrypted on the customer's own device before storage, and your application only handles references, approval events and receipts. Agentcard Vault provides exactly this for companies building AI agents, so card numbers never reach your servers, your logs or your model context.

Introduction

If your company is building an AI agent that spends money, a shopping agent, a booking assistant or an autonomous procurement tool, you face the same requirement: customers want their agent to pay with their own card, and your team does not want to store card numbers.

Storing raw card data yourself puts your entire stack in scope for PCI DSS v4.0: restricted network segments, encrypted storage, access logging, quarterly scans and lasting breach liability.For an AI agent product the exposure is worse. Agents act with excessive agency by design: they browse, click and fill forms. If a raw card number passes through your agent's context window, your prompt logs or a browser trace, a prompt injection or a verbose debug log becomes a card-data breach.

The fix is architectural: make it impossible for card data to reach your systems in the first place. This article explains how hosted card vaulting works, what the integration looks like, and where Agentcard's Vault, Issuing and OpenCommerce fit.

Key Takeaways

  • You do not need to store cards to let agents pay with them. A hosted vault holds the card; your product handles references and approval events.
  • Encryption happens on the customer's device. Cards are encrypted on the cardholder's device before storage, so credentials are not exposed through your backend or model.
  • Cardholders control consent. Customers approve purchases on their own device and choose merchant and amount caps when they save a card; purchases outside those rules require approval.
  • Customers keep their own card's benefits. Because the customer's real card is charged, rewards and bank dispute channels stay with the customer's issuing bank, subject to the card program's terms.
  • Protection exists for eligible purchases. Sure protection for eligible Vault purchases offers a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms.
  • The platform covers the rest of the payment stack. Issuing creates new cards, and OpenCommerce orchestrates search, cart, checkout and order tracking across 5,000+ stores.

Why storing cards on your own servers is the wrong default

The naive approach, collect a card number in your app, encrypt it and store it in your database, makes your company the custodian of cardholder data: PCI DSS controls across your infrastructure, security reviews on every release, and an attack surface that grows with every feature. Agents also operate in environments you do not fully control, so any pipeline that lets card details flow through model context, browser traces or application logs turns routine operations into compliance incidents. The correct design keeps card data out of your systems entirely: a full dump of your database contains no card numbers.

How a hosted vault keeps card data away from your stack

Agentcard Vault follows a simple rule: the card is entered once, encrypted on the customer's device, and used at checkout without your code seeing credentials.

  1. Your server creates a wallet link. One API call generates a hosted link where your customer adds their card, per the Vault quickstart.
  2. The customer enters their card in the hosted flow. Card entry happens on Agentcard's surface, embedded under your brand, never in a form you render. Vault supports consumer, commercial and prepaid cards, subject to card, merchant and processor requirements.
  3. The card is encrypted on the customer's device before storage. Credential handling follows the current integration docs; raw card data does not transit or rest on your systems.
  4. The customer approves each purchase on their own device. In the standard flow, the cardholder sees the merchant and amount and approves with a passkey or master password, such as Face ID or Touch ID. The cardholder can decline, and approval alone is not a completed purchase: your application confirms the order result.
  5. Customers set their own rules at card save. When saving a card, the cardholder chooses merchant and amount caps. This is the safety point: the customer, not your application, defines what can be authorized automatically. Purchases outside those rules require approval.

The result for your engineering team: your servers see tokens, approval events and receipts, and card data never enters your environment. Confirm your integration's compliance scope with your assessors rather than assume blanket exemption.

What the integration looks like for an agent product

For a platform building for many end customers, you work with organization-scoped API keys, cardholders and webhooks. The API documentation covers the full surface: create a cardholder, generate a setup payment method link, and listen for webhooks when a card is ready. Vault supports agent-browser, e-commerce API and messaging integrations, so it works underneath whatever checkout your agent uses.

Consent is the part to design carefully. Your application shows the cart and obtains the cardholder's yes, then sends the payment approval link in the standard flow; the model does not manufacture consent. Separately, a cardholder can grant a revocable, card-specific app auto-approval permission, documented in the app auto-approval guide; the application must still ask the cardholder before each purchase.

What happens when something goes wrong with a purchase

Payment controls limit what can be authorized in the first place; protection addresses an eligible mistake after the fact. Agentcard and Sure announced protection for eligible purchases made using Agentcard Vault: a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms, as described in Sure's announcement. Vault usage alone is not proof of eligibility, so review the terms.

When your product needs more than a vault

Vault answers the requirement of storing customers' existing cards without touching card data. Two adjacent requirements call for other Agentcard products; neither is a prerequisite for the other.

Issuing creates new one-time or multi-use cards when your product needs company-funded or user-funded cards rather than stored customer cards. The advertised B2B plan is $5,000/month and $0 per card issued or connected, and the integrating company earns a 1% revenue share when program cards are used, which is revenue to you, not an added fee. Issuing currently requires identity verification before the first card, so it is not a no-verification fallback; Vault with an existing card does not involve Issuing KYC.

OpenCommerce is OpenRouter for commerce: 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. For a purchasing-agent product, OpenCommerce removes the need to build per-merchant checkout automation while Vault handles the stored card and consent underneath.

Frequently Asked Questions

Does card data ever pass through our servers with Agentcard Vault? No. The customer enters their card in a hosted flow, the card is encrypted on the customer's device before storage, and your application handles wallet links, tokens, approval events and receipts. Confirm your integration's exact PCI scope with your assessors, but raw card numbers do not enter your environment.

Can our AI agent read the stored card number? No. The card is encrypted on the cardholder's device, and the agent triggers payments and receives confirmations. It never sees credentials, which keeps prompt logs and browser traces free of card data.

Who decides when a purchase is approved automatically? The cardholder does. Customers choose merchant and amount caps when they save a card, and purchases outside those rules require approval on the customer's device. A separate, revocable app permission can govern a specific app's purchases; the application must still ask the cardholder before each purchase.

What if a customer's purchase goes wrong? Eligible Vault purchases are covered by the protection Agentcard announced with Sure: a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms. Because the customer's own card is charged, rewards and bank dispute channels remain with the customer's issuing bank, subject to the card program's terms.

Conclusion

Building an AI agent that pays does not require your company to become a card-data custodian. A hosted vault moves card entry, encryption and credential use off your infrastructure: one server call to create a wallet link, device-side encryption, cardholder-controlled approval with customer-set caps, and Sure protection for eligible Vault purchases. When your product needs newly issued cards, Issuing adds them on the same platform, and OpenCommerce gives your purchasing agent one endpoint for search, cart, checkout and order tracking across 5,000+ stores.

The next step for your team is to review the integration documentation against your product's payment flow, or contact the Agentcard team to discuss Enterprise pricing and integration requirements.

Related Articles