URGENT: Double Charge for Copilot - No response on Ticket #4299184 for 2 weeks

[shai102]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Account Related

Body

Hi GitHub Community and Staff,

I am writing to seek assistance with a billing issue that has remained unresolved for two weeks.

On April 17th, 2026, I was accidentally double-charged for my GitHub Copilot Pro subscription. I mistakenly cancelled my initial subscription and immediately re-subscribed, which resulted in two separate charges of $10.00.

I submitted a support ticket (#4299184) on the same day, but I have not received a response from a human agent, even after sending a follow-up "ping" last week.

Details for the refund:

Ticket ID: #4299184

Transaction ID to be REFUNDED: 1ZX0J07E

Transaction ID to KEEP: 1THXHSYK

Could a staff member please look into this or escalate the ticket? I just want to get the redundant charge refunded.

Thank you for your time and help!

[rpvq]

hello

[Hxni786]

Hi,

This type of issue is usually handled directly by GitHub Support rather than the community, so only their billing team can process the refund.

Since you’ve already submitted a ticket, the best course is to wait for their response. Delays of 1–2+ weeks can happen depending on workload. Avoid creating duplicate tickets, as that can slow things down further.

If there’s still no reply after some more time, you can follow up again on the same ticket or try reaching out via official GitHub Support channels.

In the meantime, your request and details look correct, so it should be resolved once a support agent reviews it.

[rpvq]

Brothers, I have a problem with the warehouse. Stockfish-awa
Everything I try to create for him
Every time I try to add two archives
It cleans but doesn't show
Warehouse supervisors' accounts
Of course, this warehouse doesn't belong to me.
I copied it to my account and edited it.

[Gecko51]

The community can't process refunds directly, that has to go through GitHub's billing team. Since two weeks have passed with no response, here are some things that have worked for others in similar situations:

First, try re-opening the issue via support.github.com and select Billing as the topic. Reference ticket #4299184 explicitly in your message and mark it as a follow-up. Billing tickets sometimes get routed faster than general support queues.

Second, reaching out to @githubsupport on X (formerly Twitter) has historically gotten quicker attention for account-related billing issues. A short public message referencing your ticket number tends to get picked up.

One thing to consider: your transaction IDs are now publicly visible in this thread. On their own they're not sensitive credentials, but you may want to edit your original post to remove them once the issue is resolved, just as a cleanup step.

Hang in there, the refund should be straightforward once a billing agent actually reviews the ticket.