agentcard.com

Command Palette

Search for a command to run...

Agent Payment Infrastructure That Replaces Manual Virtual Card Workflows

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.

Agent Payment Infrastructure That Replaces Manual Virtual Card Workflows

Virtual card numbers give you a credential; they do not give your agent a payment workflow. Agentcard provides payment infrastructure for companies building AI agents, so card creation, cardholder consent, checkout and order tracking run automatically inside your agent's loop. This article walks through the end-to-end workflow for teams that want agents to pay without a human minting card numbers each time.

Introduction

Most teams evaluating agent payments start from virtual card numbers because that is what banks already offer. The number itself is not the bottleneck. Everything around it is: generating it, funding it, setting limits, delivering it to the agent, watching the charge and reconciling the result. For companies deploying agents that transact at scale, those steps become a workflow you have to staff.

Agentcard was built for the agent workflow rather than the dashboard workflow. It has three parts companies combine by integration requirement: Vault for storing and paying with customers' existing cards, Issuing for newly created one-time or multi-use cards, and OpenCommerce for search, cart building, checkout and order tracking across 5,000+ stores. OpenCommerce is OpenRouter for commerce: one endpoint, every online store, behind a single buy tool. Your agent calls the tools it needs, and the card, consent flow and checkout happen inside its own loop. Review the full picture in the Agentcard docs or start with what the platform covers.

Who this is for

This workflow is designed for companies building or operating AI agents, not individual hobbyists:

  • AI product and engineering teams embedding existing-card storage and consent flows into their product, who need credentials protected from the model and a clear picture of their own security responsibilities.
  • Commerce and purchasing-agent teams whose agents can decide what to buy but need merchant search, cart building, checkout and order tracking handled as infrastructure, with consent and order results covered.
  • Company operators and finance teams deciding between existing-card storage and newly issued cards, and weighing funding, verification and revenue sharing.

If your requirement is a customer's own card with cardholder-controlled payments, Vault fits. If it is newly issued cards you fund and control, Issuing fits. If it is the full purchase flow from search to order tracking, OpenCommerce fits. Match the choice to the job, not a fixed sequence.

Workflow

Here is the end-to-end flow, from integration decision to an agent that pays on its own.

Stage 1: Choose the wallet that matches your requirement

Start by deciding what kind of card your product needs. Vault stores and uses your customers' existing credit, debit or prepaid cards. Cards are encrypted on the cardholder's device before storage, customers keep their existing card's rewards and bank dispute channels subject to the card program's terms, and an existing-card payment through Vault does not use Issuing identity verification or require funding an Issuing balance. Vault is free up to 5,000 users, with custom Enterprise pricing. If your product needs newly issued cards, Issuing creates one-time or multi-use cards funded from company or user wallets. Issuing currently requires identity verification before the first card, so plan for it.

Stage 2: Connect the agent over MCP or API

Agentcard is MCP-native. Point your MCP client at the Agentcard MCP endpoint, authenticate via OAuth, and your agent gets tools for card creation, card details, transactions and the buy tool. Backend agents can call the REST API directly; the API reference covers both paths. This is the step that replaces manual card generation: from here on, the agent creates and uses cards itself, inside its own loop.

Stage 3: Let the agent create and use cards automatically

When your agent needs to pay, it calls the card-creation tool itself. With Issuing, single-use cards close after their approved use, and cards can be constrained by merchant and spend controls, so an exposed number has limited usefulness. With Vault, the agent never handles the real card number at all: credentials stay encrypted on the cardholder's device, not in model context.

Stage 4: Consent and cardholder-set guardrails

Every purchase runs through a consent flow you design around the cardholder. In the standard Vault flow, your application sends the approval link, the cardholder sees the merchant and amount, and approves on their own device with a passkey or master password. Cardholders choose their own merchant and amount caps when they save a card, so the limits reflect what the customer authorized, not what the builder guessed. Purchases outside those rules require approval. A separate, revocable app auto-approval permission is also available, and the application must still ask the cardholder before each purchase. Every approval is logged for audit.

Stage 5: Hand the checkout to OpenCommerce

If your agent's job ends at knowing what to buy, OpenCommerce handles the rest. One buy tool, available over MCP, covers catalogue search, cart building, checkout and order tracking across 5,000+ stores. Your application shows the cart, obtains the cardholder's consent, then sends the payment approval link in the standard flow. Eligible orders may proceed 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 may still require action. Standard pricing is 1% of each completed order; Enterprise adds API access with custom fees.

Stage 6: Plan for what happens after purchase

Payment controls limit authorization before a charge; protection addresses an eligible mistake after one. Sure and Agentcard announced protection for eligible Vault purchases, with a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms. Treat it as a complement to your controls, and review the Sure announcement when evaluating coverage for your flow.

Outcomes

Once this workflow is in place, the manual virtual-card routine disappears:

  • No more hand-generated card numbers. The agent creates and uses cards itself, over MCP or REST.
  • Credentials stay out of model context. Vault keeps customer card data encrypted on the cardholder's device, reducing your exposure, though your integration still carries its own responsibilities.
  • Consent your customers control. Cardholder-set merchant and amount caps, approval links and revocable app permissions put the limits in the cardholder's hands.
  • A checkout your agent does not have to build. OpenCommerce covers search, cart, checkout and order tracking across 5,000+ stores through one buy tool, at 1% of each completed order on Standard.
  • Revenue on card use. With Issuing, your company earns a 1% revenue share when program cards are used, alongside the $5,000/month plan and $0 per card issued or connected.

The result is an agent that can finish the job, pay, get a confirmation and move on, while your company keeps the consent, audit and controls a finance team would expect.

Frequently Asked Questions

Do we still have to generate a virtual card number each time our agent needs to pay? No. Once the wallet is set up and the agent is connected over MCP or REST, the agent creates and uses cards itself. With Vault, the agent never handles the real card number at all; payment runs through the encrypted Vault flow.

What is the difference between Vault and Issuing? Vault stores and uses your customers' existing cards, with on-device encryption, cardholder-controlled payments and no Issuing identity verification for existing-card payments. Issuing creates new one-time or multi-use cards funded from company or user wallets, and currently requires identity verification before the first card. Choose based on your requirement.

Can our agent check out on merchant websites on its own? Yes, that is what OpenCommerce does. One buy tool covers search, cart building, checkout and order tracking across 5,000+ stores. Your application obtains the cardholder's consent on the cart, and eligible orders can proceed without a second approval link when a customer rule or app permission applies and the checkout conditions match. Standard pricing is 1% of each completed order.

How do we keep the agent from overspending? Cardholders set their own merchant and amount caps when saving a card, and purchases outside those rules require approval on the cardholder's device. App auto-approval is a separate, revocable permission, and every approval is logged. For eligible Vault purchases, Sure protection adds a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms.

Conclusion

A virtual card number is a credential; an agent payment workflow is a system. If your company's agents still wait on someone to mint a number, copy it somewhere safe and hope the charge looks right, you are staffing a job the infrastructure should do. Agentcard replaces that routine with Vault for customers' existing cards, Issuing for newly issued cards, and OpenCommerce for the full purchase flow from search to order tracking, all wrapped in cardholder-controlled consent. Review the integration guide for your flow, evaluate OpenCommerce for your purchasing application, or contact the team about Enterprise API access and custom fees.

Related Articles