How to Fix 402 Payment Required Error

By ErrorFix · Updated October 26, 2026 · 6 min read

What 402 Payment Required means

HTTP status 402 is a standard response code, but it is rarely used on ordinary websites, which is why it can look so confusing when it appears. It means the server understood your request perfectly well, but it will not complete it until payment is made. Unlike a 404, nothing is missing. Unlike a 500, nothing crashed. The door is simply locked until the bill is settled.

You will most often meet a 402 on subscription services, paywalled content, software-as-a-service tools, and APIs that charge per request or per month. In recent years the code has also gained a second life in machine-readable payment protocols, where a server returns 402 with payment instructions and the client pays and retries automatically. For an ordinary visitor, though, the meaning is much simpler: the account behind the request needs money, and that is the whole story.

It also helps to separate 402 from its neighbors. A 401 means you are not logged in. A 403 means you are logged in but not allowed in, whatever you pay. A 402 sits between them: you are recognized, and payment is the one thing standing in the way. That distinction matters because it tells you where to look — not at your password or your permissions, but at your billing page.

Common causes

• Expired or canceled subscription: a plan that lapsed, was canceled, or ended its trial will return 402 the moment the next paid feature is requested.
• Failed or declined payment: insufficient funds, an expired card, a wrong billing address, or a bank blocking the transaction all leave the account unpaid.
• Overdue invoice or usage quota exceeded: an unpaid invoice, a monthly API limit reached, or a pay-per-use balance run down to zero triggers the same code.
• Payment gateway or webhook failure: a payment may succeed at the bank but never reach the service, leaving the account marked unpaid on the service side.
• Wrong account or stale session: paying on one account while signed in to another, or a browser session holding the old unpaid status, keeps the error showing after payment.

How to fix the 402 Payment Required error — step by step

Start with the visitor steps (1–4). If you own the site or API, step 5 is where most persistent 402s get fixed.

1. Check your subscription and billing status. Sign in to the service and open its billing, subscription, or account page. Confirm the plan is active, the renewal date has not passed, and no payment is marked overdue, failed, or past due. If the plan shows expired, canceled, or suspended, renew it or restart the subscription, then sign out and sign back in so the new status takes effect before you retry the blocked page or feature.
2. Update your payment method and check the basics. Open your payment settings and check the card on file: the expiry date, the cardholder name, the billing address, and the security code must all match what your bank holds. Replace an expired card, fix a mistyped address, and confirm the account has enough funds or available credit for the charge. Save the updated method, wait a minute for the change to sync, and then retry the payment from the billing page rather than from a stale checkout link.
3. Handle a declined payment with your bank or another method. If the charge was declined, check your bank app or messages for a decline notice, since banks often block an unfamiliar, international, or large transaction until you approve it. Approve the transaction if it is legitimate, or try a different card, PayPal, or another payment method the service accepts. Avoid hammering the pay button: repeated failed attempts can trigger a temporary fraud block, so wait a few minutes between tries and use only one method at a time.
4. Clear stale billing data and retry cleanly. A browser session can keep showing the old unpaid status after you have already paid. Sign out of the service completely, clear the site cookies for that domain, and sign back in, or try an incognito window to test with a clean session. If you paid through an app, update the app and reopen it, and if you paid on a different device, give the account a minute to sync before retrying. A fresh sign-in is often what finally clears a 402 that lingers after a successful payment.
5. Site or API owner: check billing webhooks and plan enforcement. If you run the site or API, a 402 usually means your billing check is stricter than your payment state. Confirm payment webhooks from your provider are reaching your server and updating subscriptions, since a missed or failed webhook leaves a paying customer marked unpaid. Check grace periods, trial-end handling, and usage quotas so a customer is not blocked the moment a card hiccup occurs. Review your server logs for 402 responses and confirm the response includes a clear payment link or message instead of a bare error page.
6. Contact support with your payment proof. If your subscription shows paid and the 402 still appears, contact the service support team with the exact page or API endpoint, the time of the error, and your payment receipt or transaction ID. Ask them to check whether your account is stuck in an unpaid state on their side, which is a common result of a failed webhook or a duplicate account. As an owner receiving these reports, check the customer record in your payment dashboard first: the subscription status there is the truth your site should be matching.

Did this fix it? Quick checklist

• Your subscription shows active and no payment is overdue
• The blocked page or feature loads after a fresh sign-in
• It works in an incognito window and on another device
• Site owners: paying customers are no longer wrongly blocked by stale billing data

If the error only appears on one device, check that device for an old login or a second account — signing in to the paying account usually clears it. On the owner side, if 402s spiked right after a billing change, check the webhook endpoint and quota settings first, since those two changes cause most sudden waves of false 402s.