HTTP Status Codes

HTTP 402 Payment Required

402
LowWeb ServerReference page

Payment Required

The 402 code is a non-standardized response originally intended for digital cash implementations, but frequently used by APIs to signal billing limitations.

Visual summary

A quick reference view of how HTTP 402 works: A paywall or toll booth blocking the path until a financial or quota requirement is met.

HTTP 402 visual summary showing a paywall or toll booth blocking the path until a financial or quota requirement is met.
Visual summary: 402 means access is blocked pending a payment, token, or quota upgrade.

What 402 Means

The shortest useful reading of this status code.

Payment Required.

This status falls into the 4xx class, indicating a client-side error outcome for the request.

Quick read

Payment Required

The 402 code is a non-standardized response originally intended for digital cash implementations, but frequently used by APIs to signal billing limitations.

Technical Context

How this status behaves without turning the page into a repair guide.

Standard usage

This status indicates that the client's request cannot be processed until a payment is made or a quota is increased.

Technical nuance

It uniquely communicates financial or tier-based restrictions rather than permissions (403) or authentication (401).

Related HTTP Codes

Nearby HTTP status codes help clarify how 402 differs inside the same response family.

402

Payment Required

The 402 code is a non-standardized response originally intended for digital cash implementations, but frequently used by APIs to signal billing limitations.

400

Bad Request

the server cannot process the request because it is malformed

401

Unauthorized

valid authentication credentials are missing for the target resource

403

Forbidden

the server understood the request but refuses to authorize it

Common Causes

Subscription expired

A common condition that triggers a 402 response when the web server evaluates the transaction.

Daily quota exceeded

A common condition that triggers a 402 response when the web server evaluates the transaction.

Premium feature access blocked

A common condition that triggers a 402 response when the web server evaluates the transaction.

Typical Scenarios

01

A developer exceeds the freemium API rate limit

02

A user attempts to read a paywalled article without an active subscription

What To Know

Verification of the API provider's billing dashboard or account subscription status is the standard path to resolving these limitations.

Frequently Asked Questions

Common interpretation questions about HTTP 402.

It indicates that the service requires a payment or tier upgrade to fulfill the request.