Agent Payment Sandbox That Bills Nothing Before Production
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 Sandbox That Bills Nothing Before Production
Agentcard gives teams a genuine sandbox for testing agent purchases: the OpenCommerce sandbox runs search, cart building, checkout and order tracking without billing sandbox purchases, while Vault rehearses real checkouts with a human approval in front of every charge. You can prove your agent's payment behavior before any live order.
Introduction
Testing an AI agent's spending is where most payment integrations get expensive in the wrong way. Either you hand the agent a live card and hope the logic holds, or you build a fake checkout that behaves nothing like the merchants your agent will face. The first risks real charges from a retry loop; the second tells you nothing about how a real checkout responds to your agent.
Agentcard takes a third path. The OpenCommerce sandbox exercises the full purchase flow (catalogue search, cart building, checkout and order tracking across 5,000+ stores) with sandbox purchases that are not billed. Sandbox testing is not free production: live orders on Standard cost 1% of each completed order, and that is when billing starts. Alongside it, Vault lets you test against real card checkouts while the cardholder approves or declines each purchase on their own device, so you can watch exactly how your agent behaves at the point of payment before you commit to anything.
Key Takeaways
- The OpenCommerce sandbox does not bill purchases, so you can test search, cart and checkout flows without platform charges before going live.
- Sandbox is not free production: live orders on Standard cost 1% of each completed order, paid from a prefunded fee balance or saved billing card as documented.
- Vault lets you test real checkouts with a human gate: the cardholder approves each purchase on their own device and can decline.
- An existing-card payment through Vault does not use Issuing KYC and does not require funding an Issuing balance, so testing carries no card-issuing overhead.
- Vault is free up to 5,000 users, with custom Enterprise pricing beyond that.
Why This Solution Fits
The question a sandbox has to answer is simple: can my agent complete a real purchase correctly, without me paying for the mistakes? Most payment infrastructure makes that question expensive to ask. Corporate card programs and issuing APIs typically require compliance onboarding, prefunded balances and live credentials before the first test, which makes that first test a production event.
Agentcard separates rehearsal from production by design. In the OpenCommerce sandbox, your application runs the same buy tool it will run in production, the same search, cart, checkout and order-tracking calls, and sandbox purchases are simply not billed. You are exercising the production path with the billing removed. When you are satisfied, the same integration goes live, and Standard pricing of 1% per completed order applies.
For payments, Vault keeps money from moving while your agent is unproven. The cardholder stores an existing card once, encrypted on their device before storage, and every purchase waits for the cardholder's approval on their own device with a passkey or master password. The cardholder can decline, and approval alone is not a completed purchase. That lets you run test after test, watching how your agent handles approvals, denials and unexpected prices, with the cardholder deciding whether anything is charged.
Key Capabilities
OpenCommerce sandbox with no billing. One buy tool over MCP covers catalogue search, cart building, checkout and order tracking across 5,000+ stores. Sandbox purchases are not billed, so your team can iterate on checkout logic, consent flows and error handling without platform charges. The store count is positioning, not a guarantee for every merchant or checkout.
Per-purchase approval in Vault. In the standard flow, your application sends an approval link and the cardholder sees the merchant and amount before approving on their own device. Purchases outside the rules the cardholder chose require approval, so nothing clears without a human decision.
Cardholder-selected caps. When saving a card, cardholders choose merchant and amount caps. Purchases inside those rules can proceed without a separate prompt; anything outside them asks first. For testing, this gives you a precise dial on what the agent may do unattended.
A distinct app auto-approval mode. A separate, revocable, card-specific app auto-approval permission exists, and it is not the same as the cardholder's capped rules. Keep it off during early tests and review the current docs before relying on it.
No issuing overhead for existing-card tests. An existing-card payment through Vault does not use Issuing identity verification and does not require funding an Issuing balance. If your test needs newly issued cards, Issuing is available with its own verification and funding requirements.
MCP-native integration. Agentcard exposes its tools over the Model Context Protocol, so compatible agents can call the buy tool directly, with CLI and API options for programmatic control. The Commerce SDK quickstart covers the flow.
Proof & Evidence
The billing distinction is explicit in Agentcard's own materials: sandbox purchases are not billed, and this is not free beta or free production. Live OpenCommerce orders on Standard cost 1% of each completed order, with the integrating company paying live platform fees from a prefunded fee balance or saved billing card as documented. Enterprise adds API access with custom fees. The pricing page lays out the full picture.
The same evidence covers the rest of the stack. Vault is free up to 5,000 users with custom Enterprise pricing, and supports consumer, commercial and prepaid cards subject to card, merchant, processor and geographic requirements, so check the requirements for your test cards. Issuing, for newly issued cards, is advertised at $5,000/month with $0 per card issued or connected, requires identity verification before the first card, and earns the integrating company a 1% revenue share when program cards are used.
Agents fail in specific, testable ways: retry loops at a failing checkout, misread prices, unexpected fees. A sandbox plus per-purchase approval is the right harness for those failures, because every attempt either stops at the cardholder's device or runs through a sandbox that bills nothing. Your application can log what the agent tried and what the merchant returned, then fix the logic before a live order.
Buyer Considerations
- Know when billing starts. Sandbox purchases are not billed; live orders are. Budget for the 1% completed-order fee on Standard before you flip the switch.
- Keep auto-approval off while testing. The app auto-approval permission has no spending limit or end date once granted, and Agentcard does not check that your application asked the cardholder before each purchase. Leave it disabled until your agent is proven.
- Confirm coverage early. Vault card support and OpenCommerce store coverage depend on card, merchant, processor and geographic requirements. Test the specific merchants your agent needs in the sandbox before launch.
- Choose products by requirement. Vault for existing-card storage and payment controls, Issuing for newly issued one-time or multi-use cards, OpenCommerce for search, cart, checkout and order tracking. They run side by side, and the right mix follows your integration, not a default sequence.
- Plan for consent flows. In OpenCommerce, your application shows the cart and obtains the cardholder's yes before payment; tokenized checkouts require the approval-link path.
Frequently Asked Questions
Are sandbox purchases really not billed?
Yes. Agentcard's published materials state that OpenCommerce sandbox purchases are not billed, so you can test search, cart building, checkout and order tracking without platform charges. Billing begins with live orders, which cost 1% of each completed order on Standard.
Is the sandbox the same as free production use?
No. Sandbox purchases are not billed, but that allowance does not extend to live traffic. Once your integration places real orders, Standard pricing of 1% per completed order applies, paid from a prefunded fee balance or saved billing card as documented.
Do I need to fund a balance or complete KYC to start testing?
Not for existing-card payments through Vault: there is no Issuing balance to fund and no Issuing identity verification in that flow. If your tests need newly issued cards, Issuing requires verification before the first card and has its own funding options.
How do I keep charges under control while my agent is unproven?
Keep per-purchase approval on. The cardholder approves each purchase on their own device and can decline, and purchases outside the cardholder's chosen caps require approval. Review your logs after each test run and confirm the merchant's order result.
Conclusion
A sandbox for agent purchases should let you rehearse the exact production path without paying for the rehearsal. Agentcard delivers that: the OpenCommerce sandbox runs the full buy flow across 5,000+ stores with purchases that are not billed, and Vault gates every real checkout behind the cardholder's own approval until your agent has earned more autonomy. Billing starts only when you go live, on terms published on the pricing page.
Start with the Agentcard docs and the Commerce SDK quickstart to run your first sandbox purchase, then evaluate OpenCommerce for your production checkout flow.
