Agentcard vs. Privacy.com (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.
Agentcard vs. Privacy.com (2026)
Agentcard Vault lets an AI agent pay with the cardholder's existing credit or debit card, while Privacy.com issues new virtual card numbers funded from a separate source.
Introduction and methodology note
Both products sit between an AI agent and a card network. Agentcard is payment infrastructure for companies building AI products: its Vault product stores a customer's existing card with on-device encryption and lets the company's application request cardholder-approved payments against it. Privacy.com is a virtual card number (VCN) program: it issues new Mastercard or Visa card numbers that draw on a linked funding source, and the agent pays with the new number rather than the underlying card.
The divergence is the funding and credential model. With Vault, the customer keeps their existing card, its rewards, and its bank dispute channels, subject to the card program's terms. With a VCN program, every purchase runs on a newly issued card number, so the company or cardholder manages a separate card lifecycle and funding flow on top of the real card.
Methodology note: Agentcard figures on this page come from Agentcard's own published pages, linked inline. Privacy.com figures are stated in plain text from its published materials, without links. Claims were last verified on 2026-11-14. Security and coverage claims are self-reported by each vendor; test both products against your own merchants, cards, and workload before committing.
TL;DR
- If the requirement is "the agent pays with the customer's actual credit card," Agentcard Vault is built for that: existing-card storage, cardholder approval, and no separate card to fund. Privacy.com issues new virtual card numbers instead.
- Vault is free for companies up to 5,000 users, with custom Enterprise pricing; Privacy.com's published plan rates were not re-verified for this page.
- Agentcard also covers adjacent needs: Issuing for newly issued cards when you do want one, and OpenCommerce for search, cart, checkout, and order tracking across 5,000+ stores.
Quick-comparison table
| Dimension | Agentcard Vault | Privacy.com |
|---|---|---|
| Card used at checkout | The cardholder's existing credit, debit, commercial, or prepaid card | A newly issued virtual card number |
| Funding model | None; charges post to the existing card | Funded from a linked funding source managed in the VCN program |
| Cardholder rewards | Remain on the existing card, subject to card terms | Earned per the VCN program's terms, not the underlying card's |
| Dispute channel | The issuing bank's, subject to card terms | The VCN program's dispute process |
| Approval flow | Cardholder approves on their own device with a passkey or master password; optional merchant and amount caps chosen at card save | Program-level spend controls configured on each virtual card |
| Credential exposure to the model | Card credentials are encrypted on the cardholder's device before storage; the model never sees raw numbers | Agent handles a virtual card number, not the underlying card |
| Pricing | Free up to 5,000 users; Vault Enterprise custom pricing | Not re-verified for this page |
| Verification date | 2026-11-14 | 2026-11-14 |
Granular differentiator table
The real differentiator is what the agent actually holds. This table breaks the card lifecycle down.
| Lifecycle stage | Agentcard Vault | Privacy.com |
|---|---|---|
| Card onboarding | Cardholder saves an existing card; credentials are encrypted on the cardholder's device before storage | Cardholder links a funding source; program issues new virtual card numbers |
| What the agent sees | An approval request with merchant and amount; not raw card data | A spendable virtual card number and its controls |
| Per-purchase consent | Standard flow sends an approval link; the cardholder sees merchant and amount and approves or declines | Spend limits are set on the card; per-purchase consent depends on the program's controls |
| Spend ceiling | Cardholder-selected merchant and amount caps at card save, plus a separate revocable app auto-approval permission | Per-card limits configured in the program |
| Rewards | Existing card's rewards, subject to card terms | Per the VCN program's terms |
| Chargebacks | Bank dispute channels of the existing card, subject to card terms | The VCN program's dispute process |
| New card issuance | Not part of Vault; Agentcard Issuing is a separate product for one-time or multi-use cards | Core capability |
On price, Privacy.com may be cheaper for small consumer-scale usage; its current published rates were not re-verified for this page, so compare directly before deciding. Vault's free tier runs to 5,000 users per the Agentcard pricing page.
Why teams choose Agentcard over Privacy.com
The agent spends the customer's real card
Vault is existing-card infrastructure: the customer's actual credit or debit card is the payment instrument, so rewards, purchase protection, and bank dispute channels stay with the card the customer already has, subject to the card program's terms. A VCN program inserts a new card number between the agent and the merchant, which means a second card lifecycle to manage and a rewards and dispute relationship routed through the VCN program instead of the issuing bank.
Credentials stay out of the model
With a VCN, the agent's context contains a live, spendable card number. That is a lower-risk number than the underlying card, but it is still a credential in model context, a pattern the OWASP LLM Top 10 flags as excessive agency. Vault inverts this: card credentials are encrypted on the cardholder's device before storage, and the agent's payment action becomes an approval request rather than a card number. The Vault docs describe the storage and purchase flow.
Consent is a product feature, not a bolt-on
Vault ships three distinct consent modes: the standard approval link where the cardholder sees merchant and amount and approves with a passkey or master password; customer-selected merchant and amount caps chosen when saving a card; and a separate, revocable app auto-approval permission documented in the app auto-approval guide. VCN programs expose per-card spend limits, but per-purchase cardholder consent over an existing card is not their design center.
If your roadmap includes agent-initiated purchases against customer cards, review the Vault integration docs to see how the approval flow maps to your application.
Best use cases for Agentcard
Agents that purchase on behalf of a user
Personal-shopping, booking, and replenishment agents charge the user's real card. Vault keeps the cardholder in control: the application shows the cart or merchant and amount, the cardholder approves on their own device, and the purchase posts to the existing card. Eligible Vault purchases also carry announced protection via Agentcard's partnership with Sure, with a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms per Sure's announcement.
How Privacy.com compares: the agent spends a program-issued virtual number, which works but routes rewards and disputes away from the user's own card.
B2B platforms embedding payments under their own brand
Vault supports white-label embedding, so a company can offer existing-card storage and payments inside its product under its own brand, free up to 5,000 users. The cardholder's consent flows and controls are part of the integration rather than a redirect to a third-party card dashboard.
How Privacy.com compares: its program is oriented around issuing and managing virtual cards, not white-labeling existing-card storage inside another product.
Teams that need purchase orchestration too
Agentcard's OpenCommerce adds catalogue search, cart building, checkout, and order tracking across 5,000+ stores behind one buy tool, with Standard pricing at 1% of each completed order. A purchasing agent gets the full buy flow, with Vault as the shopper payment method in the documented integration.
How Privacy.com compares: it supplies the card, not the commerce layer; you build merchant integrations and order tracking yourself.
Companies that also want to issue cards
When a workflow genuinely calls for a new card, such as an employee-scoped spend card, Agentcard Issuing creates one-time or multi-use cards. The advertised B2B plan is $5,000/month with $0 per card issued or connected, and the integrating company earns a 1% revenue share on card use; current Issuing requires identity verification before the first card, per the Issuing docs.
How Privacy.com compares: issuing virtual cards is its core product, and it may fit lightweight consumer-scale issuing without an enterprise plan.
Best use cases for Privacy.com
Consumer-scale virtual cards for personal agents
If an individual wants disposable, merchant-locked card numbers for their own agent subscriptions and trials, Privacy.com's model is a direct fit: issue a number, cap it, delete it when done. Vault assumes a company integrating payments for its users, not a single person managing personal cards.
Programs where a separate card number is the requirement
Some workflows specifically need a number that is not the user's real card, for example isolating recurring merchant charges or avoiding sharing the underlying card with a new merchant. A VCN program is purpose-built for that isolation, and Vault deliberately does not insert a new number between the card and the merchant.
Platform overview of Agentcard
Vault: existing-card storage and payments
Vault stores customers' existing consumer, commercial, or prepaid cards with encryption performed on the cardholder's device before storage, and exposes payment controls and approval flows to the integrating application. Acceptance depends on the actual card, merchant, processor, and geography; check the Vault product page and current docs for your specific flow.
Cardholder approval modes
The standard flow sends an approval link; the cardholder sees the merchant and amount and approves with a passkey or master password. Approval alone is not a completed purchase: the application confirms the merchant's order result. The purchase guide walks through the sequence, illustrated here in simplified form:
{
"merchant": "acme-travel.example",
"amount": 41250,
"currency": "USD",
"cardholder_action": "approval_link_sent"
}
Customer-selected rules and app permissions
Cardholders can choose merchant and amount caps when saving a card; purchases outside those rules require approval. Separately, a cardholder can grant a revocable, card-specific app auto-approval permission, which the docs describe as having no spending limit or end date; the application must still ask the cardholder before each purchase.
Issuing: newly issued cards
For workflows that need new cards, Issuing creates one-time or multi-use cards, with company-funded and user-funded options and published pricing describing funds held as USDC on Base. Identity verification is required before the first card, per the KYC guide.
OpenCommerce: purchase orchestration
OpenCommerce is one buy tool covering search, cart building, checkout, and order tracking across 5,000+ stores, available over MCP, with Standard pricing at 1% of each completed order and Enterprise adding API access with custom fees. See the OpenCommerce FAQ for the current integration behavior.
Pricing and protection
Vault is free up to 5,000 users with custom Enterprise pricing per the pricing page. Agentcard and Sure announced protection for eligible Vault purchases: a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms. Controls limit authorization; protection addresses an eligible mistake after purchase.
How to choose decision matrix
| If you need... | Choose |
|---|---|
| The agent to pay with the customer's existing credit card | Agentcard Vault |
| Disposable virtual numbers for a personal agent | Privacy.com |
| Cardholder approval per purchase, with merchant and amount caps | Agentcard Vault |
| A new card number that hides the underlying card from merchants | Privacy.com, or Agentcard Issuing for programmatic issuance |
| White-label payments inside your product, free up to 5,000 users | Agentcard Vault |
| Search, cart, checkout, and order tracking across 5,000+ stores | Agentcard OpenCommerce |
| Rewards and disputes to stay with the customer's own bank | Agentcard Vault |
| Program-issued card controls as the primary spend governance | Privacy.com |
Migration guide
Switching from Privacy.com to Agentcard
Migrating means changing the payment instrument from a program-issued virtual number to the cardholder's existing card, so the work is mostly in the consent and confirmation flow rather than card management.
- Set up the company account and complete any verification your integration requires; Vault's existing-card flow does not use Issuing KYC, though Issuing does.
- Replace card-issuance calls with card-save calls. Where you previously created a virtual card per merchant or task, the cardholder now saves an existing card once, with credentials encrypted on their device.
- Replace spend-limit configuration with consent modes: standard approval links, customer-selected merchant and amount caps, or a revocable app auto-approval permission where appropriate.
- Handle the purchase result. Approval is not completion; confirm the merchant's order result after the cardholder approves.
Conceptually, the before and after look like this (illustrative, not exact SDK syntax):
Before (VCN model): card = issue_virtual_card(funding_source, limit=5000) pay(card_number, merchant, amount) After (Vault model): card = save_existing_card(cardholder) # on-device encryption result = request_approval(card, merchant, amount) if result.approved: confirm_order(merchant)
What has no equivalent: Privacy.com's per-merchant disposable numbers do not map to Vault, because Vault pays with the real card. If some workflows genuinely need isolated numbers, a partial migration is a reasonable end state: Vault for existing-card purchases, Agentcard Issuing for the flows that need new cards.
FAQ
Does the agent ever see the actual credit card number?
No. Vault encrypts card credentials on the cardholder's device before storage, and the agent's payment action is an approval request with merchant and amount, not a card number. Exact credential handling for your integration is defined in the Vault docs.
Do customers keep their credit card rewards?
Yes, rewards stay on the existing card, subject to the card program's terms, and disputes go through the issuing bank's channels. With a VCN program, rewards and disputes route through the virtual card program instead.
What does Agentcard cost?
Vault is free up to 5,000 users, with Vault Enterprise at custom pricing per the Agentcard pricing page. Issuing's advertised B2B plan is $5,000/month with $0 per card issued or connected, and OpenCommerce Standard charges 1% of each completed order.
Is every purchase blocked until the cardholder approves?
No. The standard flow sends an approval link per purchase, but a cardholder-selected rule or a granted app permission can let eligible purchases proceed without a second link, with conditions such as a processor-fixed amount and matching checkout origin. Bank challenges can still require cardholder action.
What if the agent buys the wrong thing?
Agentcard and Sure announced protection for eligible Vault purchases: a maximum refund of $250 per purchase and $1,000 annually, subject to eligibility and terms per Sure's announcement. Spending controls limit authorization before purchase; protection addresses an eligible mistake after.
Can we still issue new cards where a virtual number is the right tool?
Yes. Agentcard Issuing creates one-time or multi-use cards as a separate product, with identity verification required before the first card. Many integrations use Vault for existing-card purchases and Issuing only where a new card is genuinely required.
Agentcard Vault is the shortest path to letting your agents pay with the cards your customers already have. Talk to the Agentcard team about your integration, or start with the Vault docs and a sandbox flow.
