# Billing and credit errors Source: https://docs.graphops.xyz/platform/errors/billing Each error below is identified by the `code` in the [error response](/platform/errors#error-response). The response's `docsUrl` links to the matching entry on this page. ## `billing_account_needs_review` Billing account needs review · HTTP 409 Conflict GraphOps found more than one billing account for this organization and cannot choose one safely, so purchases and billing pages are blocked until support reviews it. **What to do:** Contact support with the organization ID. Retrying does not resolve this. ## `billing_auto_top_up_authorization_failed` Automatic top-up setup failed · HTTP 500 Internal Server Error GraphOps could not start the card authorization for automatic top-ups. **What to do:** Refresh Billing and try again. If the error continues, contact support. ## `billing_auto_top_up_authorization_required` Card authorization required · HTTP 409 Conflict Automatic top-ups are off or have no authorized card, so you cannot turn them on or change their settings without authorizing a card. **What to do:** Authorize a card in Billing → Settings → Automatic top-ups. Completing the authorization turns automatic top-ups on. ## `billing_auto_top_up_invalid` Invalid automatic top-up settings · HTTP 400 Bad Request The threshold, credits per top-up or monthly spending limit is outside what your plan allows, or the authorization statement you accepted is no longer current. **What to do:** Adjust the settings to the values Billing allows, review the current authorization statement and try again. ## `billing_auto_top_up_unavailable` Automatic top-ups need a monthly plan · HTTP 409 Conflict Automatic top-ups need an active monthly plan. A plan that is set to cancel or whose payment needs attention does not qualify. **What to do:** Start a monthly plan, keep a plan that is set to cancel, or resolve the payment issue, then set up automatic top-ups again. ## `billing_auto_top_up_update_failed` Automatic top-up update failed · HTTP 500 Internal Server Error GraphOps could not save your automatic top-up settings. **What to do:** Refresh Billing and check your automatic top-up settings before trying again. If the error continues, contact support. ## `billing_catalog_get_failed` Billing catalog unavailable · HTTP 500 Internal Server Error GraphOps could not load the current plan and top-up prices. **What to do:** Retry the request. If the error continues, contact support. ## `billing_checkout_session_create_failed` Plan checkout failed · HTTP 500 Internal Server Error GraphOps could not start Stripe Checkout for a new monthly plan. **What to do:** Refresh Billing and check for a plan or an open checkout before trying again. If the error continues, contact support. ## `billing_email_update_failed` Billing email update failed · HTTP 500 Internal Server Error GraphOps could not save your organization's billing email. **What to do:** Refresh Billing and check the billing email before trying again. If the error continues, contact support. ## `billing_low_credit_recipients_required` Alert recipient required · HTTP 400 Bad Request Low-credit alerts are on, but neither the billing email nor any role is selected as a recipient. **What to do:** Select the billing email, at least one role, or both. ## `billing_low_credit_thresholds_invalid` Invalid low-credit thresholds · HTTP 400 Bad Request The low-credit thresholds include a duplicate, a value that is not a non-negative whole number of credits, or more thresholds than Billing allows. **What to do:** Enter distinct whole-number credit amounts, up to the number of thresholds Billing allows. ## `billing_low_credit_thresholds_required` Low-credit threshold required · HTTP 400 Bad Request Low-credit alerts are on, but no threshold is set. **What to do:** Add at least one threshold, or turn low-credit alerts off. ## `billing_maintenance` Billing changes paused · HTTP 503 Service Unavailable Billing changes are paused for maintenance. You can still view your plan, balance and invoices. **What to do:** Try again shortly. If the pause continues, check GraphOps status or contact support. ## `billing_notification_preferences_get_failed` Notification settings unavailable · HTTP 500 Internal Server Error GraphOps could not load your organization's billing notification settings. **What to do:** Refresh Billing. If the error continues, contact support. ## `billing_notification_preferences_unavailable` Notification settings not set up · HTTP 409 Conflict Billing notification settings have not been set up for this organization. **What to do:** Refresh Billing. If the error continues, contact support with the organization ID. ## `billing_notification_preferences_update_failed` Notification settings update failed · HTTP 500 Internal Server Error GraphOps could not save your billing notification settings. **What to do:** Refresh Billing and check the saved settings before trying again. If the error continues, contact support. ## `billing_notification_recipient_roles_invalid` Invalid alert recipient roles · HTTP 400 Bad Request The recipient roles include a role that does not exist or the same role more than once. **What to do:** Select each role once from the roles Billing offers. ## `billing_order_not_found` Order not found · HTTP 404 Not Found The plan increase or order in the request does not exist in this organization. **What to do:** Refresh Billing to load current pending payments, then try again. ## `billing_order_payment_failed` Payment page unavailable · HTTP 500 Internal Server Error GraphOps could not open the payment page for a pending automatic top-up. **What to do:** Refresh Billing and try again. If the error continues, contact support. ## `billing_order_payment_unavailable` Payment no longer pending · HTTP 409 Conflict The automatic top-up no longer needs you to pay or confirm it, for example because it was paid, canceled or expired. **What to do:** Refresh Billing and check the top-up's status in top-up activity. ## `billing_order_transition_invalid` Order already changed · HTTP 409 Conflict The order changed while your request was processed, so the requested change no longer applies. **What to do:** Refresh Billing and check the order's current status before trying again. ## `billing_organization_disabled` Organization disabled · HTTP 409 Conflict GraphOps has disabled this organization, so it cannot buy top-ups or set up automatic top-ups. **What to do:** Contact support. ## `billing_plan_already_current` No plan change needed · HTTP 409 Conflict Your plan already renews at the size you chose, or there is no scheduled change to cancel. **What to do:** Refresh Billing to check your current and renewal plan sizes. ## `billing_plan_change_amount_changed` Amount due changed · HTTP 409 Conflict The amount due today for the plan increase differs from the amount you reviewed, or the request did not include it. You have not been charged. **What to do:** Review the new amount due today and confirm the increase again. ## `billing_plan_increase_failed` Plan increase failed · HTTP 500 Internal Server Error GraphOps could not complete the plan increase, so your plan size did not change. You have not been charged. **What to do:** Contact support with the organization ID. ## `billing_plan_increase_pending` Plan increase in progress · HTTP 409 Conflict A plan increase is waiting for payment or is being processed, so you cannot make another plan change or cancel it yet. **What to do:** Complete or cancel the pending increase in Billing. If its payment is processing, wait a minute and refresh Billing. ## `billing_plan_quantity_invalid` Plan size out of range · HTTP 400 Bad Request The requested plan size is outside the sizes GraphOps offers. **What to do:** Choose a plan size within the range shown in Billing. ## `billing_portal_session_create_failed` Billing portal unavailable · HTTP 500 Internal Server Error GraphOps could not open the secure billing portal. **What to do:** Refresh Billing and try again. If the error continues, contact support. ## `billing_purchase_rate_limited` Too many billing requests · HTTP 429 Too Many Requests Your organization sent too many purchase, plan change or automatic top-up requests in a short time. **What to do:** Wait for the time in the response's `retryAfterSeconds` field, then try again. ## `billing_purchases_held` Purchases on hold · HTTP 409 Conflict GraphOps has put new purchases for this organization on hold, usually after a payment dispute or fraud report. Top-ups, plan increases and automatic top-ups are unavailable. **What to do:** Contact support to resolve the hold. ## `billing_state_get_failed` Billing unavailable · HTTP 500 Internal Server Error GraphOps could not load your organization's billing. This does not mean your plan or balance changed. **What to do:** Refresh Billing. If the error continues, contact support with the organization ID and the time of the error. ## `billing_state_projection_failed` Billing setup failed · HTTP 500 Internal Server Error GraphOps could not prepare your organization's billing before completing the request. **What to do:** Retry the request. If the error continues, contact support with the organization ID. ## `billing_state_unavailable` Billing not set up · HTTP 409 Conflict Billing has not been set up for this organization. **What to do:** Refresh Billing. If the error continues, contact support with the organization ID. ## `billing_subscription_change_blocked` Plan cannot change now · HTTP 409 Conflict Your plan cannot make this change in its current state. For example, there is no active plan, the plan is set to cancel or is not set to cancel, a payment needs attention or is still processing, or the plan needs support to change. **What to do:** Refresh Billing and follow its notice, such as Keep my plan or Resolve payment issue, then try again. If Billing says the plan needs support, contact support. ## `billing_subscription_changed` Billing changed · HTTP 409 Conflict Your plan or billing details changed while the request was processed, so it no longer matches what you reviewed. **What to do:** Refresh Billing, review the current state and try again. ## `billing_subscription_exists` Plan already exists · HTTP 409 Conflict Your organization already has a subscription that has not ended, so you cannot start another plan. **What to do:** Manage the existing plan in Billing. If Billing shows no plan, contact support. ## `billing_subscription_mismatch` Subscription does not match · HTTP 409 Conflict The subscription on record does not belong to this organization's billing account. **What to do:** Contact support with the organization ID. ## `billing_subscription_missing` No plan to cancel · HTTP 409 Conflict Your organization has no monthly plan to cancel. **What to do:** Refresh Billing to check your plan. ## `billing_subscription_preview_failed` Plan change preview failed · HTTP 500 Internal Server Error GraphOps could not calculate the cost of the plan change. **What to do:** Refresh Billing and try again. If the error continues, contact support. ## `billing_subscription_provisioning_active` Plan checkout already open · HTTP 409 Conflict A checkout for a new plan is already open for this organization. **What to do:** Continue the open checkout from Billing, or wait for it to expire before starting another. ## `billing_subscription_unsupported` Plan needs support to change · HTTP 400 Bad Request Your subscription is not on the standard monthly plan, so it cannot be changed or canceled from Billing. **What to do:** Contact support. ## `billing_subscription_update_failed` Plan update failed · HTTP 500 Internal Server Error GraphOps could not complete the plan change. **What to do:** Refresh Billing and check for an updated plan or a pending payment before trying again. If the state is still unclear, contact support with the time of the error. ## `billing_tax_location_invalid` Billing address needs updating · HTTP 409 Conflict Tax cannot be calculated for the billing address on your organization's billing account, so the plan increase was not charged. **What to do:** Update your billing address in Billing → Settings → Billing address & tax details, then try the increase again. ## `billing_top_up_activity_failed` Top-up activity unavailable · HTTP 500 Internal Server Error GraphOps could not load your organization's top-up activity. **What to do:** Refresh Billing. If the error continues, contact support. ## `billing_top_up_blocks_invalid` Top-up amount not allowed · HTTP 400 Bad Request The number of credits is outside the range for one top-up, or more than you can still buy at the current price. **What to do:** Choose an amount within the range shown in Billing → Top-ups. ## `billing_top_up_create_failed` Top-up failed to start · HTTP 500 Internal Server Error GraphOps could not start the top-up. **What to do:** Refresh Billing and check top-up activity before trying again. If the error continues, contact support. ## `billing_top_up_pay_as_you_go_cap_reached` Pay-as-you-go limit reached · HTTP 409 Conflict Your organization has reached its limit for pay-as-you-go top-ups over the last 30 days. **What to do:** Start or increase a monthly plan to buy credits at your plan price, or contact support to raise the limit. ## `billing_top_up_price_changed` Top-up price changed · HTTP 409 Conflict The price per million credits changed after you reviewed the top-up. You have not been charged. **What to do:** Review the new price and confirm the top-up again. ## `billing_unavailable` Billing temporarily unavailable · HTTP 503 Service Unavailable Billing is temporarily unavailable, so purchases and billing changes cannot be completed right now. **What to do:** Try again shortly. If the error continues, check GraphOps status or contact support. ## `credit_balance_get_failed` Credit balance unavailable · HTTP 500 Internal Server Error GraphOps could not load your credit balance. This does not mean your balance is zero. **What to do:** Refresh Billing. If the error continues, contact support with the organization ID. ## `credit_balance_unavailable` Credit balance not set up · HTTP 409 Conflict Credits have not been set up for this organization. **What to do:** Refresh Billing. If the error continues, contact support with the organization ID. ## `credit_ledger_list_failed` Credit ledger unavailable · HTTP 500 Internal Server Error GraphOps could not load your organization's credit ledger. **What to do:** Refresh Billing. If the error continues, contact support. ## `stripe_checkout_url_missing` Checkout unavailable · HTTP 503 Service Unavailable Stripe Checkout did not return a page for the card authorization. **What to do:** Try again. If the error continues, check GraphOps status or contact support. ## `stripe_customer_binding_conflict` Billing account link failed · HTTP 409 Conflict GraphOps could not link a billing account to this organization. **What to do:** Refresh Billing and try again. If the error continues, contact support with the organization ID. ## `stripe_subscription_list_invalid` Subscription history unavailable · HTTP 503 Service Unavailable GraphOps could not verify your organization's existing subscriptions before starting a new plan. **What to do:** Contact support with the organization ID. ## `stripe_subscription_projection_failed` Plan refresh failed · HTTP 500 Internal Server Error GraphOps could not refresh your plan before completing the request. **What to do:** Refresh Billing and try again. If the error continues, contact support.