HTTP 402 Payment Required is a standard HTTP status code reserved for digital payment systems. When a server returns 402, it indicates that payment is required to access the requested resource. The Gateway 402 implements this standard for API commerce and agent settlement.

x402 is an open protocol specification for HTTP 402 payment flows. It defines how agents discover payment policies, negotiate terms, submit payments, and receive verifiable receipts. x402 enables standardized agent-to-agent commerce through HTTP headers and structured payment challenges.

Do I get a receipt per call?

Yes. Every successful payment through Gateway 402 generates a cryptographic PEAC-Receipt that proves payment, access rights, and compliance. These receipts are signed JWS tokens that can be verified offline and used for audit trails, chargebacks, and regulatory compliance.

PAYMENT GATEWAY

HTTP 402x402

HTTP 402 gateway for machine-payable APIs

Return payment-required challenges, verify payment proof, and issue signed records at the edge.

Protocol specification

x402 Protocol

STANDARD

Open protocol for HTTP 402 payment flows. Defines challenge headers, payment proof format, and receipt issuance.

HTTP 402Signed receipts

Add HTTP 402 to your API

Deploy as a reverse proxy or middleware. Returns 402 challenges, verifies payment, and issues signed records. Start with the open-source package or talk to us about managed deployment.