What exactly is the GITHUB* charge on my bank statement?

The GITHUB* charge is a billing descriptor used by GitHub when processing payments for paid plans such as GitHub Pro, GitHub Team, GitHub Copilot, or GitHub Enterprise through their payment processor.

Why does the charge say GITHUB* instead of just 'GitHub'?

The 'GITHUB*' format with an asterisk is how GitHub's payment processor (Stripe) formats the merchant name on card statements. It may also include a suffix like 'GITHUB*COM' or 'GITHUB*COPILOT' depending on the product billed.

Can I get a refund for a GITHUB* charge?

GitHub offers refunds on a case-by-case basis. If you were charged in error or forgot to cancel before renewal, contact GitHub Support at support.github.com — they often provide a prorated refund for unused subscription time.

How do I cancel my GitHub subscription to stop GITHUB* charges?

Log into GitHub, go to Settings > Billing and Plans, and click 'Downgrade to Free'. For organization plans, visit your org's Billing settings. Cancellation stops future GITHUB* charges at the end of the current billing period.

How do I stop future GITHUB* charges if I no longer use GitHub?

Downgrade your account to the free GitHub tier, which has no subscription cost. Then remove your saved payment method in Settings > Billing to ensure no future GITHUB* charges can be processed.

Home›Browse Charges›SaaS›GITHUB*

GITHUB* Charge (What It Is + Is It Legit?)

✓ Legitimate

The "GITHUB*" charge is from GitHub. GitHub Pro or Teams subscription.

🌍 US🕐 7 min read📅 Updated May 22, 2026

GitHub

GitHub Pro or Teams subscription.

GITHUB*

Why does this charge appear?

GitHub processes its subscription payments through Stripe, one of the most widely used payment processors in the software industry, which automatically truncates merchant names to fit within the standard 22-character limit imposed by card networks like Visa and Mastercard. Because GitHub's billing system identifies the merchant with an asterisk-separated format, the descriptor becomes "GITHUB*" followed by additional transaction details, rather than displaying the full company name. If you see this on your statement alongside a charge of around $4.00 per month, it almost certainly relates to a GitHub Pro individual plan or a GitHub Teams workspace subscription billed through your account at github.com.

🛡️

Got a suspicious message or link?

Free

Detect scams in seconds — texts, emails, websites & more, instant results.

🛡️ Check for Scam →

✅

Your next steps

Identify Your GitHub Plan

Log into your account at github.com and navigate to your profile settings to confirm whether you are subscribed to GitHub Pro or a GitHub Teams plan, both of which would generate a GITHUB* charge on your bank statement.

Review Your Billing History

Visit github.com/settings/billing to view your full billing history and confirm that the GITHUB* charge amount matches your current GitHub subscription plan pricing and billing cycle date.

Check for Multiple GitHub Seats

If your organization uses GitHub Teams, go to github.com/settings/billing and verify the number of paid seats on your account, as the GITHUB* charge may reflect multiple user seats that have been added over time.

Cancel or Downgrade if Needed

If you no longer need the GitHub Pro or Teams subscription that is generating the GITHUB* charge, go directly to github.com/settings/billing to downgrade to the free plan or cancel your paid subscription to stop future charges.

🔓

How to cancel GitHub

GitHub bills you Monthly. To stop future charges, cancel from your account directly.

Cancel at GitHub

🛡

Legitimate or scam?

No, this is a legitimate charge from GitHub. However, if you did not authorize this charge or cancelled your subscription, you may be eligible for a refund.

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.

ℹ️ 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.