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 monetization and agent commerce.

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

The payment infrastructure for agents

Enterprise-grade HTTP 402 Payment Required gateway with multi-rail settlement support. Enable autonomous agents to securely purchase access to your APIs, content, and services through standardized payment protocols.

Enable HTTP 402 commerce for AI agents and automated economy use cases. Gateway 402 brings x402 commerce to your infrastructure with machine-payable APIs, agent-native payments, and PEAC-Receipts for every transaction.

Talk to payments engineer Configuration template

Protocol specification

x402 Protocol

STANDARD

HTTP 402 compliant protocol with agent-native policy negotiation and verifiable receipts.

HTTP 402Agent-native

Deploy enterprise payment infrastructure

Enable autonomous agents to purchase access to your APIs and services through standardized payment infrastructure.

Talk to payments engineer View deployment guides