What does HTTP 402 Payment Required mean?
Short answer
402 Payment Required is an HTTP status code that means the server will not answer until it is paid. The HTTP standard reserves the code "for future use" and does not say how payment should work. Protocols such as x402, MPP and L402 fill that gap by defining what a 402 reply must contain.
What the standard says
HTTP status codes in the 400 range mean the request cannot be fulfilled as sent. 401 means "sign in first". 403 means "you are not allowed". 404 means "not found". 402 sits between them and means "pay first".
The current HTTP standard, RFC 9110, gives 402 one line: the code "is reserved for future use". It defines no headers, no price format and no way to pay. That is why, for most of the web's history, almost nothing returned it.
Who uses 402 today
Three payment protocols give the code a concrete meaning. All three reply 402, but each puts the payment details somewhere different.
| Protocol | Where the price is | Paid with |
|---|---|---|
| x402 | PAYMENT-REQUIRED header (version 2) or the JSON body (version 1) | Tokens on many blockchains, usually USDC |
| MPP | WWW-Authenticate: Payment header | Stablecoins, cards and Lightning |
| L402 | WWW-Authenticate: L402 header with a Lightning invoice | Bitcoin over the Lightning Network |
One reply can carry more than one of these. A server may send both a PAYMENT-REQUIRED header and a WWW-Authenticate: Payment header, and each kind of client reads the one it understands.
If you got a 402 and did not expect it
- Calling an API from code: the endpoint charges per request. Look at the response headers to see which protocol it uses, or paste the address into the 402 checker.
- In a browser: some sites use 402 loosely to mean "your plan has run out" or "billing problem", with no payment protocol behind it. In that case the fix is in your account with that site, not in a wallet.
What 402 is not
A 402 is not an error in your request. The address and the input can be perfectly valid. It is the server quoting a price. A client that speaks the right protocol treats it as the first half of a normal exchange. See how x402 works.
Sources
- RFC 9110, HTTP Semantics, section 15.5.3
- x402 version 2 HTTP transport specification
- MPP compared with x402, mpp.dev
- L402 protocol specification
Facts checked against these sources on . Protocols change, so the official specification wins if it disagrees with this page. Read this page as Markdown.
Related questions
Who writes this. Ask402 is published by Havok Holdings LLC, which also runs Agent402, one of the x402 services covered here. Agent402 is labelled wherever it appears. Everything else is described from each project’s own documentation, and nobody pays to be listed.