Your AI agent
can now pay for things
No more burning tokens fighting payment forms. New tools for Claude Code's Chrome integration that spin up a virtual card and fill the entire checkout in one call.
NPM
>npx agent-cards setup-mcp
Claude Code can now make
payments in the browser
🔒acme.dev/checkout/pro
Acme Inc.
Pro Plan
$29 / month
Pro Plan$29.00
Subtotal$29.00
Total due today$29.00
Email
team@company.com
Card information
4242 4242 4242 7291
12 / 27
123
Name on card
AI Agent
Billing address
123 Main St
New York
10001
Subscribe
claude
> Subscribe to Acme Pro for the team
Claude
I'll handle that checkout now.
mcp__agent-cards__pay_checkout run
amount: 29.00
merchant: "acme.dev"
email: "team@company.com"
mcp__agent-cards__pay_checkout result
Payment form filled successfully
Card •••• 7291 ($500 balance)
Form Payment form
Fields email, card, name, address
Done. Review the form and click
Subscribe when you're ready.
claude-sonnet-4-6
Three tools.
One checkout.
detect_checkout
Scans the active tab and detects whether a payment form is present. Returns the fields it found.
pay_checkout
Spins up a virtual card, fills every checkout field, and completes the payment — all in one call.
fill_card
Fills only the card fields with an existing AgentCard. Use when you want to handle the rest yourself.
How it worksFour steps,
Four steps,
fully automatic
01
Opens checkout page
Claude Code navigates to the checkout page in your browser and the extension detects the payment form automatically.
02
Creates a card
The MCP server spins up a virtual debit card with just enough balance for the purchase. If a matching card already exists, it reuses it.
03
Shares it securely
Card details are passed directly to the browser extension. The LLM never sees the card number.
04
Completes checkout
The extension fills every field — card, expiry, CVC, email, name, billing address — and leaves the submit button for you.
No more struggling
with the Chrome tool
The Chrome tool burns tokens clicking around, fails on iframes, and never gets the card in. AgentCard Pay does it in one call.
tmux: checkout-task2 panes
0
> Buy the Pro plan on acme.dev
Claude
I'll navigate to the checkout page.
mcp__chrome__navigate run
url: "acme.dev/pricing"
mcp__chrome__navigate ok
mcp__chrome__click run
selector: "button.upgrade-pro"
mcp__chrome__click ok
Now I'll fill the card number field.
mcp__chrome__fill run
selector: "input[name='cardNumber']"
mcp__chrome__fill error
Element not found. The card input is
inside a cross-origin iframe.
Let me try accessing the iframe directly.
mcp__chrome__execute_js run
"document.querySelector('iframe')
.contentDocument.querySelector('input')"
mcp__chrome__execute_js error
DOMException: Blocked a frame with origin
"acme.dev" from accessing a cross-origin frame.
mcp__chrome__fill run
selector: "div[class*='CardField'] input"
mcp__chrome__fill error
Element not interactable
I'm unable to fill the payment form. The card
fields are in a sandboxed iframe that I can't
access. You'll need to enter the card manually.
chrome tool ── 8 tool calls, failed
1
> Buy the Pro plan on acme.dev
Claude
I'll handle that checkout now.
mcp__agent-cards__pay_checkout run
amount: 29.00
merchant: "acme.dev"
email: "team@company.com"
mcp__agent-cards__pay_checkout result
Payment form filled successfully
Card •••• 7291 ($500 balance)
Form Payment form detected
Fields card, email, name, address
Done. Review the form and click
Subscribe when ready.
agentcard pay ── 1 tool call, done
[checkout-task] 0:chrome* 1:agentcard-"user@dev" 14:32 13-Mar-26
The card infrastructure
behind the checkout
Speed
Instant issuance
Card is ready within seconds. No waiting, no manual approval, no delays.
Security
Single-use by default
Each card is locked to the amount you load. Limit exposure per agent, per task, per spend.
Coverage
Works everywhere
Accepted anywhere Mastercard works online. If a site takes Mastercard, your agent can pay.
Control
Human in the loop
You authorize every card creation and every payment before it happens. Agents propose, you approve.
Integration
Built for agents
Expose cards to any MCP-compatible AI with one config block. Claude, Cursor, and any MCP runtime.
Privacy
LLM never sees the card
Card details go directly to the browser extension. The AI model only gets a confirmation — never the number.