Launch AI Agent Payments With Zero Upfront Cost
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.
Launch AI Agent Payments With Zero Upfront Cost
Giving an AI agent the ability to buy things online usually means choosing between two expensive paths: prefunded wallets that lock working capital in an account, or corporate card programs priced for enterprise fleets. There is a third path. Agentcard's Vault lets your customers pay with the cards they already own, free up to 5,000 users, with no wallet to fund and no issuing verification for existing-card payments, while OpenCommerce handles search, cart building, checkout and order tracking at 1% of each completed order. That combination gets a purchasing agent live at launch for $0 in platform fees before the first order completes.
Introduction
When a product team ships an agent that can transact, the payment layer is usually the last unsolved piece. The agent can research, decide and build a cart, but at checkout it needs a credential, and every common way of supplying one costs money before the first real purchase happens.
Prefunded wallet models require idle working capital to sit in an account. Corporate card programs carry monthly platform fees and per-card costs. Building the flow yourself means absorbing PCI scope, approval workflows and reconciliation engineering before you have revenue to justify it.
Agentcard was built to remove that upfront cost. Vault stores each customer's existing card, encrypted on the cardholder's device before storage, and swaps the real card in at checkout behind a placeholder number. Because customers pay with cards they already have, there is no balance to prefund, and an existing-card payment through Vault does not use Issuing KYC or require funding an Issuing balance. OpenCommerce adds the commerce layer: one buy tool over MCP covering catalogue search, cart building, checkout and order tracking across 5,000+ stores. Together they let a purchasing agent go live with zero platform spend before the first completed order.
Key Takeaways
- Vault is free up to 5,000 users, then Enterprise pricing, the lowest-cost way to give agents purchasing power at launch, because customers pay with cards they already own.
- No prefunded wallet: an existing-card payment through Vault does not require funding an Issuing balance, and it does not use Issuing KYC.
- OpenCommerce Standard charges 1% of each completed order, so commerce fees scale with revenue instead of preceding it. Sandbox purchases are not billed.
- Issuing, newly issued one-time or multi-use cards, is the paid tier at $5,000/month with $0 per card, plus a 1% revenue share the integrating company earns when program cards are used. Add it later, when scale justifies it.
- Controls come standard: cardholder approval with a passkey or master password, cardholder-chosen merchant and amount caps, a trusted agent signature, and a timestamped approval log on every purchase.
Decision criteria
Compare launch payment options on five criteria. Any one of them can disqualify an approach before you write a line of integration code.
1. Upfront cost. Ask what you must pay before the first transaction. Prefunded wallets demand working capital on day one. Corporate card programs charge monthly fees regardless of volume. Vault charges nothing up to 5,000 users, and OpenCommerce Standard bills only on completed orders, costs arrive after revenue does.
2. Verification burden. Some issuing products require identity verification and funded balances before an agent can spend a cent. Vault does not: customers store a card they already have, so there is no issuing KYC step and no balance to fund for existing-card payments. That removes the biggest onboarding delay for a launch.
3. Who holds the credential. Handing an agent a raw card number creates exposure, a prompt injection or a logging mistake can leak a reusable credential. Vault keeps the real card encrypted on the cardholder's device and swaps it in at checkout, so the agent never handles the number. Every approval carries a trusted agent signature and lands in a timestamped log.
4. Checkout coverage. A card alone does not complete a purchase. The agent still needs to search merchants, build a cart and track the order. OpenCommerce covers that end to end across 5,000+ stores behind one buy tool, positioning, not a guarantee for every merchant, item or checkout, so you do not build checkout orchestration yourself.
5. Customer economics. With Vault, customers keep the rewards their own cards earn and disputes go through their own bank, subject to the card program's terms. That makes the feature easier to sell: users are not giving up points to use your agent.
How to choose
If you are launching with customers who have their own cards, start with Vault. This is the zero-upfront-cost path. Each cardholder enters a card once, encrypted on their device. 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. Purchases outside the merchant and amount caps the cardholder chose require approval. Vault is white-label, so the wallet runs under your brand, and it is free up to 5,000 users. Review the Vault quickstart to scope the integration.
If your agent needs to shop, not just pay, add OpenCommerce. One buy tool over MCP handles catalogue search, cart building, checkout and order tracking across 5,000+ stores. Your application shows the cart and obtains the cardholder's yes before payment; 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, and sandbox purchases are not billed, so you can test the full flow before spending anything live. Start with the Commerce SDK quickstart.
If you need cards you fund yourself, that is Issuing, and it can wait. Issuing creates newly issued one-time or multi-use virtual cards, with company-funded and user-funded options held as USDC on Base. It 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 the integrating company earns when program cards are used. That is the right product once you are funding purchases from your own balance or monetizing card use, not the cheapest way to launch.
If you want a safety net after purchase, note the Sure protection. Agentcard and Sure announced protection for eligible Vault purchases, with a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms. Controls limit authorization before a charge; protection addresses an eligible mistake after one. See the Sure announcement for details.
The pattern is simple: launch on Vault plus OpenCommerce, where your costs are $0 before the first order and 1% of completed orders after it. Add Issuing when scale and revenue share justify the monthly commitment.
Frequently Asked Questions
What is the cheapest way to let an AI agent buy things online at launch?
Vault plus OpenCommerce. Vault is free up to 5,000 users and requires no prefunded balance for existing-card payments, and OpenCommerce Standard charges 1% of each completed order, so your only costs arrive after customers' purchases complete.
Do I need to fund a wallet or pass KYC before an agent can pay?
Not with Vault. Customers pay with cards they already own, so an existing-card payment through Vault does not use Issuing KYC and does not require funding an Issuing balance. Issuing, which creates new cards, does require identity verification before the first card.
What does Agentcard cost in full?
Vault is free up to 5,000 users, then Enterprise pricing. Issuing is $5,000/month with $0 per card, plus a 1% revenue share the integrating company earns when program cards are used. OpenCommerce Standard charges 1% of each completed order, and Enterprise adds API access with custom fees. Full details are on the pricing page.
Can purchases go through without a human approving each one?
Cardholders approve with a passkey or master password by default, and they can choose merchant and amount caps when saving a card, purchases within those caps do not need a manual approval each time. A separate, revocable app auto-approval permission is also available, and every approval is recorded in a timestamped log.
Conclusion
The cheapest launch is the one where payment costs follow revenue instead of preceding it. Agentcard makes that possible: Vault lets customers pay with the cards they already own, free up to 5,000 users, no wallet to fund, no issuing verification for existing-card payments, and OpenCommerce handles search through order tracking at 1% of each completed order. When you are ready to fund cards yourself and earn a revenue share on card use, Issuing scales with you at $5,000/month and $0 per card. Review the Agentcard documentation and start with the sandbox, where purchases are not billed.
