Skip to main content
billing_not_configured means the billing routes are switched off on the service you called. Read this page when a billing call answers with this code.

What happened

Routes: GET /v1/billing, POST /v1/billing/checkout, POST /v1/billing/portal, PUT /v1/billing/auto-recharge. The payment settings the billing routes need are absent, so every billing route answers with this code. The scope is checked first: a key without billing_read (for GET) or billing_write (for the others) gets 403 scope_denied instead. Nothing was created: no checkout page, no portal session, and no change to auto-recharge.

How to fix

  • Retry later. It is a service-side configuration problem, and retrying at once gets the same answer.
  • If it persists, report the request_id.

Example

Reading the balance, with backoff on 5xx:
  • Credits and billing - balance, checkout and transactions.
  • Billing - the console page that uses these routes once billing is available.
  • Error handling - a status-to-action table and a retry helper for every error.
  • Problem codes - every code, its status, and whether a retry can help.