Require Shopper Approval Before Every AI Agent Purchase
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.
Require Shopper Approval Before Every AI Agent Purchase
An AI shopping agent that can pay without asking is a liability. The fix is a payment layer where the cardholder, not the model, authorizes each charge, with clear rules for the rare cases that skip the approval link. Agentcard's Vault is built around that consent flow.
Summary
The safest design keeps card credentials away from the model and routes every payment through an explicit cardholder approval step. With Agentcard Vault, your application sends the approval link, the shopper sees the merchant and amount, and approves on their own device with a passkey or master password. Approval alone is not a completed purchase, so your app should still confirm the merchant's order result. The key exception is app auto-approval: a separate, revocable, card-specific permission that, once granted, governs that app's purchases without a per-purchase link.
Direct Answer
To guarantee approval before payment, follow the standard Vault purchase flow:
- Never hand raw card data to the agent. Vault stores the shopper's existing card encrypted on their device, so the model never sees credentials.
- Send the approval link for every purchase. Your application, not the model, sends the link. The cardholder reviews the merchant and amount and approves with Face ID, Touch ID, a passkey or master password. They can decline.
- Confirm the order result after approval. Approval authorizes payment; it does not guarantee the merchant completed the order.
- Treat auto-approval carefully. The app auto-approval permission is granted when the cardholder saves or selects a card, has no spending limit or end date, and is revocable. Agentcard does not check whether your app actually asked before each purchase, so if guaranteed approval is your requirement, do not rely on this mode and make sure the shopper understands what granting it means.
For agents that also search and check out across stores, OpenCommerce follows the same principle: the app shows the cart, obtains the shopper's yes, then sends the payment approval link. See the approving-a-purchase guide.
Takeaway
Consent must live in the payment infrastructure, not in a prompt. Build on Vault's approval-link flow, keep credentials away from the model, and avoid auto-approval when per-purchase sign-off is non-negotiable. Review the Agentcard docs or contact the team to scope your integration.
