GitHub Community
Accidentally used code security and other advanced licenses and got charged #207494
🏷️ Discussion TypeQuestion 💬 Feature/Topic AreaCode quality Discussion DetailsGithub support is not responding for tickets: #4702588 and #4720687 even though I am a pro plan user. approximately $68 for GitHub Advanced Security and $20 for Code Quality. We are an early-stage startup and did not realize enabling these features would result in paid license charges. We did not intentionally intend to subscribe to paid services, and I disabled the features as soon as I discovered the associated costs. Could you please review these charges and waive or refund the pending $88 amount as a one-time courtesy? These costs were unintentional and are significant for us at our current stage. |
Replies: 2 comments
|
Only GitHub Billing Support can review or reverse those charges, so the Community forum cannot approve a refund. Keep the request on the existing ticket and make sure it was submitted by an organization owner or billing manager. Include the invoice or billing-period details, the exact features and dates they were enabled, and when they were disabled, but do not post payment details or private ticket content publicly. Also check the organization billing settings and audit log to confirm which repository or organization enabled the features, and remove any remaining Advanced Security or Code Quality seats. Ask Support to confirm whether the amount is pending authorization or an actual invoice charge; the resolution can differ. |
|
Hi @Nanda-Kiran — community cannot process refunds, but here is how to stop billing and strengthen your ticket: Disable nowSettings → Code security and analysis → turn OFF GHAS, Code Quality, and related paid features. Refund ticketReply on #4702588 / #4720687 with:
GHAS bills per active committer on private repos — easy to miss in setup wizard. Set billing spending alerts and restrict admin/billing access to prevent recurrence. |
Only GitHub Billing Support can review or reverse those charges, so the Community forum cannot approve a refund. Keep the request on the existing ticket and make sure it was submitted by an organization owner or billing manager. Include the invoice or billing-period details, the exact features and dates they were enabled, and when they were disabled, but do not post payment details or private ticket content publicly.
Also check the organization billing settings and audit log to confirm which repository or organization enabled the features, and remove any remaining Advanced Security or Code Quality seats. Ask Support to confirm whether the amount is pending authorization or an actual invoi…