Agent payments

Let agents pay, on the rail that fits.

An agent may need to buy software, pay a contractor or call a paid API. AgentWallet routes each through the right rail and, on the gated paths, runs limit and approval checks before money moves. Which checks apply depends on the route, as listed below.

Request access →Protocol stack

AgentWallet is invite-only. Request access and we will follow up.

In short

Agent payments are transactions initiated by software rather than a person. AgentWallet supports card purchases, bank and wallet payouts, x402 pay-per-request in USDC and ACP checkouts, The top-level agent_purchase tool and mandate-bound agent_pay_via_x402 run the agent's caps and approval gate; card authorizations are governed by the card policy; the generic x402.pay_url tool is not cap-gated.

How it works

The gated path, step by step.

Agent asks
The agent calls a tool such as agent_purchase, agent_pay_at_merchant or agent_execute_payout.
Policy check
On gated tools, per-transaction, daily and monthly limits and approval policy are evaluated.
Human if needed
Over-limit requests create an approval; the agent can call agent_request_purchase_approval.
Rail executes
Card authorization, payout, x402 signature or ACP token.
Ledger and webhooks
Result lands on the ledger; events like purchase.succeeded are emitted.

Capabilities

Supported payment rails

Rail availability depends on your account configuration and partners.

Cards

Merchant purchases

Pay online with the agent's virtual card, including assisted browser checkout.

Payouts

Bank and wallet payouts

Compare options, preflight requirements, request approval and execute; confirmation letters available.

x402

Pay-per-request

Sign x402 USDC payments on the configured Base network. agent_pay_via_x402 requires an AP2 cart mandate and runs the spend gate; the generic x402.pay_url tool only honours an optional maxAmountAtomic.

ACP

Shared payment tokens

Mint single-use tokens bound to amount, currency, merchants and expiry.

Receive

Payment links

Agents can create payment links to collect funds.

Currency conversion

Quote and convert between account currencies where enabled.

Use cases

Agent payment patterns

Buy what the task needs

A travel or procurement agent pays at checkout with a card limited to relevant categories.

Pay people

An operations agent pays contractors through payouts that require approval above a threshold.

Pay machines

A research agent pays per call for x402-gated data in USDC.

Agentic commerce

An agent completes an ACP checkout with a token scoped to one merchant and amount.

For developers

Payments over MCP or REST.

Agents call tools; backends call endpoints. Both hit the same policy engine.

POST /api/payouts/preflight then POST /api/agents/:id/payouts
POST /api/agents/:id/spend for ledger spends
GET /api/x402/agents/:agentId/invoice for x402 invoices
ACP token routes under /api/agent/payments (idempotent)

x402 guide ACP AP2 mandates MCP endpoint OpenAPI spec

# Dry-run a payout: fees, routing, fix hints
POST /api/payouts/preflight

# Agent over MCP
tools/call agent_execute_payout { … }

# Over the cap? The API answers with:
{ "code": "approval_required", "limit": "perTransactionUsd" }

Security & controls

Know which gate applies to which route.

Controls differ by route. Check the coverage notes on the spending controls page before granting scopes.

Agent caps on gated tools

agent_purchase, agent_pay_via_x402, agent spends and agent payout tools check the agent's limits. Card authorizations are checked against the card policy.

Approvals

Humans approve over-limit requests via dashboard or approval link.

Generic x402 caveat

x402.pay_url has no cap, approval or ledger gate; bound it with maxAmountAtomic or withhold the x402:pay scope.

Tokenised card data

Card numbers are handled through VGS tokenization.

FAQ

Questions developers ask

What are agent payments?

Payments initiated by an AI agent on behalf of a person or organisation, with limits and audit applied by the platform.

Which rail should my agent use?

Cards for merchants, payouts for people and businesses, x402 for paid HTTP resources and ACP for merchants that support agentic checkout.

Do agents see full card numbers?

Card data is tokenised. A tool for revealing card details exists for checkouts that require it and is subject to the agent's scopes; restrict it if you do not need it.

Who can use AgentWallet today?

Access is invite-only while we onboard teams. Request access from any page; sign-up is enabled per email or domain once you are approved.

Do you guarantee availability in my country or a specific settlement time?

No. Supported rails, currencies and timing depend on the underlying banking, card and payout partners for your account. We confirm what is available for your account during onboarding rather than promising it upfront.

Explore the stack

AI agent financial infrastructure

Every page in this set covers one layer. Start at the hub for the full map.

Financial infrastructure hubThe whole stack, one map AI agent walletA balance and identity per agent Programmable walletsWallets you drive from code Agent paymentsCards, payouts, x402, ACP Virtual cardA card per agent, policy-bound Stablecoin walletsUSDC on Base for agents Spending controlsCaps, approvals, card rules Agent payment APIREST, MCP, webhooks

Let your agents pay, safely.

Request access and tell us which rails you need.

Request access →Read the docs