Skip to main content
x402 is an open payment standard that activates HTTP 402 Payment Required for practical use. It lets agents and applications charge for API access with a standard HTTP flow:
  1. Client requests a paid resource
  2. Server responds with 402 Payment Required
  3. Client signs a payment payload
  4. Client retries with payment attached
  5. A facilitator verifies and settles on-chain

When to use x402

Use x402 when you want:
  • the simplest pay-per-request integration path
  • a public facilitator on Abstract
  • a clean split between client and server middleware
Use MPP instead when you want HTTP-native charge and session payment modes in one protocol, especially for repeated micro-payments.

Abstract facilitator

Abstract runs a public x402 facilitator that any developer can use:

Supported token

The facilitator works with any ERC-3009-capable token on Abstract. USDC is the recommended token:

x402 vs MPP

Get started

Accept x402 Payments

Add payment middleware to your API.

Make x402 Payments

Build a client that can pay x402-protected resources.