AI agents · MCP server

Your AI Agent Can Finally Pay for Things

Connect Claude, Cursor or any MCP-compatible agent directly to your WaldenPay cards. It fetches card details at checkout, receives the 3DS verification code itself, enters it, and confirms the charge landed — the full payment loop, with no human copy-pasting numbers or codes.

3DS/OTP
codes go to the agent
<1 min
to connect a client
Free
MCP access, standard card fees
The missing step

Agents can shop. They just can't pay.

AI agents already browse, compare and fill checkout forms — then stall at the payment step. Three things stand in the way, and this feature removes all three.

Agents have no card of their own

Dedicated agent-enabled virtual cards, created and funded from your crypto wallet — the agent can even issue its own card with the exact budget for a task.

You don't want your personal card in an agent's context

Programmatic access to card credentials, scoped to cards you've explicitly enabled, with a notification to you on every read.

3DS codes go to a phone the agent can't see

The key differentiator: the agent receives the 3DS/OTP verification code itself through a dedicated waiting tool, and enters it to complete the purchase.

How it works

Connected in under a minute

01

Generate a key

On the AI Agents page in your dashboard, generate a personal MCP key. It's shown once — only a hash is stored — and can be revoked at any moment.

02

Paste one config block

The dashboard produces a ready-to-paste snippet for Claude Desktop or Cursor: a URL plus your key as an auth header. Connected in under a minute.

03

Choose what it can touch

Each card has an Agent access toggle. The agent only sees cards you switch on. Cards it creates for itself are agent-enabled automatically.

04

Set the budget

A daily spend cap — default $500, yours to adjust — limits how much the agent can move from the wallet onto cards in any rolling 24 hours.

05

Let it work

It lists its cards, quotes exact fees before spending, pays at checkout, waits for and enters the 3DS code, then confirms the charge in the transaction history.

Claude Desktop / Cursor configgenerated for you in the dashboard
{
  "mcpServers": {
    "waldenpay": {
      "url": "https://… copied from your dashboard …",
      "headers": {
        "Authorization": "Bearer wp_••••••••••••"
      }
    }
  }
}

No SDKs, no OAuth dance — a URL and your key as a Bearer header.

Capabilities

What the agent can do

Everything needed to complete a purchase end-to-end — and nothing beyond it.

Read
  • List its agent-enabled cards with balances and statuses
  • Get full card credentials for checkout — you're notified every time
  • Wait for a 3DS/OTP code and receive it the moment it arrives
  • Read recent transactions to verify a charge went through
  • Check the wallet balance and its remaining daily budget
  • Quote the exact all-in cost of an operation before spending
Act
  • Create a new virtual card funded from the wallet
  • Top up a card from the wallet balance
  • Freeze and unfreeze cards
Explicitly impossible
  • Withdraw money anywhere
  • Move card balances back to the wallet
  • Make or receive deposits
  • Touch account settings
  • See cards you haven't enabled

Money only ever flows one way — from your wallet onto cards. That's not a limitation to work around; it's the design.

Safety model

Spend limits you control

Your cards, your toggles, your cap, your kill switch — and every action logged.

Opt-in per card

The agent only sees cards you've switched on. Exposure per purchase is naturally capped by that card's balance — the recommended pattern is a dedicated agent card with a small balance.

Daily spend cap

A hard server-side limit on agent-initiated funding in any rolling 24-hour window. Default $500; raise or lower it whenever you like.

You always know

In-app, email or Telegram notification whenever the agent reads card credentials or moves money. Nothing happens silently.

Full audit trail

Every single agent action lands in an activity feed on the AI Agents page — what it read, what it moved, and when.

Instant kill switch

Revoke the key and access ends immediately. Cards, balances and settings stay exactly as they were.

The caps are the feature

An agent that can spend without limits is a liability. One that works inside a budget you set — and proves every action in an audit trail — is a tool you can actually leave running.

In practice

What people run on it

“Book me the cheapest flight to Berlin next weekend”

The agent finds the flight, creates a card with the exact budget, pays at checkout, handles the 3DS prompt, and confirms the charge landed — all before reporting back.

One card for all your subscriptions

The agent keeps your SaaS and AI tools on a dedicated card, tops it up before renewals, and freezes it between billing cycles so nothing else can charge it.

Ad accounts that never run dry

An ad-ops agent tops up the advertising card when a campaign budget runs low — instantly, and never beyond the daily cap you set.

Research that pays for itself

A research agent buys datasets, reports or one-off tools without waking you up. You just see the notification and the line in the audit trail.

Under the hood

Built on the same cards you already use

CardsVirtual Visa/Mastercard — any name and billing address works at checkout
FundingWallet topped up with crypto: 135+ cryptocurrencies across 35+ networks, credited in USD
Card typesSubscriptions & Advertising (recurring) and Apple Pay & Google Pay (one-time purchases)
ProtocolStandard MCP over Streamable HTTP — works with any MCP client
AuthBearer key, shown once, revocable instantly
Rate limit60 requests per minute
PricingMCP is free — $10 one-time card issuance, standard top-up fee with volume discounts, no monthly fees

Standard card pricing is the same as everywhere else on the platform — see pricing for the full fee schedule.

MCP & AI agent FAQ

What is MCP and what do I need to use this?

MCP (Model Context Protocol) is the open standard AI agents use to talk to external tools. WaldenPay hosts an MCP server, so any MCP-compatible client works: Claude Desktop, Cursor, or a custom agent you build yourself. Setup is a personal key generated in the dashboard plus one config block pasted into your client — no SDKs and no OAuth flow.

How does the agent get past 3D Secure?

Through a dedicated waiting tool. When a merchant triggers 3DS at checkout, the agent calls the tool, receives the one-time verification code the moment it arrives, and enters it to finish the payment. Codes are single-use, and you are notified every time card credentials are read. Getting the verification code to the agent is the step every other agent setup fails at.

What can the agent never do?

It cannot withdraw money anywhere, cannot move card balances back to the wallet, cannot make or receive deposits, cannot touch account settings, and cannot even see cards you haven't enabled for agent access. Money only ever flows one way — from your wallet onto cards — and only within the daily cap you set.

How do I control what it can spend?

Four layers. Agent access is opt-in per card, so exposure per purchase is naturally capped by that card's balance. A daily spend cap (default $500, adjustable) limits agent-initiated funding in any rolling 24-hour window, enforced server-side. You're notified whenever the agent reads credentials or moves money. And revoking the key cuts access instantly.

What does it cost?

The MCP feature itself is free. Standard card pricing applies: a one-time $10 card issuance fee, the standard top-up fee with automatic volume discounts, and no monthly fees. The agent can quote the exact all-in cost of any card operation before spending anything.

Where can the agent pay?

The cards are virtual Visa/Mastercard, so they work at merchants that accept Visa or Mastercard online. There's no fixed cardholder name or billing address — any name and address works at checkout, which suits automated flows well. Two card types cover the common cases: one for recurring charges like AI tools, ads and cloud, and one for Apple Pay / Google Pay one-time purchases like flights and hotels.

Which clients are supported, technically?

Anything that speaks MCP. The server runs standard MCP over Streamable HTTP with Bearer key authentication, rate-limited at 60 requests per minute. If your client can connect to a remote MCP server with an auth header, it can use WaldenPay.

Give your agent a card

Generate a key, paste one config block, flip a toggle on a card — and your agent completes the next purchase itself, 3DS code included.