HTTP status code 402 is a non-standard status code that is reserved for future use. This status code was initially created to support digital cash or micropayment systems, indicating that the requested content will only be provided after the client has completed payment.
In practice, the usage of the 402 status code is not widespread, and different systems may use it in various ways. Sometimes, it is used on commercial websites or services to inform users that payment is required before they can access the desired content or features. If a user’s payment information cannot be verified, or if the payment has expired or become invalid, the server may return a 402 status code.
General Steps for Handling 402 Status Code
- Check Payment Information: Users should verify that the payment information they provided is complete and correct.
- Update Payment Information: If the payment has expired or become invalid, users need to update their payment information to continue accessing the resource.
- Contact Website Administrator: If users believe this is a system error, they should contact the website administrator to report the issue.
- Wait and Retry: If the error is temporary, users can wait for a while and try to access the resource again.
It is worth noting that although the 402 status code was designed for payment systems, there is currently no standard usage convention, and it is rarely used in practice. In fact, no browsers support the 402 status code, and errors are often displayed as a generic 4xx status code. If you are a website administrator, ensure that your site uses the latest encryption technologies to protect users’ payment information.
Related 4xx error code
- 400 Bad Request
- 401 Unauthorized
- 403 Forbidden
- 404 Not Found
- 405 Method Not Allowed
- 406 Not Acceptable
- 407 Proxy Authentication Required
- 408 Request Timeout
- 409 Conflict
- 410 Gone
- 411 Length Required
- 412 Precondition Failed
- 413 Payload Too Large
- 414 URI Too Long
- 415 Unsupported Media Type
- 416 Range Not Satisfiable
- 417 Expectation Failed
- 418 I’m a teapot
- 421 Misdirected Request
- 422 Unprocessable Entity (WebDAV)
- 423 Locked (WebDAV)
- 424 Failed Dependency (WebDAV)
- 425 Too Early
- 426 Upgrade Required
- 428 Precondition Required
- 429 Too Many Requests
- 431 Request Header Fields Too Large
- 451 Unavailable For Legal Reasons
- 499 Client Closed Request