How AI Agents Make Payments in 2026

How AI agents make payments is one of the most important infrastructure questions of 2026. Agents can browse the web, write code, manage projects, and communicate with APIs. But until they can spend money, they hit a wall every time a task requires a purchase.

This post explains the full payment flow for AI agents, covers the different payment rails available today, and shows how the pieces fit together.

The Agent Payment Flow

Every agent payment follows the same basic pattern, regardless of the payment rail:

1. Intent Declaration

The agent determines that a purchase is needed and declares what it wants to buy. This is not just "charge $50." It is a structured intent:

{
  "purpose": "Purchase Pro plan on Vercel",
  "merchant": "vercel.com",
  "estimated_amount_cents": 2000,
  "currency": "USD",
  "justification": "Project requires serverless functions beyond free tier"
}

The intent serves as both a policy check and an audit record. It answers the question: why is this agent spending money?

2. Policy Evaluation

Before any payment credential is issued, the intent is checked against the agent's spending policy. The policy defines:

• ▸Maximum amount per transaction
• ▸Daily and monthly spend limits
• ▸Allowed merchants or merchant categories
• ▸Whether human approval is required

If the intent violates the policy, it is rejected. The agent is told why, and no payment credential is created.

3. Credential Issuance

If the policy allows it, the agent receives a payment credential. This could be a virtual card number, a bank account for ACH, or a crypto wallet address. The credential is scoped to the declared intent.

4. Payment Execution

The agent uses the credential to complete the payment. For a card payment, this means filling a checkout form. For ACH, it means initiating a transfer. For crypto, it means signing a transaction.

5. Settlement and Reconciliation

The payment settles, and the platform records the full lifecycle: intent, policy decision, credential issued, transaction details, and settlement confirmation. This audit trail is what makes agent payments governable.

Payment Rail 1: Virtual Cards

Virtual cards are the workhorse of agent payments. They work with any merchant that accepts online card payments, which is effectively every website.

Why Cards Work for Agents

• ▸Universal acceptance. Cards work at millions of merchants without any merchant-side integration.
• ▸Programmable controls. Spend limits, merchant locks, and single-use expiration are enforced at the network level.
• ▸Instant issuance. A card can be created in milliseconds, used once, and discarded.
• ▸Familiar checkout flows. Agents fill the same forms that humans do. No special merchant support needed.

How It Works

1. ▸Agent declares intent to buy something
2. ▸Platform issues a virtual Visa or Mastercard
3. ▸Agent enters card details at checkout
4. ▸Transaction is authorized against the policy in real time
5. ▸Card expires after use (if single-use)

Limitations

• ▸Card-not-present fees. Online card transactions incur higher interchange fees than other rails.
• ▸Checkout friction. Some merchants have CAPTCHAs, 3D Secure challenges, or other anti-bot measures that can block agents.
• ▸Settlement delay. Card transactions take 1 to 3 business days to fully settle.

For a deep dive into agent card options, see our credit cards for AI agents guide.

Payment Rail 2: ACH and Wire Transfers

For larger payments, especially B2B transactions, bank transfers are often the better choice.

When Agents Use ACH/Wire

• ▸Vendor invoices. Paying a cloud provider's monthly invoice via ACH instead of card.
• ▸Large deposits. Funding a new account that requires a wire transfer.
• ▸Lower fees. ACH costs a fraction of card interchange for high-value transactions.
• ▸Recurring payments. Setting up autopay for services that support bank-to-bank billing.

How It Works

1. ▸Agent declares intent to pay an invoice or fund an account
2. ▸Platform provisions a virtual bank account or initiates a transfer from an existing one
3. ▸Agent provides the bank details to the payee (or the platform sends the transfer directly)
4. ▸Funds move via ACH (1 to 3 days) or wire (same day)

Limitations

• ▸Speed. ACH is not instant. Same-day ACH exists but costs more. Wires are faster but expensive.
• ▸Irreversibility. Wire transfers cannot be reversed easily. A wrong transfer is harder to fix than a card chargeback.
• ▸Limited to B2B. Most consumer merchants do not accept ACH at checkout. This rail is for vendor payments and account funding.

Payment Rail 3: Crypto and Stablecoins

Crypto payments, especially stablecoins like USDC, are gaining traction for agent-to-agent and agent-to-API payments.

When Agents Use Crypto

• ▸API billing. Some AI and data APIs accept USDC directly.
• ▸Agent-to-agent payments. When one agent needs to pay another agent's service, stablecoins provide instant settlement without intermediaries.
• ▸Cross-border payments. Stablecoins settle globally in seconds without the cost and delay of international wire transfers.
• ▸x402 protocol. An emerging standard where APIs return an HTTP 402 "Payment Required" response, and the agent pays with crypto to unlock the resource.

How It Works

1. ▸Agent declares intent to pay for an API call or service
2. ▸Platform provisions a wallet or signs a transaction from an existing one
3. ▸Stablecoin transfer is sent to the payee's address
4. ▸Settlement is near-instant on supported chains

Limitations

• ▸Limited merchant acceptance. Most traditional merchants do not accept crypto. This rail is primarily for APIs, digital services, and agent-to-agent commerce.
• ▸Volatility risk. Stablecoins mitigate this, but non-stablecoin payments carry price risk.
• ▸Regulatory uncertainty. Crypto payment regulations vary by jurisdiction and are still evolving.

The x402 Protocol

x402 deserves its own section because it represents a fundamentally new payment model for agents.

The HTTP specification has always included status code 402, "Payment Required." It was reserved for future use. x402 finally puts it to work.

Here is the flow:

1. ▸Agent makes an API request
2. ▸Server returns 402 Payment Required with a payment envelope (price, accepted currencies, payment address)
3. ▸Agent's payment client automatically constructs and signs a payment
4. ▸Agent retries the request with a payment proof header
5. ▸Server validates payment and returns the requested resource

This is machine-to-machine commerce at the protocol level. No checkout forms, no card numbers, no manual intervention. The agent discovers the price, pays, and gets the resource in a single request cycle.

x402 is still early. Adoption is growing among AI-focused API providers, but mainstream merchants are years away from supporting it. For now, it is a complement to card-based payments, not a replacement.

How Proxy Covers All Three Rails

Most agent payment platforms focus on one rail. Proxy supports all three through a single API:

• ▸Virtual cards for any merchant that accepts online payments. Single-use or multi-use, with full policy controls.
• ▸Bank accounts for ACH and wire transfers. Virtual accounts for receiving funds, outbound transfers for paying vendors.
• ▸Crypto wallets for stablecoin payments and x402 protocol support.

The agent does not need to know which rail to use. It declares an intent, and Proxy routes the payment through the appropriate channel based on the merchant, amount, and policy.

{
  "intent": "Pay Neon invoice #4821",
  "amount_cents": 14900,
  "preferred_rail": "ach",
  "fallback_rail": "card"
}

If the preferred rail is not available, Proxy falls back automatically.

What Comes Next

Agent payments are evolving fast. Here is what to expect over the next 12 months:

• ▸More x402 adoption. As agent-to-API commerce grows, expect more providers to support pay-per-request billing via x402.
• ▸Smarter policies. Spending policies will incorporate context from the agent's task, not just static limits. An agent working on a high-priority deployment might get a temporarily elevated budget.
• ▸Multi-agent orchestration. Teams of agents will share budgets, with a lead agent allocating spend to sub-agents based on task requirements.
• ▸Real-time reconciliation. Finance teams will get instant visibility into agent spend, not monthly reports.

For a comparison of the card-based options available today, see our virtual card API comparison.

Start Building

Proxy gives your agents access to every major payment rail through a single platform. Virtual cards, bank accounts, and crypto wallets, all governed by policies you define and audited end to end.

Create a free account at useproxy.ai and connect your first agent in minutes.