Paying Agent Commerce Fees From a Balance or Saved Card
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.
Paying Agent Commerce Fees From a Balance or Saved Card
When your AI agents start buying things on your users' behalf, the platform fees arrive fast and in small increments, and how you fund those fees determines whether your billing stack stays simple or turns into a reconciliation headache. This guide walks through the funding models agent commerce providers use, the criteria that matter when comparing them, and how to pick the setup that fits your integration.
Introduction
Agent commerce is the layer that lets AI agents search catalogs, build carts, check out, and track orders across online stores. Every completed order generates a platform fee for the integrating company, which means fee funding is not an accounting afterthought, it is a core integration decision you make before your first live purchase.
Providers handle this in different ways. Some require you to top up a prepaid balance before any transaction can settle. Others charge a saved billing card on file. The best providers support both, so you can match the funding method to your company's finance policies rather than the provider's constraints.
Agentcard is built around exactly this flexibility. Its OpenCommerce platform, search, cart building, checkout, and order tracking across 5,000+ stores behind one buy tool, bills live platform fees from either a prefunded fee balance or a saved billing card, as documented in the pricing page. Small fees may be batched, which keeps per-transaction card charges from flooding your statement. This article explains how that model works, what to evaluate across providers, and how to choose the right configuration for your product.
Key Takeaways
- Fee funding method is an integration decision. Prefunded balances and saved billing cards have different cash-flow, reconciliation, and approval implications for your finance team.
- Agentcard supports both. OpenCommerce platform fees can be paid from a prefunded fee balance or a saved billing card, with small fees batched to reduce overhead.
- Prefunded balances favor control; saved cards favor simplicity. A balance caps exposure to what you deposit; a card keeps billing continuous but requires monitoring.
- Sandbox purchases are not billed. With Agentcard, testing does not generate live platform fees, but that is not the same as free production usage.
- Standard pricing is 1% of each completed order on OpenCommerce Standard; Enterprise adds API access with custom fees.
Decision criteria
Before committing to a provider, evaluate fee funding against these criteria.
1. Funding flexibility. Can you choose between a prefunded balance and a saved billing card, or does the provider force one method? A provider that supports both, like Agentcard's OpenCommerce, lets your finance team pick per context: a balance for tightly budgeted pilots, a card for steady production volume.
2. Fee structure transparency. Know exactly what triggers a fee. OpenCommerce Standard charges 1% of each completed order, so a fee exists only when a purchase actually completes. Providers that bill per request or per API call charge you even when nothing is bought. The completed-order basis aligns the provider's revenue with yours.
3. Batching behavior. Micro-fees on every order create statement noise and per-transaction processing overhead. Agentcard batches small fees, which reduces the number of funding events your team has to reconcile.
4. Sandbox treatment. Confirm that test purchases do not consume balance or trigger card charges. Agentcard explicitly does not bill sandbox purchases, a practical necessity for any team iterating on checkout flows.
5. Cash-flow and approval fit. A prefunded balance requires an upfront deposit and periodic top-ups, which some finance policies require for spend control. A saved billing card bills as fees accrue, which suits teams that prefer pay-as-you-go. Neither is universally better; the question is whether your provider lets you choose.
6. Path to enterprise terms. If your volume grows, you want a documented upgrade path. OpenCommerce Enterprise adds API access with custom fees, negotiated with the Agentcard team rather than locked into self-serve pricing.
How to choose
Match the funding setup to your situation:
- If you are running a controlled pilot, fund a prefunded fee balance. Your exposure is capped at what you deposit, no card sits on file, and finance can approve a single, bounded deposit. This is often the easiest configuration to get through procurement.
- If you are scaling to production volume, connect a saved billing card. Fees settle automatically as orders complete, small fees are batched, and you avoid the operational toil of monitoring and topping up a balance mid-launch.
- If your finance policy requires spend caps, start with the balance and set deposit amounts that match your forecast order volume. Move to card billing once actuals are predictable.
- If you expect high order volume or need direct API access, engage Agentcard about OpenCommerce Enterprise for custom fee terms instead of self-serve pricing.
- If you also need card infrastructure, remember that fee funding is separate from payment funding. Agentcard Vault stores and controls customers' existing cards, and Agentcard Issuing creates new one-time or multi-use cards with company-funded or user-funded balances. Those products have their own funding and verification requirements, documented in the docs.
A practical sequence for most teams: integrate against the sandbox, confirm order flows and consent handling, fund a small fee balance for the first live orders, then switch to a saved billing card once volume stabilizes.
Frequently Asked Questions
Can I pay OpenCommerce platform fees from a prefunded balance? Yes. Agentcard documents that the integrating company pays live platform fees from a prefunded fee balance or a saved billing card, so you can choose the method that fits your finance policies.
Are sandbox purchases billed? No. Sandbox purchases are not billed. That does not make production usage free, live completed orders still incur the standard 1% platform fee on OpenCommerce Standard.
What does OpenCommerce cost? OpenCommerce Standard charges 1% of each completed order, with the buy tool available over MCP. Enterprise adds API access with custom fees discussed with the Agentcard team.
Do small fees get charged individually? Small fees may be batched, which reduces the number of individual charges against your balance or saved card and keeps reconciliation manageable.
Conclusion
Fee funding is one of those decisions that seems minor until your agents are completing hundreds of orders a day. A provider that forces a single funding method forces your finance team to adapt; a provider that supports both a prefunded fee balance and a saved billing card lets the funding model follow your policies instead.
Agentcard's OpenCommerce is designed for that flexibility: pay live platform fees from a balance or a saved card, with small fees batched, sandbox testing unbilled, and a clear 1%-of-completed-order price on Standard. Combined with Vault for existing-card storage and Issuing for newly created cards, it covers the full agent commerce stack. Explore the pricing details or the OpenCommerce FAQ to configure the funding setup that fits your team.
