HTTP 402 Payment Required vs 425 Too Early
Both HTTP 402 (Payment Required) and 425 (Too Early) belong to the 4xx Client Error category. 402 indicates that reserved for future use. Originally intended for digital payment systems, some APIs use it to indicate a billing or subscription issue. Meanwhile, 425 means that the server is unwilling to risk processing a request that might be replayed. Used with TLS 1.3 early data (0-RTT).
Description
Reserved for future use. Originally intended for digital payment systems, some APIs use it to indicate a billing or subscription issue.
When You See It
On some APIs when a subscription has expired or payment is needed.
How to Fix
Check your billing status, update payment method, or upgrade your subscription.
Description
The server is unwilling to risk processing a request that might be replayed. Used with TLS 1.3 early data (0-RTT).
When You See It
When a server rejects a request sent as TLS 1.3 early data due to replay risk.
How to Fix
Retry the request after the TLS handshake completes.
Key Differences
HTTP 402: Reserved for future use. Originally intended for digital payment systems, some APIs use it to indicate a billing or subscription issue.
HTTP 425: The server is unwilling to risk processing a request that might be replayed. Used with TLS 1.3 early data (0-RTT).
You encounter 402 when on some APIs when a subscription has expired or payment is needed.
You encounter 425 when when a server rejects a request sent as TLS 1.3 early data due to replay risk.
When to Use Which
For 402 (Payment Required): Check your billing status, update payment method, or upgrade your subscription. For 425 (Too Early): Retry the request after the TLS handshake completes.