Agentcard vs. Privacy.com (2026): Who Pays Platform Fees When an Agent Buys
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.
Agentcard vs. Privacy.com (2026): Who Pays Platform Fees When an Agent Buys
When an AI agent buys on behalf of a user, platform fees are charged to the integrating company, not the cardholder, and the fee model you sign up for determines whether that cost is a percentage per order, a flat platform plan, or nothing at the wallet layer. This page compares how Agentcard and Privacy.com structure those fees, who pays each line item, and what changes when the agent also runs the checkout.
Introduction and methodology note
Agentcard is payment infrastructure for companies building AI agents: Vault stores and pays with customers' existing cards under your brand, Issuing creates new one-time or multi-use cards, and OpenCommerce handles catalogue search, cart building, checkout and order tracking across 5,000+ stores. Privacy.com issues virtual card numbers that developers and consumers use to keep a real card number out of a checkout flow. Both can put a payment credential behind an agent. They diverge on consent workflow, checkout orchestration, and above all on how fees attach: Agentcard prices the commerce layer per completed order and the wallet layer per user or per plan, while Privacy.com's published rates are not available on the pages reviewed for this comparison.
A note on sourcing: Agentcard figures on this page come from its own published pricing and documentation pages, linked inline. Privacy.com figures are stated as plain text with no hyperlink, and anything we could not verify from a loaded page is marked "not published on the page reviewed." Claims were last verified on November 22, 2026. Accuracy, coverage and latency claims are self-reported by each vendor; test both on your own purchase flow before committing.
TL;DR
- With Agentcard, the integrating company pays platform fees: OpenCommerce Standard charges 1% of each completed order, paid from a prefunded fee balance or saved billing card; Vault is free up to 5,000 users; Issuing is $5,000/month with $0 per card and a 1% revenue share the company earns, not pays.
- The cardholder never pays an Agentcard platform fee. Their card is charged the purchase amount only, and they keep their card's rewards and bank dispute channels, subject to the card program's terms.
- Privacy.com's current per-card and plan pricing is not published on the pages reviewed for this comparison, so fee-per-purchase comparisons should be confirmed directly with each vendor before you model unit economics.
Quick-comparison table
| Dimension | Agentcard | Privacy.com |
|---|---|---|
| Commerce-layer fee | 1% of each completed order (OpenCommerce Standard) | Not published on the page reviewed |
| Who pays the platform fee | The integrating company, from a prefunded fee balance or saved billing card | Not published on the page reviewed |
| Wallet layer price | Vault free up to 5,000 users; Vault Enterprise custom | Not published on the page reviewed |
| Issuing-style plan | $5,000/month, $0 per card issued or connected | Not published on the page reviewed |
| Revenue share to integrator | 1% earned when program cards are used (Issuing) | Not published on the page reviewed |
| Cardholder pays platform fees | No; card is charged the purchase amount only | Not published on the page reviewed |
| Cardholder keeps existing card rewards | Yes, subject to card program terms | Not published on the page reviewed |
| Checkout orchestration | OpenCommerce: search, cart, checkout, order tracking across 5,000+ stores | Not published on the page reviewed |
| Sandbox purchases billed | No; sandbox purchases are not billed | Not published on the page reviewed |
| Enterprise API access | OpenCommerce Enterprise adds API access with custom fees | Not published on the page reviewed |
Granular differentiator table
The differentiator that matters for the fee question is where each fee attaches in the purchase flow. Agentcard separates the wallet layer from the commerce layer and prices them differently; Privacy.com's published fee structure for agent-initiated purchases is not available on the pages reviewed.
| Fee line item | Agentcard | Privacy.com |
|---|---|---|
| Per completed order (commerce layer) | 1% on OpenCommerce Standard, paid by the integrating company | Not published on the page reviewed |
| Per user (wallet layer) | $0 up to 5,000 Vault users, then custom Enterprise pricing | Not published on the page reviewed |
| Per card issued | $0 on the advertised Issuing B2B plan | Not published on the page reviewed |
| Platform plan (issuing-grade) | $5,000/month on Issuing | Not published on the page reviewed |
| Revenue share | Integrating company earns 1% when program cards are used; it is not an added fee | Not published on the page reviewed |
| Optional transaction markup | Additional and separate, per published pricing | Not published on the page reviewed |
| Fee funding mechanism | Prefunded fee balance or saved billing card; small fees may be batched | Not published on the page reviewed |
| Cardholder-facing fee | None published; the card is charged the purchase amount | Not published on the page reviewed |
On the numbers that are published, Privacy.com is not cheaper or more expensive in this table; its rates simply are not published on the pages reviewed, so no cost comparison can be made from this page. Confirm current rates with both vendors before modeling.
Why teams choose Agentcard over Privacy.com
The fee is a known percentage of the order, not a per-card line item
OpenCommerce Standard charges 1% of each completed order, and the integrating company pays it from a prefunded fee balance or a saved billing card, with small fees batched (Agentcard pricing). That makes unit economics a one-line calculation: an agent purchasing $40,000 of supplies in a month costs $400 in commerce fees, derived as $40,000 × 1%. Sandbox purchases are not billed, so you can model the flow before live fees apply.
The cardholder is never billed for the platform
Because Vault pays with the cardholder's own existing card, the card is charged the purchase amount and nothing else. Cardholders keep their existing card's rewards and bank dispute channels, subject to the card program's terms (Vault). For a platform serving end users, that means you do not have to explain a surcharge on a customer's statement, because there is not one.
Consent and fees are decoupled from the agent
Every purchase runs through a consent flow the cardholder controls: the application sends an approval link showing the merchant and amount, the cardholder approves on their own device with a passkey or master password, and cardholders can set merchant and amount caps when saving a card (completing a purchase). A separate, revocable app auto-approval permission can govern a specific app's purchases, and the application must still ask the cardholder before each purchase (app auto-approval). Fees and approvals live in your infrastructure, not in the agent's judgment.
If you are pricing an agent product today, explore Agentcard pricing and run the sandbox flow before any live fee applies.
Best use cases for Agentcard
Agents that buy on behalf of customers using the customers' own cards
Vault stores each customer's existing card once, encrypted on the cardholder's device before storage, and your agent pays with those cards under your brand. Customers keep their rewards and dispute channels, and an existing-card payment through Vault does not use Issuing KYC or require funding an Issuing balance. Pair it with OpenCommerce when the agent also needs to find the item and complete the checkout.
How Privacy.com compares: Privacy.com issues new virtual card numbers rather than using the customer's existing card, so rewards and dispute behavior differ, and its current rates are not published on the pages reviewed.
Procurement and purchasing agents that need the checkout handled
OpenCommerce is one buy tool, available over MCP, covering 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; eligible orders may move 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 (Commerce SDK quickstart). Treat the 5,000+ store count as positioning, not a guarantee for every merchant or checkout.
How Privacy.com compares: Privacy.com supplies a card credential; the checkout itself, from merchant login to order tracking, remains your integration to build.
Company-funded agents with per-task budgets
Issuing creates one-time or multi-use virtual Visa cards funded from company or user wallets, with cards limited to a single purchase, locked to one merchant, or capped at a spend amount. The advertised B2B plan is $5,000/month with $0 per card issued or connected, and your company earns a 1% revenue share when program cards are used. Issuing requires identity verification before the first card, and funds are held as USDC on Base (Issuing).
How Privacy.com compares: Privacy.com also issues virtual numbers, but its published plan structure, per-card fees and funding model for this use case are not available on the pages reviewed.
Platforms that need a white-labeled wallet
Vault is fully white-labeled, with a web script-tag embed, an iOS SwiftUI package, a React Native component, and hosted wallet links for CLIs and backend agents. Free up to 5,000 users means a platform can launch the wallet under its own brand before any wallet-layer cost begins.
How Privacy.com compares: white-label embedding of a cardholder wallet is not a capability published on the Privacy.com pages reviewed.
Best use cases for Privacy.com
Consumer-facing virtual card numbers for human-managed checkouts
Privacy.com's core product issues virtual card numbers that a person creates and manages themselves for online shopping. If your product's flow is a human at a checkout who wants a merchant not to see their real card number, that is the job Privacy.com is built for, and its current pricing is not published on the pages reviewed for this comparison.
Merchant-specific card controls outside an agent loop
Virtual card numbers with per-merchant limits suit spenders who want a card that only works at one store. Agentcard's Issuing covers similar controls for agent-initiated purchases, but if the spender is a human managing cards in a dashboard rather than an agent calling tools, Privacy.com's published workflow may fit better. Its current API and agent support details are not published on the pages reviewed.
Platform overview of Agentcard
Vault: existing-card storage and payment controls
Each cardholder stores their existing card once, encrypted on the cardholder's device before storage and at rest with AES-256-GCM and per-card keys. At checkout, Agentcard swaps the real card in behind a dummy card number, so the agent never handles real credentials. See the Vault quickstart.
Cardholder approval and caps
The standard flow sends an approval link; the cardholder sees the merchant and amount and approves on their own device with a passkey or master password. Cardholders choose merchant and amount caps when saving a card, and purchases outside those rules require approval. Every approval lands in a timestamped log with a trusted agent signature.
OpenCommerce: the buy tool
One buy tool over MCP turns plain-text intent into search, cart, checkout and order tracking across 5,000+ stores. Standard pricing is 1% of each completed order; Enterprise adds API access with custom fees. The OpenCommerce FAQ covers program details.
# Agent calls the buy tool over MCP
buy(intent="order two boxes of diapers from Amazon",
cardholder="ch_abc123")
# -> cart built, cardholder consent requested, order confirmed
MCP-native agent access
Agents connect over MCP with OAuth through Claude Code, Claude Desktop, Cursor, or any MCP-compatible client, with tools for card creation, balances, transactions and the buy tool. Platforms integrate through the REST API with organization-scoped Bearer API keys and webhooks (API reference).
Issuing: newly issued cards
Issuing creates single-use or multi-use virtual Visa cards funded from a per-user wallet in USDC on Base. Cards can be limited to a single purchase, locked to one merchant, or capped at a spend amount, and identity verification is required before the first card (Issuing KYC).
Protection for eligible Vault purchases
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 (Sure announcement). Payment controls limit authorization before a purchase; protection addresses an eligible mistake after one. Review the actual policy before promising coverage.
How to choose: decision matrix
| Your requirement | Choose |
|---|---|
| Agent buys with each customer's own card, rewards preserved | Agentcard Vault + OpenCommerce |
| Agent buys from a company budget with hard per-task caps | Agentcard Issuing + OpenCommerce |
| Agent needs merchant search, cart, checkout and tracking handled | Agentcard OpenCommerce (1% per completed order on Standard) |
| Human-managed virtual card numbers for personal checkouts | Privacy.com (rates not published on the pages reviewed) |
| Wallet free until real scale | Agentcard Vault, free up to 5,000 users |
| Revenue on card use rather than only fees | Agentcard Issuing, 1% revenue share to the integrating company |
| Enterprise API access with custom commercial terms | OpenCommerce Enterprise, contact the team |
Migration guide: switching from Privacy.com to Agentcard
Step 1: Set up the company account. Create an Agentcard organization and get organization-scoped Bearer API keys for REST access, or connect an MCP client over OAuth. The integration guide covers both paths.
Step 2: Decide the wallet model. If your users should pay with their own cards, embed Vault and have each cardholder add their card once. If your company funds purchases, complete Issuing identity verification before the first card and fund per-user wallets in USDC on Base.
Step 3: Swap the card call. Before, a Privacy.com-style flow has your backend create a virtual number and hand it to the checkout code:
# Before: create a virtual card number, pass it to checkout card = privacy_api.create_card(limit=4000, merchant="amazon") checkout.pay(card.number, cart)
After, the agent never holds a card number; Vault swaps the real card in behind a dummy number and consent is enforced by the platform:
# After: request the purchase; consent and payment run in Agentcard
order = agentcard.buy(intent="order supplies from Amazon",
cardholder="ch_abc123")
# approval link sent to cardholder; order confirmed on success
Step 4: Rebuild consent into the flow. Your application must show the cart, obtain the cardholder's yes, then send the payment approval link in the standard flow. Purchases outside cardholder-set caps require approval, and bank challenges may still require cardholder action.
Step 5: Watch for the gaps. There is no direct equivalent for a self-managed personal virtual card dashboard; Agentcard is built for company integrations, not consumer card management. If some users need human-managed numbers, a partial migration where Agentcard handles agent-initiated purchases and the legacy flow handles the rest is a reasonable end state. Also plan for the fee model change: OpenCommerce fees are 1% of each completed order rather than per-card charges, and the exact base for taxes, shipping, tips and refunds is not settled in public wording, so confirm commercial terms.
FAQ
Who pays platform fees when an agent buys on behalf of a user?
The integrating company pays Agentcard platform fees. OpenCommerce Standard charges 1% of each completed order, paid from a prefunded fee balance or saved billing card, and Vault is free up to 5,000 users (Agentcard pricing). The cardholder's card is charged the purchase amount only.
Does the cardholder see an Agentcard fee on their statement?
No published fee is charged to the cardholder. Purchases post to the cardholder's own card, so they keep their card's rewards and disputes go to their own bank, subject to the card program's terms.
How is the 1% OpenCommerce fee calculated?
Published wording says 1% of each completed order. The detailed base for taxes, shipping, tips, refunds or gross versus net amounts is not settled in public materials, so confirm the calculation basis in your commercial terms before modeling.
What does the Issuing plan cost, and is the 1% revenue share a fee?
The advertised B2B plan is $5,000/month with $0 per card issued or connected. The 1% revenue share is money the integrating company earns when program cards are used, not an added fee. Optional transaction markup is additional and separate.
Are there fees during testing?
No. Sandbox purchases are not billed, which lets you model the full consent and checkout flow before live fees apply.
What does Privacy.com charge for the same workflow?
Not published on the pages reviewed for this comparison. Its current per-card and plan pricing for agent-initiated purchases should be confirmed directly with the vendor before comparing unit economics.
If your agents are ready to buy on behalf of real users, get started with Agentcard and run your first sandbox purchase before any live fee applies.
