Skip to main content
NOPE
Low reported severity

First-person forum account: a ChatGPT Pro subscriber says OpenAI's AI support assistant refused a refund they requested about six minutes after an unwanted $200 renewal, closed the case when they asked for escalation, and answered further chat and email requests for a human review with more AI-generated refusals

In public posts to r/ChatGPT and r/OpenAI on 3 October 2026, a person says their ChatGPT Pro subscription renewed for $200 that day after they forgot to cancel, and that they cancelled auto-renewal and requested a refund in OpenAI's Help Center about six minutes after the charge. They say the Help Center's AI assistant declined without giving a reason specific to their account, and that when they asked for escalation the chat showed that the case was closed. A second chat asking specifically for a human billing specialist produced the same refusal, they write, and two email requests, one with five redacted screenshots, received replies marked as generated with AI support. The poster acknowledges that OpenAI's seven-day refund policy is discretionary and conditional, and says the unresolved problem is that they received no case-specific explanation and no confirmed human review. OpenAI's handling is described only by the poster, and the account is uncorroborated.

AI system
OpenAI Help Center assistant
OpenAI
Occurred
3 Oct 2026
Reported
3 October 2026
Event location
Unknown
What the AI did
Communicated with the person · Made a decision about the person
Reported harm
Financial Loss
Whose AI use
An institution’s AI use
Setting
Finance · Everyday life
Evidence
AI involvement reported · Causal attribution alleged · 2 sources, 1 underlying account
4 claims: 4 reported. 3 open questions
People reported harmed
1 person

AI system as recorded: OpenAI Help Center AI support assistant (chat) and AI-generated email support replies handling a ChatGPT Pro refund request

What Happened

The charge. The poster says that on 3 October 2026 their ChatGPT Pro plan renewed for $200 and that "I forgot to cancel beforehand and did not intend to renew". They give a timeline in Tbilisi time (UTC+4): the bank notification of the charge at 13:32:55, OpenAI's cancellation confirmation email at 13:34, and a first refund request in the Help Center at about 13:39, "approximately six minutes after the charge".

The chat refusals. The poster writes that "The AI declined without giving a reason specific to my account", and that when they requested escalation the chat displayed: "This case is closed. Create a new case to receive support." In the r/OpenAI version they put it as: "The Help Center assistant gave a generic refusal without identifying which eligibility requirement I failed." They say: "I opened another case specifically requesting a human billing specialist. Same generic refusal."

The email refusals. The poster says they then emailed support with the invoice and timeline and that "another refusal arrived, explicitly marked as generated with AI support". A reply with five redacted screenshots and another request for manual review, they write, "also received an AI-generated refusal".

The poster's position. The poster says they understand that the refund policy is "conditional, not an automatic entitlement", that they asked support to check their actual usage since renewal and explain which criterion they failed, and that "I also explicitly agreed that refunded subscription access would end". They write that "I still have no explanation specific to my case and no confirmed human review", and call it "an appalling way to treat a paying customer".

Limits. Account of a single poster across two posts made about eleven minutes apart, uncorroborated. The screenshots the poster describes were not retrieved. Whether the refund would have been granted on human review is unknown, and the poster's usage of the plan in the minutes after renewal is not stated. Where the poster was is not stated beyond the time zone used for the timeline.

Reported harm

The poster says OpenAI's AI support assistant refused a refund of an unwanted $200 ChatGPT Pro renewal that they requested within minutes, closed the case when they asked for escalation, and that further chat and email requests for a human review produced only AI-generated refusals, leaving them without the $200, a case-specific reason or human review (first-person account, uncorroborated).

Outcome

Ongoing

At the time of the posts the poster had received no refund, no case-specific explanation and no confirmed human review, and was asking other users which official route reaches a human billing specialist. Commenters suggested a bank chargeback, insisting on a human before mentioning a refund, or a mailed demand letter. No response from OpenAI is reported.

What remains unknown

  • Whether the poster was eligible for a refund under OpenAI's discretionary policy, including any usage in the minutes after renewal.
  • Whether any human reviewed or set the refusals, and whether a later human review or bank chargeback recovered the $200.
  • Where the poster lives; the timeline is given in Tbilisi time only.

What the evidence supports

AI involvement: reported. The poster says the Help Center refusals came from an AI assistant and that the email replies were explicitly labelled as generated with AI support; the screenshots they describe were not retrieved. Whether a human reviewed or set the refusal is not known.

4 claims: 4 reported. What the statuses mean

Reported The poster says their ChatGPT Pro plan renewed for $200 on 3 October 2026 after they forgot to cancel, and that they requested a refund in the Help Center about six minutes after the charge.

Causal attribution. Poster's account.

Reported The poster says the Help Center AI assistant declined the refund without a reason specific to their account and, when they asked for escalation, the chat showed the case as closed.

Causal attribution. Poster attributes the refusal to an AI assistant; whether the decision followed fixed policy rules or human configuration is not known.

  • reddit.com(opens in new tab) supports · English
    'The AI declined without giving a reason specific to my account'; 'This case is closed. Create a new case to receive support.'
  • reddit.com(opens in new tab) supports · English
    'The Help Center assistant gave a generic refusal without identifying which eligibility requirement I failed'; 'When I asked for escalation, the case was closed'
Reported The poster says a second chat asking for a human billing specialist produced the same refusal, and that two email requests received refusals marked as AI-generated.

Causal attribution. Poster's account.

  • reddit.com(opens in new tab) supports · English
    'I opened another case specifically requesting a human billing specialist. Same generic refusal.'; 'another refusal arrived, explicitly marked as generated with AI support'; 'That also received an AI-generated refusal'
  • reddit.com(opens in new tab) supports · English
    'A second chat specifically asking for a human produced the same refusal'; 'also received responses explicitly labeled as AI-generated'
Reported The poster acknowledges that the refund policy is discretionary and conditional, says they agreed that refunded access would end, and says they still had no case-specific explanation or confirmed human review.

Causal attribution. Poster's account.

  • reddit.com(opens in new tab) supports · English
    'seven-day discretionary refund policy is conditional, not an automatic entitlement'; 'I still have no explanation specific to my case and no confirmed human review'
  • reddit.com(opens in new tab) supports · English
    'I also explicitly agreed that refunded subscription access would end'; 'I find this an appalling way to treat a paying customer'

Sources

2 sources inspected, from 1 underlying account. Sources that repeat one account do not corroborate each other.

How the sources were read, and where the events happened

Read in English on 2026-10-04: full self-text and the thread's 6 comments (none by the poster), retrieved through the arctic_shift archive API by post ID. The attached screenshots were not retrieved. The poster handle is not recorded. Applies to s1.

Read in English on 2026-10-04: full self-text and the thread's 15 comments (none by the poster), retrieved through the arctic_shift archive API by post ID. Same poster as s1, posted about eleven minutes later and linking s1; not independent. Applies to s2.

Event countries: Unknown. Affected-person countries: Unknown. Court countries: Unknown.

The poster gives their timeline in Tbilisi time (UTC+4) but does not say where they were or live; no country is recorded.

Reviewed for publication 2026-10-04: Published under the 2026-09-15 charter's public-forum rule as a concrete first-person account of an AI support system refusing a refund and blocking escalation to a human, described with attribution and without corroboration. The poster's handle is not recorded.

People described

The poster, a ChatGPT Pro subscriber who requested a refund minutes after an unwanted $200 renewal

People reported harmed in this case

1 person

1 AI participant · 0 other people harmed

One person: the poster. A commenter who says they had the same refund problem is not counted. Exact 1.

Counted once within this case. The same person may appear in other cases. This count does not establish AI causation.

Tags

#first-person#reddit#openai#chatgpt#ai-customer-support#refund#billing#no-human-review

Cite this case

Compiled per our published methodology: verification statuses, sourcing standards, and corrections process.

APA

NOPE. (2026). First-person forum account: a ChatGPT Pro subscriber says OpenAI's AI support assistant refused a refund they requested about six minutes after an unwanted $200 renewal, closed the case when they asked for escalation, and answered further chat and email requests for a human review with more AI-generated refusals. AI incidents. https://nope.net/incidents/2026-openai-ai-support-assistant-refused-chatgpt-pro-refund-requested-minutes-after-renewal-first-person

BibTeX

@misc{2026_openai_ai_support_assistant_refused_chatgpt_pro_refund_requested_minutes_after_renewal_first_person,
  title = {First-person forum account: a ChatGPT Pro subscriber says OpenAI's AI support assistant refused a refund they requested about six minutes after an unwanted \$200 renewal, closed the case when they asked for escalation, and answered further chat and email requests for a human review with more AI-generated refusals},
  author = {NOPE},
  year = {2026},
  howpublished = {AI incidents},
  url = {https://nope.net/incidents/2026-openai-ai-support-assistant-refused-chatgpt-pro-refund-requested-minutes-after-renewal-first-person}
}

Related cases

Medium Unidentified video tool

Bengaluru: a security guard says a WhatsApp video call in which an alleged deepfake 'Chief Minister Vijay' offered him financial aid led to fake 'processing' charges and a fake CBI fine, and he lost more than Rs 1.04 lakh; Byappanahalli police register an IT Act case (September 2026)

A security guard in Bengaluru, originally from Odisha, told the Times of India that on 9 September 2026 he answered a WhatsApp video call in which a face and voice presented as Tamil Nadu Chief Minister C. Joseph Vijay introduced himself in Hindi, asked his name, work and where he lived and pressed him to accept financial help. A 'manager' then promised Rs 11 lakh, said Rs 5 lakh had been allotted to him and asked for a Rs 5,000 exchange charge, then Rs 18,000 to unlock a supposedly locked PIN; a caller posing as a CBI officer demanded more than Rs 50,000 as a fine. The fraudsters sent a fake allotment letter and a purported CBI officer's identity proof. He paid more than Rs 1.04 lakh through a digital payment app before refusing a further Rs 50,000 demand, called the 1930 cybercrime helpline and went to Byappanahalli police, who registered a case under the Information Technology Act. The Times of India says the fraudster allegedly used a deepfake AI-generated video and calls it the first such case reported in the city. No arrest is reported, and no link to the Tamil Nadu CB-CID deepfake case or its Alwar arrest has been established.

Medium Unidentified video tool

India: AI deepfake videos of Tamil Nadu Chief Minister Vijay offering 'financial assistance' were used to defraud people in Madhya Pradesh and other states; a Rajasthan man was arrested

In 2026 AI-generated videos showing a simulated Tamil Nadu Chief Minister C. Joseph Vijay speaking in a fabricated Hindi voice circulated on Facebook and other platforms, urging viewers to contact a WhatsApp number to receive money for education, medical treatment and other needs. The Tamil Nadu Crime Branch-CID detected the videos during routine monitoring, registered a case on 1 September 2026 under the Bharatiya Nyaya Sanhita and the Information Technology Act, and traced the scheme to Rajasthan and Madhya Pradesh. On 12 September a 28-year-old man from Alwar district was arrested with Rajasthan Police, brought to Tamil Nadu on a transit warrant and remanded in judicial custody; a phone, SIM cards and a CPU were seized. Investigators traced a man in Madhya Pradesh who had lost money, and said people in several states were cheated. The CB-CID is also examining similar videos posted from Facebook accounts suspected to be run from Pakistan.

Medium Unidentified voice-cloning tool

Picos, Piauí, Brazil: a digital influencer lost more than R$56,000 when fraudsters sent him audio messages in his uncle's AI-cloned voice 'confirming' a car he was buying in Fortaleza

On Monday 10 August 2026 a digital influencer from Picos, in the centre-south of Piauí, began negotiating a car advertised online for sale in Fortaleza (Ceará), where an uncle of his lives, and asked the sellers to take the car to the uncle so he could inspect it. On Tuesday 11 August a contact using a different number but the uncle's photo sent him audio messages in a voice identical to his uncle's, generated with artificial intelligence, saying the car was in good condition and telling him to make the bank transfer. Believing he was speaking to his uncle, he transferred the money; when he then called the uncle's real number he learned he had been defrauded. The loss exceeded R$56,000, money he says he had saved for years. He registered a police report on 11 August; the Piauí property-crimes unit (Depatri) is investigating and he is seeking a refund from the banks. The account is the victim's own, reported by G1 Piauí on 13 August 2026 from his social-media posts and an interview; the police unit did not respond to G1 before publication.

Medium Unidentified video tool

Kazakhstan: the Prosecutor General's Office reported 119 trading-fraud cases registered in about six weeks, lured by deepfake videos of Elon Musk, Pavel Durov and other public figures and fake 'AI' platforms; a Taldykorgan woman transferred more than 7 million tenge

On 16 September 2026 the Prosecutor General's Office of Kazakhstan warned of an investment-fraud scheme in which criminals advertise non-existent projects on TikTok, Instagram, YouTube and other platforms using deepfake videos of well-known people and fake 'AI' investment platforms promising very high passive income: 'Kaspi AI' with Mikhail Lomtadze, 'Quantum AI' with Elon Musk, 'TON' with Pavel Durov, and 'people's investments' in KazMunayGas or Gazprom fronted by news presenters from Khabar 24, KTK and Channel One. The office said 119 such cases had been registered across the country in the previous one and a half months. Its example: in September 2026 a woman from Taldykorgan saw an Instagram advertisement offering high returns from share trading, left her details through the link, was contacted by the fraudsters and, following their instructions, transferred more than 7 million tenge to third-party accounts; the money and supposed dividends appeared in a fake wallet that she could not withdraw from. A pre-trial investigation is under way. The office urged people not to trust guaranteed-return offers or transfer money to strangers.

If you or someone you know is struggling, free and confidential support is available. Find a helpline near you at Signpost.

Back to all incidents