Charged $50 for Copilot Pro with zero usage – 3 weeks, no response from GitHub Support (Tickets #4100811, #4100862)

[excaliburnet]

Select Topic Area

Question

Body

Billing Issue – $50 Charge for Copilot Pro with Zero Usage, No Support Response in 3 Weeks

I'm posting this publicly because GitHub Support has completely ignored my tickets for over 3 weeks.

What happened

On January 20, 2026, GitHub charged me $50.00 for GitHub Copilot Pro (Invoice ID: H261502B). I had zero usage of Copilot Pro during that billing period, as confirmed by my billing dashboard.

What I've done

I have submitted 3 support tickets requesting a refund:

• #4100811 – Refund request ($50, zero usage) – Status: Open, created Feb 20, 2026 – no response
• • #4100862 – Refund request ($49.50 overcharge) – Status: Archived – no response
• • #4121041 – Escalation ticket – Status: Archived – no response
    All three tickets have been ignored. The last update on any of them was March 10, 2026, with no reply from GitHub staff.

What I'm asking

1. Has anyone else experienced this kind of billing issue with Copilot Pro?
2. 2. Is there any other way to reach GitHub Billing support that actually works?
3. 3. Does anyone know of a direct contact or escalation path?
      This is a clear billing error and the complete lack of response from GitHub Support is unacceptable. I will be filing a chargeback with my bank if this is not resolved.

Any help or advice from the community or GitHub staff would be greatly appreciated.

[Rajveer-code]

Yeah, I’ve seen similar confusion around this, so just sharing what I’ve learned.

Copilot Pro is subscription-based, not usage-based. So even if you didn’t use it at all during that period, you’ll still get charged if the subscription was active when the billing cycle renewed. It catches a lot of people off guard.

The key thing to check is when you canceled (if you did):

If cancellation happened after the renewal date → you still get billed for that cycle
If it was canceled before → then yeah, that’s worth pushing harder with support

Also worth double-checking:

Whether Copilot was enabled via another account or org
If the billing cycle date aligns with Jan 20

On the support side — 3 weeks with no reply is honestly not normal.

What’s worked better in my experience:

Don’t open new tickets → reply to the same one so it stays active
Try the billing-specific support option (not general support)
If you’re in an org, have the admin raise it — those sometimes get faster responses

About chargeback — I get the frustration, but just be careful:
GitHub can lock or limit your account if a chargeback goes through. It’s usually better as a last option.

If everything checks out and you really had it canceled before billing, then yeah, I’d keep pushing — this is one of those cases where it’s probably just stuck in their queue rather than being ignored intentionally.

Hope you get it sorted soon 👍

[alex-gamero]

Oh man, three weeks with no response and tickets getting archived sounds frustrating, especially with a clear paper trail as you have.

One thing worth trying, tweet/post at @githubsupport directly and reference your ticket numbers publicly. It sounds petty, but billing complaints with specific invoice IDs tend to get picked up faster that way than sitting in a queue.

Also, if you have a GitHub Education or any org affiliation, have whoever manages that account raise it separately, org-level billing tickets do seem to get prioritized differently.

Rajveer's point about chargebacks is worth taking seriously though. If you do go that route, make sure you've documented everything first, screenshots of zero usage, the invoice, the ticket numbers and dates. That way if GitHub does push back you have a clean record showing you made every reasonable attempt to resolve it first.

[KL2300030695]

This looks like two separate issues — billing behavior and support delay.

1. About the $50 charge
   Copilot Pro is subscription-based, not usage-based. So even with zero usage, you’ll still be charged if the subscription renewed on Jan 20, 2026.
   That said, this becomes a valid refund case if:

You canceled before the renewal date
The subscription was never intentionally activated
The amount charged doesn’t match your plan/region

2. No response from support (main concern)
   3+ weeks with no reply is definitely not normal for billing tickets.

Things that usually help:

Reply to the same ticket instead of opening new ones (keeps it active)
Clearly mention: “Requesting escalation – no response for 3 weeks”
Tag @githubsupport on X/Twitter with ticket + invoice IDs (this often speeds things up)
If this is tied to an org, ask the org admin to raise the issue

3. About chargeback
   Understandable, but use it as a last resort — GitHub may restrict your account if a chargeback is initiated.

[krillmango]

found the engineer

[ajx-dev]

Yeah, I actually ran into something similar with GitHub billing before. Their support can be really slow sometimes, especially with Copilot stuff.

Honestly, waiting 3 weeks with no response is not normal. At this point, I’d suggest a couple things:
• Try replying to one of your existing tickets instead of opening new ones (sometimes that bumps it up).
• If you have Twitter/X, try tagging @githubsupport — people have had better luck getting attention there.
• Also double check if the charge was from an auto-renewal, because even with zero usage they still bill if the subscription is active.

That said, if they’re still ignoring you after all that, going for a chargeback is completely fair.

Hope you get this sorted, that’s super frustrating.

[krillmango]

a virtual financial instrument allows you to set a spending cap. any merchant rejecting is SHADY

such a tool is usually associated with a bank account like wise.com or privacy.com

there are others