Let agents buy
anything online
Powering payments for agentic startups
Consumer apps, B2B companies and crypto teams run their agents’ purchases on Agentcard.
Consumer apps like Orchid buy on Amazon for customers using Agentcard:
Orchid uses Agentcard to store customers’ cards safely and buy things on their behalf.”
OrchidConsumer B2B companies like Almanac use Agentcard to give cards to company agents:
Almanac stores corporate cards using Agentcard and automates company purchases with their Slack agent.”
AlmanacB2B Crypto companies like Laso use Agentcard as their payment infrastructure:
When users have funds in crypto and their agent wants to make purchases using them, they can use Laso (powered by Agentcard) and create cards their agent can use.”
Laso FinanceCrypto
Explore our products
Vault, Issuing and the Purchase Agent: one for each way an agent spends.
… clicks made
Purchase Agent
Integrate our agent into yours and enable purchases from Amazon, DoorDash and many other online stores.
Read the docs
Integrates natively with the tools you use
Kernel, Browserbase, your own browser, Linq and Blooio: the stack your agent already runs on.
Browser integrations
Integrate with Kernel, Browserbase or your own browser and automate purchases online.
// One card item per purchase, in the // user's KERNEL vault await kernel.vaults.items.upsert('order', { type: 'card', spec: { provider: 'agentcard', merchant: 'amazon.com', amount: 2306, currency: 'usd' }, }); const browser = await kernel.browsers.create({ vaults: [{ id: vault.id }], });Messaging integrations
iMessage agents built on top of Linq and Blooio can use Agentcard to complete payments.
POST api.linqapp.com/…/v3/payments { "handle": "+15551234567", "amount": 2306, "currency": "usd", "merchant": "amazon.com" } // Linq sends the approval as a native // bubble, then hands your agent the card.
Working with Agentcard
Personal assistant companies use Agentcard as their payment infrastructure.
- Orchid
- Pally
- Almanac
- Endstack
- Pickle
- Persona
- Ego
- Orgo
- Laso Finance
- Bezalel
- Runable
- Paper Instruments
Frequently asked questions
Everything you need to know about Agentcard.
What does Agentcard do?
It lets AI agents pay at real checkouts. Three products: Vault (the user's own card, stored securely and used by the agent with their approval), Issuing (new virtual cards per user or per agent) and the Purchase API (one /buy endpoint with native merchant integrations).
Vault or Issuing: which should we start with?
Start with Vault. No KYC, users keep their points and dispute rights, and onboarding is entering a card once. Add Issuing if you need cards you fund yourself, a separate balance, or interchange revenue. Both can run side by side.
Is Agentcard B2B or for consumers?
B2B. We sell to companies building agents.
Does the merchant need to integrate anything?
No. It works on any checkout that takes cards. For hard checkouts we cover the big payment processors (Stripe, Shopify, Adyen, Checkout.com, Braintree, Worldpay and more, 23 mapped) plus native integrations for Amazon, DoorDash, eBay, Best Buy and airlines.
How is this different from Stripe Link?
Link issues a one-time card, so users lose points, disputes route through Stripe, recurring payments break, and users often need a separate app. Vault uses the real card, and we also complete the checkout (Purchase API, processor integrations), which Link doesn't.
How does the Purchase API work, and how reliable is it?
The agent sends a natural-language purchase to /buy; we route it to the right merchant. Purchases complete in under 2 seconds with a 99% success rate (target 99.9%), handling CAPTCHAs, OTPs and refunds. Merchants are mostly US today; we add regional stores (for example Alibaba) on request.
Do you support x402, AP2 or other agent payment protocols?
Not yet.
How does a purchase work end to end?
The user saves their card once in Agentcard's hosted form. The agent fills the cart, enters a dummy card and clicks Pay. Agentcard intercepts the checkout request, the user gets a push or iMessage approval and approves with Face ID (a passkey), and Agentcard sends the real card to the merchant with a trusted-agent signature. The approval is logged with a timestamp as evidence if the merchant ever faces a dispute, and the final request goes out from the user's device, which cuts bot-detection failures compared with server VMs.
How is the card secured? Can Agentcard see it?
No. The card is encrypted with a passkey that lives on the user's phone, similar to 1Password. Only the user can decrypt it (Face ID). Neither the agent, the integrator nor Agentcard ever sees the raw number, even if our database leaked.
Do users keep their points, and how do disputes work?
Yes. It's their real card on the card network, so rewards accrue, the statement shows the actual merchant, and disputes go straight to their bank.
Does the user have to approve every purchase?
By default, yes, but we also support auto-approvals. Users can opt in to auto-approval when they save the card and choose a per-amount threshold (for example, auto-approve under $50).
Which cards and countries work?
Any card: credit, debit, prepaid, commercial or consumer; Visa, Mastercard or Amex; from any country. No purchase limits, and cards transact in the merchant's currency.
Is Vault free?
Yes, up to 5,000 users.
Why store real cards instead of issuing one-time cards or using Visa Intelligent Commerce?
We tried both. One-time cards needed KYC for everyday purchases, and users refused it. Network tokenization (Visa Intelligent Commerce, Click to Pay) only worked for about 8% of cards: no Chase, prepaid, commercial BINs (Brex, Ramp) or non-US cards. Vault works with any card.
Can approval happen natively in our app?
Today it runs in an iframe or web view inside your app, no redirect.
Which checkouts does it work on?
23 payment processors mapped (Stripe, Adyen, Shopify, Checkout.com, Braintree, Worldpay and more) plus Amazon.
Does 3DS still apply?
Yes, when the user's bank requires it. Not for every transaction.
Can we white-label the Vault?
Yes. Logo, colors and typography are set in the dashboard, and the form can run on your domain.
Is there a card router?
Yes: it picks the user's best card per merchant for rewards.
Can users scan a card with the camera?
Yes.
Who issues the cards?
Rain, settled in USDC on Base.
Debit or credit? Single-use or multi-use?
Visa cards on a credit BIN (better acceptance than prepaid) that behave like debit against a funded balance. Both one-time cards (created per transaction, closed after use) and permanent multi-use cards are supported. Multi-use fixes merchants like Uber and DoorDash that close one-time cards with a $1 validation hold.
Can we control what an agent spends?
Yes, per card: hard spend limits, transaction-count limits, and merchant or merchant-category (MCC) restrictions enforced at the Visa network level.
How are cards funded?
Each user has a wallet. Fund it with USDC on Base (from their own wallet or yours), or Apple Pay / Google Pay.
Where can cards be issued?
Globally, except sanctioned countries.
What does Issuing cost?
$5,000/month standard.
Physical cards, Apple Pay, Google Pay?
No physical cards. Cards can be added to Apple Pay and Google Pay.
Can the cards be white-labeled?
No. Cards carry the Agentcard brand, visible in KYC and the terms.
Can one card be shared by a group, or issued to an LLC?
Yes.
Can we fund all our users from one company account?
Yes, with the company wallet: prefund it (USDC works), and funds move to the user's wallet just before a card is created, about 30 seconds end to end.
ACH, wire or bank transfer?
Not yet. Users can fund their wallets only with Apple Pay, Google Pay, a card or crypto today.
Can the card draw just-in-time from a stablecoin balance at authorization?
No. Funds must be in the card wallet first; we don't do network-level just-in-time authorization.
Who handles disputes and chargebacks?
Agentcard, through the issuer, with a dashboard to track them. For now we cover disputes ourselves while the long-term model is settled.
