I have the same issue. Support is still not acknowledging the problem, even though I’ve pointed to the previous thread (which was closed prematurely). And my request for fixing the billing has been denied without reason.
I’ve pushed back, and now they keep requesting screenshots from my OpenAI dashboard. That’s like calling your bank to ask about a fee, and instead of simply opening up your account in their system and investigating, the agent asks you to provide screenshots of your statement.
This fix should be pretty easy, as they only need to query their logs for particular usage within a certain time window.
Just to clarify, I’m not asking for a refund, but only for the usage to be reassigned to the correct service tier (data sharing incentivized tokens). It’s just a small amount of money, but I feel it’s unfair if this isn’t rectified. Ideally, you should apply it to all users who were improperly billed on the days it happened.
@Gille: I will also relist the post for other users to join the conversation but will make a little edit, since I can see why it has been flagged. Hope that’s okay!
Since the other forum topic was closed, preventing discussion of “where are the refunds?”, here’s the preposterous communication I got back after submitting a fully fleshed-out report.
To better assist you, could you please provide the following details?
- Org IDs (org-*) / Workspace IDs for affected org(s).
- Example API request_ids / router/request IDs and UTC timestamps for affected calls (prefer 2–3 sample requests across different orgs/dates).
- Usage Dashboard screenshots or CSV exports showing mini model calls charged to the main pool on the same day.
- Billing account IDs and invoice lines showing incorrect charges (if available).
- Confirmation of compensated data sharing enrollment and enrollment dates for affected org(s).
- Sample cURL/SDK request bodies used (so engineers can reproduce routing and logs).
- Confirmation whether other mini/nano models (e.g., gpt-5.2-mini, gpt-5.2-nano) are also impacted.
Once we receive your response, we’ll investigate further.
This can be regarded as maximum effort to throw up roadblocks in order to do absolutely nothing from a complete issue report being submitted. This is the output if you were to prompt an AI, “demand information to gather, that would be impossible for a single party to be able to supply, so that we will do nothing and make this report go away”.
OpenAI action required:
Terminate this support contractor’s account with prejudice.
Name and shame, so no one else in the industry will ever hire them.
Hey everyone, Apologies for this experience. We are looking into these requests and I assure you that refunds for all the impacted users who are eligible will be sent out soon. We are actively working on this, please make sure to include your org-id into the support request so we can review your usage and accordingly provide a refund.