Stats

We may earn commissions from some links.We may earn commissions from links to support our work. Learn more.
Get more AI tool alerts:
About Agentcard
An assistant that finds the right product but hands checkout back to the customer has only finished part of the job. I recommend Agentcard for companies building shopping or personal-assistant agents that need to take that next step. Its strongest starting point is Vault: customers pay with their existing card, keep its usual rewards and approve the payment on their own device in the default flow.
Agentcard also has Issuing for separately funded agent cards and a Purchase Agent for handling shopping execution. That makes it a broader option than a card API alone. Stripe Issuing is the alternative for building your own controlled card program; Link for agents suits assistants that should request customer-approved payments through a Link wallet.
Explore Agentcard for your agent.
What is Agentcard?
Agentcard is payment infrastructure for companies building AI agents. It separates using a customer's existing card, creating a new card and completing a purchase into different products, which can work alongside each other.
Vault stores the customer's own card for agent-assisted checkout. Issuing creates virtual cards backed by a funded balance.
Purchase Agent, delivered through the Commerce SDK and other interfaces, handles finding products, building carts and placing covered orders. Voice is an early-access approval option.
The distinction matters before you compare prices. You don't need a new card program just because your assistant needs to buy something, and adding payment credentials doesn't by itself give an agent a working shopping workflow.
Who is Agentcard for?
Consumer-assistant teams have the clearest reason to consider Vault. A customer could ask an assistant to find household supplies, review the proposed cart and approve payment with the card they already use. Keeping that card's rewards and familiar bank-dispute route makes the buying experience easier to explain.
Issuing fits platforms that need a separate balance or a card budget for each agent or task. Company-funded purchasing is a different job from asking a customer to pay with their own card, and Agentcard supports both models.
For teams already building browser automation, our Browser Use overview covers the browser side of that workflow. Agentcard supplies a payment layer rather than replacing all the agent's browsing logic. Purchase Agent is the more relevant product if you want Agentcard to handle the covered shopping flow instead.
This is infrastructure to integrate into a product, not simply a consumer shopping chatbot subscription. A small team that only needs an occasional company card should weigh Issuing's monthly commitment carefully.
Agentcard pros and cons
The own-card path is Agentcard's most compelling differentiator. Its tradeoffs become more substantial when you move into running a funded card program or need broad international shopping coverage.
Agentcard features
Vault payments
In the ordinary Vault flow, the customer saves a real card through a hosted page with a passkey. The agent submits placeholder card details at checkout, and the SDK pauses a recognized payment-processor request. The customer sees the merchant and amount, approves on their device, and that device sends the real card to the processor.
Agentcard describes this architecture as keeping the raw card number out of both the agent and Agentcard's view in that user-approved flow. That is a useful design distinction from handing an agent reusable card credentials, rather than a promise that every payment mode has identical behavior.
Because the underlying card pays the merchant, customers retain its usual rewards and dispute charges through their bank. Vault also supports your branding and a custom domain, although the Agentcard footer remains.
Approval options
Individual payment approval is the default. Customers can also set autopilot rules with an amount threshold, total budget and expiry, which is useful for repeat purchases they are comfortable delegating.
App auto-approval is a separate permission. It can have no spending limit or end date, remains revocable, and takes precedence over the shopper's separate rules for that app. The integrating app must ask before each purchase; Agentcard does not verify that it did.
These modes have processor and transaction requirements. Commerce SDK auto-approval needs a processor-fixed amount and a checkout matching the confirmed store; tokenization flows such as Shopify still require an approval link. Choose the approval model deliberately rather than treating every automatic payment as a small, capped purchase.
Issuing and spending controls
Issuing creates single-use or multi-use virtual cards after identity verification and funding. KYC involves a government ID, face scan and any additional required details. Cards support spend limits, transaction-count limits and merchant or merchant-category restrictions.
Single-use cards close after the first approved charge. Multi-use cards remain available until their limit is spent or they are closed, making them the relevant option for subscriptions or merchants that charge repeatedly. A validation hold can matter when choosing the card type.
Unlike Vault's default flow, Issuing intentionally gives the authorized agent the card number, expiry and security code for checkout. Optional approval before revealing credentials adds another control, but it doesn't turn Issuing into the same architecture as Vault.
The cards spend against a prefunded balance held in USDC on Base, with company-funded and user-funded options. Agentcard does not currently support ACH, wire or bank-transfer funding, or network-level just-in-time funding at authorization.
International eligibility is a material constraint. Rain's cardholder policy excludes residents or registered cardholders in 17 countries, including India and mainland China, and Agentcard's terms currently limit wallet funding to the US. This is not a globally available funding program.
Purchase Agent
Purchase Agent handles more of the task than supplying a payment method. Its Commerce SDK gives your agent a buy tool for supported online shopping, food delivery, restaurant reservations and flights. Your app can receive order and delivery updates for the shopper's conversation.
The normal workflow separates saying yes to the cart from approving payment. When a store's final checkout price can vary, the approval ceiling may exceed the displayed cart total; the customer needs to see both. Changed carts return for confirmation.
Coverage is store-specific and currently mostly US-focused. The merchant lookup identifies supported, unsupported and unknown stores. Payment approval and order confirmation are separate steps; an order can remain pending or fail after approval.
Browser integration and Voice
The direct checkout SDK attaches to Playwright Chromium browsers, including CDP-connected sessions. It needs to attach before checkout requests happen, with active service workers blocked. Your integration still has to read the merchant's order result; payment approval alone isn't order confirmation.
Vault's hosted pages need a supported browser and refuse framing. Plan around the documented browser flow rather than assuming you can embed an approval form in any app view.
Voice adds spoken purchase approval in early access, with assisted integration. Agentcard describes a passphrase whose final word changes for each purchase, English and Spanish support, and passkey or Face ID fallback. It has no published numeric price, so I wouldn't make it a requirement for an initial deployment.
See Agentcard's payment options.
Agentcard vs alternatives
Agentcard vs Stripe Issuing
Stripe Issuing is the closer comparison for new agent cards. It supports browser checkout using virtual-card credentials and Shared Payment Tokens for supported programmatic flows. You build the real-time authorization logic and can apply spending and merchant-category controls.
US virtual-card creation costs $0.10 per card, not $0.10 for the whole payment program. Stripe's US pricing also lists cross-border charges of 1% plus 30 cents, with another 1% when currency conversion is required. Own-business production access requires eligibility review; platform programs go through Stripe directly.
I recommend Stripe for teams that want to build around those card and authorization primitives. Agentcard is more compelling when you need Vault's existing-card path or want covered shopping execution through Purchase Agent, rather than owning that entire workflow yourself.
Agentcard vs Link for agents
Link for agents gives assistants access to a customer-controlled wallet. The agent requests approval for a purchase, then receives a scoped virtual card or a supported payment token rather than the customer's underlying card details. Payment access supports US and Canadian Link accounts; its financial-insights feature is US-only.
Link also supports recurring virtual cards for eligible customers. For eligible US customers, a funded Link balance can support purchases below a customer-set per-purchase approval threshold. Those options make it a useful comparison for delegated spending, not just one-off card generation.
The choice is how much of the shopping workflow you want supplied. Link handles authorization and payment credentials while your agent works through the seller's flow; Agentcard's Purchase Agent handles covered product searches, carts and orders. Vault is also appealing when keeping the customer's existing card and rewards is central to the experience, since some Link agent-payment flows use a separate payment method and do not retain those benefits.
Current Link Agent Wallet Preview terms have no additional wallet-service cost to the integrating business, while other Stripe-service fees still apply. That is different from Stripe Issuing's per-card price. Choose Link when a customer-controlled wallet fits the assistant you're building; choose Agentcard when its own-card flow or covered shopping execution is the stronger requirement.
Agentcard pricing
Purchase Agent is free to use, with a 1% fee on live purchases. Vault and Issuing have separate pricing for existing-card payments and funded virtual cards.
Issuing pays the integrating business a 1% revenue share and supports optional transaction markup. This is separate from the 1% fee charged on Purchase Agent live purchases. Card-program charges can apply beyond the subscription and card-creation price.
Vault is the sensible starting point when customers already have the cards they want to use. Issuing's monthly fee needs a business case around funded agent spending and card-program economics. Our payment-processing category is useful for exploring adjacent payment tools, but compare the payment model before the headline rate.
Verdict
I recommend Agentcard for assistant builders who want customers to pay with their existing cards and keep a recognizable approval flow. Vault is the strongest entry point, while Purchase Agent is useful when you also need covered carts and orders handled for you. Add Issuing when separate balances and controlled agent cards justify its cost and eligibility requirements.
Choose Stripe Issuing for a card program built around your own authorization and transaction logic. Choose Link for agents when your assistant should request payments through a customer-controlled Link wallet. For Agentcard, the deciding factors are the payment model you need and whether its actual merchant and funding coverage fits your customers.
Explore Agentcard for your payment workflow.
FAQ
Is Agentcard free?
Yes. Purchase Agent is free to use, with a 1% fee on live purchases. Vault is free up to 5,000 users. Standard Issuing is a separate product at $5,000/month.
Do customers need KYC?
Issuing requires identity verification before creating real funded cards. Paying with an existing card through Vault does not require Issuing KYC.
Does every purchase need approval?
Individual approval is the default, but supported purchases can use customer-set autopilot rules or a separate app auto-approval permission. App permission can be unbounded, and some processor flows still require an approval link.
Can Agentcard pay at any checkout?
No. Vault depends on the payment processor, merchant flow, browser and any bank approval steps. Purchase Agent supports specific merchants and is currently mostly US-focused.
Can Issuing use bank-transfer funding?
Not currently. Agentcard lists wallet funding through crypto, Apple Pay, Google Pay or a card, subject to eligibility. Funds must already be in the card wallet before authorization.