English

x402 Service Guide

This page explains how merchants integrate with the live Axon x402 facilitator and how users complete payments through merchants that support x402.

Live environment

For merchants

Merchants now self-onboard with wallet signature proof, create runtime API keys, and publish one or more payment routes per resource. Discovery is public, while verification and settlement remain server-side calls from the merchant.

  1. Complete wallet-signature onboarding at /v1/merchant/onboard/*.
  2. Create a payment_runtime API key.
  3. Create a resource and one or more routes.
  4. Return 402 payment_required from the protected endpoint with one accept route.
  5. The buyer prepares a payment from that accept route.
  6. Call POST /v2/x402/verify from your backend.
  7. If verification succeeds, call POST /v2/x402/settle.
  8. Return your business response after settlement succeeds.

Open the merchant self-serve guide.

For users

Users normally do not call the facilitator directly. They interact with the merchant twice: once to receive a 402 response, then again to submit the signed payment payload.

  1. Request the paid merchant endpoint.
  2. Read the returned accept route.
  3. If the wallet only holds native AXON, wrap the required amount into WAXON402.
  4. Sign the EIP-3009 transferWithAuthorization payload.
  5. Send the payment to the merchant.
  6. The merchant verifies, settles, and returns the paid result.

Waiting and retrying

Useful paths

Live merchant example: Map the Frontier