How it works
A typical x402 payment flow follows five steps:- Client requests a resource — a standard HTTP request to a protected endpoint.
- Server responds with 402 — the response includes payment requirements (price, network, token, recipient).
- Client signs a payment — using their wallet, the client creates a signed payment payload matching the requirements.
- Client retries with payment — the original request is resent with the signed payment in a header.
- Facilitator verifies and settles — the server (via the facilitator) verifies the signature and settles the payment on-chain.
Abstract’s facilitator
Abstract runs a public x402 facilitator that any developer can use to accept and make payments on Abstract:| Facilitator URL | https://facilitator.x402.abs.xyz |
| Service fees | None |
| Gas fees | Sponsored via paymaster — you pay nothing |
| Supported networks | Abstract mainnet (eip155:2741), Abstract testnet (eip155:11124) |
Supported tokens
The facilitator works with any ERC-3009-capable token on Abstract. USDC is the recommended token and is used throughout these guides:| Network | Token | Address |
|---|---|---|
Mainnet (eip155:2741) | USDC | 0x84A71ccD554Cc1b02749b35d22F684CC8ec987e1 |
Testnet (eip155:11124) | USDC | 0xe4C7fBB0a626ed208021ccabA6Be1566905E2dFc |
Key concepts
| Term | Description |
|---|---|
| Client | The entity making a request and paying for access to a resource. |
| Server | The HTTP server that provides the resource and requires payment. |
| Facilitator | A service that verifies payment signatures and settles transactions on-chain. |
| Scheme | The payment logic — Abstract uses exact, which transfers a fixed amount per request. |
Get started
Accepting Payments
Add payment middleware to your API to charge for access on Abstract.
Making Payments
Use the client SDK to access x402-protected resources on Abstract.