Skip to content

Payment Required

URI: https://docs.ankatech.co/errors/payment-required
HTTP Status: 402 Payment Required

When you see this

The request was refused on licensing grounds that are specific to your usage — a plan or usage limit rather than the deployment's own license term.

This is not the deployment-expiry refusal

An expired deployment license is a different problem with a different remedy, and it carries its own type: Deployment License Expired. Both answer 402, so dispatch on the type URI and never on the detail text. If you are reading this page because a previously working encrypt, sign or key-creation call started returning 402, check the type first — it is most likely the deployment page, not this one.

Common Causes

  • Usage limit exceeded
    You have consumed all available API calls, cryptographic operations, or storage quota for your current plan.

  • Credit depletion
    Your prepaid credits have been exhausted and need to be replenished.

  • Feature tier restriction
    You attempted to use a premium feature not included in your current subscription tier.

  • Concurrent operation limit
    You've exceeded the maximum number of concurrent operations allowed by your license.

How to Resolve

  1. Read the type first

    • …/errors/payment-required — a usage or plan limit; continue with the steps below.
    • …/errors/deployment-license-expired — the deployment's license has lapsed. Nothing on your side resolves it; see that page.

  2. Check your usage against your plan

    • Review current usage against your plan limits in the admin console.
    • Your platform administrator can read the deployment's own license state from the License Server; it is an administrator surface, not a client one.

  3. Renew or upgrade your plan

    • Contact your account manager or visit the AnkaSecure portal.
    • Consider upgrading to a higher tier if you consistently exceed usage limits.

  4. Purchase additional credits

    • For pay-as-you-go plans, add credits through the billing portal.
    • Review usage patterns to estimate required credit amounts.

  5. Optimize usage

    • Implement caching strategies to reduce redundant API calls.
    • Batch operations where possible to maximize efficiency.
    • Review and remove unused keys or inactive services.

Response Example

{
  "type": "https://docs.ankatech.co/errors/payment-required",
  "title": "Payment Required",
  "status": 402,
  "detail": "License limit exceeded for client: 7c9e6679-7425-40de-944b-e07fc1f90ae7",
  "instance": "/api/v3/crypto/encrypt",
  "timestamp": 1791676805
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details. Core API's license interceptor writes exactly the six members above; it sets no correlation member in the body, so correlate a request by the X-Correlation-Id response header.

If you need immediate assistance with license renewal or have questions about pricing plans, please contact [email protected] or consult the full Developer Hub Reference.