Why You're Seeing "GITHUB*" on Your Bank Statement
Why You're Seeing "GITHUB*" on Your Bank Statement
A charge showing GITHUB* on your bank statement comes from GitHub, the world's leading software development and version control platform owned by Microsoft. This charge typically represents a paid subscription to GitHub Pro (for individual developers) or GitHub Teams (for organizations), which unlock advanced features beyond the free tier. You may see this charge monthly or annually depending on the billing cycle you chose when upgrading your account. If you don't recognize it, it's worth checking whether a team member, employee, or someone with access to your payment method set up a GitHub subscription.
The descriptor GITHUB* appears on your bank statement because GitHub uses a truncated billing identifier that payment processors display in place of the full company name. The asterisk following 'GITHUB' is a common formatting convention used by many SaaS companies to separate the brand name from additional billing detail, though in this case the descriptor keeps it brief. This is the standard way GitHub's charges are reported across most major banks and credit card providers in the United States.
Is the GITHUB* Charge Legitimate or Fraud?
A GITHUB* charge on your bank or credit card statement is almost always a legitimate billing from GitHub, the world's leading software development and version control platform owned by Microsoft. This charge typically appears when you subscribe to GitHub Pro, GitHub Team, GitHub Enterprise, or GitHub Copilot. Common reasons you might see a GITHUB* charge include:
- A monthly or annual subscription to GitHub Pro (~$4/month)
- A GitHub Team plan for your organization (~$4/user/month)
- A GitHub Copilot AI coding assistant subscription (~$10â$19/month)
- A GitHub Enterprise plan billed to your company account
How to Verify the GITHUB* Charge
- 1
Log into your GitHub account
Visit github.com and sign in. Navigate to Settings > Billing and Plans to view your current plan, pricing, and recent payment history to confirm the GITHUB* charge.
- 2
Search your email for GitHub receipts
Search your inbox for emails from 'noreply@github.com' or 'billing@github.com'. GitHub sends a receipt for every charge, which should match the GITHUB* amount on your statement.
- 3
Check if a household member signed up
Ask family members or colleagues if they used your card to sign up for GitHub Pro, GitHub Copilot, or a GitHub organization plan, as these all appear as GITHUB* on statements.
- 4
Review your GitHub organization memberships
If you belong to a GitHub organization, check if you're an owner responsible for billing. Go to your organization's Settings > Billing to see active subscriptions generating GITHUB* charges.
- 5
Contact your bank if still unsure
If you cannot match the GITHUB* charge to any GitHub account activity, call the number on the back of your card. Your bank can provide the exact merchant details and transaction date.
How to Dispute a GITHUB* Charge
- 1
Act within 60 days of the charge
Most banks require you to dispute unauthorized charges within 60 days of the statement date. Don't delay if you believe the GITHUB* charge is fraudulent or made in error.
- 2
Contact GitHub Support first
Visit github.com/contact or support.github.com to reach GitHub's billing team. GitHub is generally responsive and may issue a refund directly, which is faster than a bank chargeback for GITHUB* charges.
- 3
File a chargeback with your bank
If GitHub does not resolve the issue, contact your bank or card issuer to dispute the GITHUB* charge. Provide your GitHub account details and any correspondence with GitHub Support as evidence.
- 4
Request a new card number
If you believe the GITHUB* charge is the result of fraud or unauthorized card use, ask your bank to issue a replacement card to prevent any further unauthorized charges from GitHub or other merchants.
Tips for Managing GitHub Charges
Enable GitHub billing email alerts so you're notified before each GITHUB* charge hits your card.
Review your GitHub Billing page monthly to track all active plans and seats generating GITHUB* charges.
Secure your GitHub account with two-factor authentication to prevent unauthorized plan upgrades.
Switch to an annual GitHub plan to save up to 17% and reduce the number of GITHUB* charges per year.
Use a virtual card number for your GitHub subscription to isolate GITHUB* charges and simplify disputes.
Use WhatIsThisCharge.net to identify other unfamiliar charges that may appear alongside GITHUB* on your statement.
Frequently Asked Questions About the GITHUB* Charge
âšī¸ Note
In most cases, a GITHUB* charge is a routine, expected billing from GitHub for a paid developer plan like GitHub Pro or GitHub Copilot â if you or a team member uses GitHub for coding, this charge is almost certainly legitimate and easy to verify in seconds through your GitHub billing settings.
đ Decode this charge instantly
Search our database for GITHUB* and similar charges.
Decode GITHUB* âWas this article helpful?