Builder Path
Common implementation paths
Developers usually approach x402 from one of several angles depending on whether they sell resources, buy resources, or operate infrastructure.
- Seller integration Add a 402 response path to a server, publish payment requirements, verify the payment, and release the resource.
- Buyer integration Build a client that can read payment requirements, sign or submit payment, retry the request, and record the receipt.
- Gateway or proxy Put a payment-aware layer in front of an existing API so the upstream service does not need to be rewritten.
- Facilitator integration Use verify and settle endpoints instead of directly implementing every chain-specific settlement path.
- Testing and validation Use playgrounds, examples, testnets, and validators before exposing production paid endpoints.