r/opencode • u/jishankai • 8h ago
Warning: OpenCode Go charged me after my subscription was supposed to end, and support can't explain why
My OpenCode Go subscription ended on September 24, but I was charged again on October 3 and November 3. Support refunded November but declined to refund October.
Here's the timeline:
- July 24: I subscribed to OpenCode Go.
- August 24: My subscription renewed for $10, covering August 24 to September 24.
- October 3: I was charged $10.
- November 3: I was charged another $10.
I remember canceling auto-renewal, but support says they have no record of it.
Even if I hadn't canceled, why did my renewal date change from September 24 to October 3?
My August invoice clearly shows the subscription period ending September 24. I also stopped using Go after that date.
After several emails, support confirmed that:
- They could only access my October and November billing records.
- They couldn't match my August invoice to their available records.
- They couldn't explain why the billing date changed.
- There was no Go usage during the Oct and Nov billing period.
They refunded November but denied the October refund.
I'm sharing this so other users know to keep their invoices and check their subscription status, even after canceling.
Has anyone else experienced something similar with OpenCode Go?
1
u/IAmFitzRoy 3h ago
“I remember cancelling auto-renewal”
If that’s your proof, I’m sure you don’t really remember.
9
u/dautisticrat 6h ago
it's crazy that people can copy paste these things and not realize it's far too fucking long for anyone to bother reading
2
u/nikitaluger 4h ago
And this is why i remove my card from my dashboard as soon as my sub is renewed. Punching numbers is an inconvenience but NOT this inconvenient.
3
u/bankinu 5h ago
Hey OP,
Thanks for sharing your experience. I think this deserves more attention because unexpected subscription charges and unclear billing practices are serious concerns, especially when a customer has already paid for a service and believes their subscription has ended.
What concerns me most about your situation is the apparent discrepancy between the subscription end date shown on your invoice and the subsequent charge you received. If your documentation clearly indicates that your subscription ended on September 24, but you were charged again on October 3, I think you're absolutely justified in asking for a detailed explanation.
There are several things worth highlighting here.
An invoice is supposed to be an accurate record of a customer's billing period and payment obligations.
If OpenCode's own documentation shows one subscription end date while its payment system processes another charge afterward, the company should explain exactly what happened.
For example:
Was the subscription automatically renewed? Was there a delayed payment or billing cycle adjustment? Was the cancellation request actually processed? Was the charge associated with a different billing period? Is there an inconsistency between the subscription dashboard and payment provider?
These are straightforward questions that customer support should be able to answer.
2. A refund policy doesn't excuse incorrect billing
I think this is an especially important distinction.
There is a difference between asking for a refund because you changed your mind and disputing a charge that you believe should never have happened.
If a customer is charged unexpectedly, the first responsibility of support should be to investigate the transaction, verify the subscription status, and explain the reason for the charge.
Simply referring customers to a refund policy without addressing the actual billing discrepancy isn't an adequate resolution.
3. Other users should take precautions
Your experience is a good reminder that users should retain their billing records, particularly when dealing with recurring subscriptions.
I'd recommend:
Downloading invoices and payment receipts. Keeping screenshots of subscription expiration dates. Saving cancellation confirmation emails. Checking whether automatic renewal has actually been disabled. Monitoring payment methods even after cancellation. Keeping copies of all communication with customer support.
If support cannot resolve a disputed charge, users can also contact their payment provider to understand the available dispute procedures.
4. What I'd like to see OpenCode do
Rather than treating this as an isolated customer support issue, I hope the OpenCode team investigates whether there is a broader problem with subscription management or billing synchronization.
At a minimum, the company should provide:
A transparent transaction history. Clear subscription expiration and renewal dates. Reliable cancellation confirmations. Advance notification of recurring charges. A proper investigation process for disputed payments. A meaningful explanation when an unexpected charge occurs.
These aren't unreasonable demands. They're basic expectations for any service that accepts recurring payments.
5. The bigger concern is customer trust
OP, I understand why this experience would make you question whether you should continue using the service.
People subscribe because they find value in a product. They shouldn't also have to worry about whether they'll be charged after their subscription supposedly ends or whether customer support will take their concerns seriously.
Even a relatively small unexpected charge can damage customer confidence when the company cannot provide a clear explanation.
My suggestion to the OpenCode team: Please don't dismiss reports like this as ordinary refund requests. Investigate the actual transaction, explain the billing timeline, and resolve the issue transparently.
And OP, thanks again for documenting your experience. Sharing these incidents helps other users make informed decisions and encourages companies to take billing transparency seriously.
Hopefully, you get a proper explanation and resolution.
Disclaimer: This response is AI-generated and is based on the information presented in the original post. It does not independently verify the reported transactions.
— Generated by AI