GPT Image 2.5 is live — OpenAI's newest image model, targeted edits that leave the rest of the frame alone
All resources

· reAPI Team

API credits not received after payment: what to check

Find out why API credits are missing after payment. Check the receipt, payment status, account, balance and usage before retrying or contacting billing support.

API credits not received after payment: what to check

Your bank shows a transaction. The API dashboard still shows zero. Buying the same credits again might get you moving, but it leaves the first payment unexplained—and can leave you with two purchases to untangle.

Start with the purchase already made. Find it in the provider's payment history, keep its reference number, and read its status exactly as shown. A bank notification, a completed merchant purchase and an available API balance are different observations. The next useful check depends on which of those you actually have.

Does the provider show a completed purchase?

A payment marked processing has not reached the same state as one marked succeeded. A checkout asking for additional authentication still needs that action. Stripe's payment lifecycle distinguishes these states; treating all of them as “the money went through” loses the information needed to resolve the problem.[1]

Compare the provider's purchase record with the bank entry for that transaction. Check the amount, currency and time, allowing for the timezone shown on each side. If the bank's label is unclear, ask the issuer what it means. If the merchant says the purchase completed, keep that receipt for the next step. Neither side's record needs to be guessed from the other.

Even a completed payment does not, by itself, show where the purchased credits went. Stripe separates payment from fulfillment, the step that supplies what was bought. It also documents delayed payment methods and cases where a buyer never reaches the return page after paying.[2] That explains why the checkout screen alone cannot settle the question. It does not establish that your provider lost a webhook or failed to update a database.

There is little benefit in repeatedly refreshing an abandoned checkout tab once you have a completed purchase reference. Move to the account and balance records. Conversely, if the transaction is still processing, investigate that payment's documented timing before treating it as a missing credit entry.

Follow the purchase to the account your application uses

Consider a troubleshooting example: you fund a team account in the browser, while a background worker still holds a key created under your personal account. The team dashboard can show the correct purchase and the worker can still report insufficient funds. Nothing about the successful payment changes which account owns that key.

Put the funded account beside the running application's account. Include the organization or project where the service uses those divisions. Use a safe key name or identifier to make the comparison; the secret itself does not belong in a screenshot or support message. Check the deployed worker, not just the environment on your laptop.

OpenAI's prepaid instructions specifically direct users to the billing overview of the API organization they funded.[3] That is also where to check prepaid API credit when a search for “credits in ChatGPT” has led you to the wrong place. Asking a chatbot for a balance cannot establish what the API billing overview records. The same overview provides the credit-purchase option, but an unexplained earlier purchase should be resolved before another is made.

For reAPI, a balance lookup lets you check the account behind a credential without generating a paid image or video:

GET /api/v1/balance
Authorization: Bearer YOUR_API_KEY

This is the documented request shape, not a request executed for this article. The endpoint returns the authenticated credential's current balance and does not consume credits.[4] Make the lookup through your normal secure tooling, using the application's intended credential.

Read the result alongside the dashboard at roughly the same time. Once you have confirmed that both views belong to the same account, matching balances let you move on to the balance movements. Matching numbers alone are not enough: two different accounts can both show zero. If they differ, save both timestamps and the safe account identifiers. A difference is useful evidence; it is not yet proof that money disappeared.

Changing a secret in one place also does not prove that an already running process loaded it. Follow your application's configuration loading and deployment procedure before deciding that the worker uses the newly checked credential. There is no need to rotate every key or restart unrelated services merely to identify the account involved.

A zero balance can still include the purchase

The current balance does not show everything that happened since checkout. It may include an older shortfall, the new purchase and work submitted afterward. Look for those movements separately.

Here is a hypothetical account using invented credit units. The arithmetic is illustrative, not a provider's price or a report of a real customer transaction:

MovementChangeBalance afterward
Earlier usage leaves a shortfall—−5
New purchase is applied+2015
Subsequent work consumes credits−150

The final zero looks the same as a purchase that never arrived. The history is entirely different. In this example, asking support to locate all twenty units as missing would overlook both the earlier five-unit shortfall and the fifteen units used afterward.

OpenAI documents a specific version of the first step: usage processed before access stops can produce a negative balance, which is deducted from the next purchase.[3] Check for that rule where it applies; do not assume every provider handles overdraw identically. The separate guide to a negative prepaid API balance covers that question in more detail.

For the second step, inspect requests around the purchase time. A worker can consume newly available funds while you are still looking at the billing page. If you control nonessential automated submissions, pause them during the comparison and note when you did so. Tasks already accepted need their own records; stopping new submissions does not explain or cancel earlier work.

reAPI's task documentation separates an initial reservation from the final settled result.[5] Match the relevant tasks to those fields instead of treating every movement in available balance as a final charge. A purchase record answers whether value was added. Task records answer what happened to value associated with a generation.

If the consumption is familiar, adjust the workload or monitoring once the purchase is reconciled. If it is unfamiliar, preserve the request identifiers and investigate the key or application responsible before adding more funds. Buying again can hide the symptom briefly while the same unexplained consumption continues.

The balance is correct, but the API still rejects requests

At this point the payment investigation may be finished. Keep the successful purchase and balance evidence, then inspect the failing API response as a separate problem.

Capture the HTTP status and response body from the existing client or logs. Include the provider's error code, message and returned request identifier where available. An application's “payment failed” banner may summarize several different failures; the response tells you what the service actually rejected. Remove authorization headers and private request content before sharing it.

For reAPI, the documented insufficient-credit response is HTTP 402 with code 30001. Its error reference distinguishes that condition from authentication and rate limiting.[5] A positive balance also needs to be sufficient for the particular request; “greater than zero” does not establish that any generation can start.

Use the receiving provider's definitions. A familiar status number does not replace the message or make every service's policy identical. In particular, do not assume that every 429 means the purchase failed—or that it always describes the same kind of limit. More credit only helps when the rejected request actually lacks the required available funds.

Keep the comparison narrow. If your dashboard balance and authenticated lookup agree, but a worker receives an authentication error, investigate what that worker sends. If the response names a limit, check that limit. If it names insufficient credit despite apparently sufficient available value, give support the balance observation and request details together. Repeating checkout cannot correct a wrong endpoint, stale credential or unrelated access restriction.

When there is still no credit entry

Use the provider's own waiting guidance. OpenRouter says to allow up to one hour for Stripe purchases and to contact billing with purchase details if a charge exists but credits remain missing. OpenAI says a successful purchase can take a few minutes to update, and asks users to contact support with the organization and purchase reference before buying again if the records still do not match.[6][3] These are the respective providers' instructions reviewed on November 15, 2026, not a universal deadline for every payment method.

While waiting, keep the original receipt and the balance observations. Record additional purchase attempts individually if you already made them. Two transactions with the same amount still have different references and may have different outcomes. Combining them into one total makes it harder to establish which purchase needs attention.

Keep an observation time beside each balance screenshot or lookup. A value captured before the purchase and another captured after further usage are not simultaneous views of the account. That timeline can explain an apparent disagreement without changing either record.

Once the relevant window has passed, ask for a trace of the specific purchase. A useful message can be short:

Purchase [reference], for [amount and currency], is marked [exact status] at [time and timezone]. It belongs to [account or organization]. The balance was [value] at [time] and is [value] now. I cannot find the corresponding credit entry. Please confirm the account funded and the posting or adjustment associated with this purchase.

If a credit entry exists but the subsequent movement is unexplained, say that instead and attach the relevant request identifiers. Send only the necessary receipt or bank-record excerpt, with unrelated transactions and sensitive details removed. Do not include card security codes, passwords or API keys. The question support needs to answer is where this purchase went; give it enough information to identify that purchase without another checkout attempt.

References

  1. Stripe. How Payment Intents and Setup Intents work. Retrieved November 15, 2026. Payment lifecycle documentation.
  2. Stripe. Fulfill orders. Retrieved November 15, 2026. Checkout fulfillment documentation.
  3. OpenAI. Setting up and managing prepaid API billing. Retrieved November 15, 2026. Prepaid billing guidance.
  4. reAPI. Balance reference. Retrieved November 15, 2026. Read the authenticated account's balance.
  5. reAPI. Errors and Tasks references. Retrieved November 15, 2026. Error codes and task settlement.
  6. OpenRouter. Support: Credit and Billing Systems. Retrieved November 15, 2026.
All resources