Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.hel.io/llms.txt

Use this file to discover all available pages before exploring further.

MoonPay Commerce is agent-payable: an AI agent can buy products or services from MoonPay Commerce merchants on checkouts or deposits, without a human clicking through a web checkout. The agent settles the payment on-chain in main-net USDC, and the merchant receives funds the same way they would from a human payer.
All agent payments use real main-net USDC. Always confirm the amount, chain, and recipient with the user before spending.

Why Agent Payments

Traditional checkouts assume a browser, a cookie session, and a human clicking buttons. Agents don’t have any of those. Agentic payments give an autonomous client a machine-native way to:
  • Buy a product or service exposed via a checkout (Paylink or Charges)
  • Top up a recurring deposit balance for usage-based services
The merchant integration is unchanged — paylinks, charges, deposits, and webhooks all work the same. Only the payer side is different.

Supported Protocols

ProtocolStatusBest for
x402AvailableOne-time checkout, recurring deposits, any HTTP-based agent flow
MPPRoadmapOpen standard optimized for high-frequency, machine-to-machine transactions
MCP serverRoadmapMCP-compatible hosts (Claude Desktop, Cursor, Windsurf)
Agentic Commerce Protocol (ACP)RoadmapCatalog-style discovery and multi-step purchase flows
More protocols will be added as the agentic-payments ecosystem matures. The shared model — paylinks, deposits, on-chain settlement — stays the same across protocols.

Quick Start

Pay with x402

HTTP 402–based payment protocol. Pay any MoonPay Commerce paylink with mainnet USDC.

MoonPay CLI

Install mp to sign and submit x402 payments from the terminal or an agent runtime.

Create a Paylink

Generate a paylink for your product so agents can pay it.

Deposits

Recurring / balance-based deposits. Pair with x402 for usage-based agent billing.

How a Merchant Enables Agent Payments

If you already have a MoonPay Commerce checkout or deposit, you’re already agent-payable — no extra integration is required. The agent flow uses the same paylink ID as the human flow. The only merchant-side considerations:
  • Paylink eligibility — paylinks that require customer detail fields (email, name, custom fields) are not currently supported via x402; the agent will receive X402_UNSUPPORTED_FEATURES. Use a paylink without required customer details for agent flows.
  • Pricing — both fixed-price and dynamic-price paylinks are supported. Dynamic paylinks let the agent specify the amount at pay time.
  • Webhooks — agent payments fire the same paylink/deposit webhooks as human payments. Use them to react to settlement.

Security Model

  • Agents pay from a wallet they (or their user) control. MoonPay Commerce never holds the agent’s keys.
  • Each request pre-allocates a per-payer deposit wallet. Funds sweep from the deposit wallet to the merchant asynchronously after the on-chain payment is verified.
  • Rate limits apply per payer IP (10 requests / 60s) to prevent abuse.
For the full payment flow, error handling, and code examples, continue to Pay with x402.