# PAYMENT_REQUIRED

Canonical page: https://docs.ovok.com/errors/payment-required

**HTTP 402.** Problem type: [`https://docs.ovok.com/errors/payment-required`](https://docs.ovok.com/errors/payment-required).

## What this means [#what-this-means]

The project's plan stops this write. Ovok answers with a payment-required status when a write would take the project past a hard cap on its plan, such as monitored patients or sub-tenants. Ovok's own refusals name `PLAN_LIMIT_REACHED`, so you see this code only when a payment-required answer names no other code.

## Troubleshooting [#troubleshooting]

1. Check `type`. If it ends in `plan-limit-reached`, follow that page. It names the plan, the limit and the resource.
2. Ask an admin of the parent project to buy a larger plan in the console. The new limit applies once the payment is confirmed.
3. Free room instead if you do not need a larger plan. Delete test patients that are enrolled in Signals, or remove sub-tenants you no longer use.

## Retry safely [#retry-safely]

Retry after the plan changes or after you free room. An unchanged retry gets the same answer. The write was refused before anything was saved, so no cleanup is needed.

## If the problem persists [#if-the-problem-persists]

Share the HTTP status, problem `type`, request path, response timestamp and `traceId` with your administrator or support contact. Remove access tokens, provider secrets and patient data first. The [Error responses guide](/errors) explains the response fields, and the [machine-code registry](/errors/machine-codes) lists every endpoint-specific type.
