REFUND GUIDE

How to Get a GitHub Copilot Refund After Renewal.

Here's what GitHub actually owes you, what their policy quietly says, and how to escalate if they ignore the request.

Last verified 15 Jun 2026 against GitHub’s own Terms · UK, US, and EU rights covered below

The short answer

GitHub's default position is that cancellation stops future billing but does not refund the remainder of the current cycle, you keep access until the period you've already paid for ends. Exceptions exist: if your Copilot personal plan is replaced by a Business/Enterprise seat you get a prorated refund automatically, and during the April, May 2026 Copilot plan changes GitHub offered a Cancel-and-refund button in Billing settings. For one-off refunds (unused months, billing errors, accidental renewals) open a ticket at support.github.com/contact under Billing & Payments; consumer-law refunds (UK/EU 14-day right of withdrawal) apply if you have not used the service.

Or let yoink chase the refund.

30 seconds to set up. yoink emails GitHub, cites the policy, escalates if ignored, and surfaces the win when the money lands.

Get yoink (App Store) →

What GitHub actually says

No refunds are issued for unused time in the current cycle.

, verbatim from GitHub’s terms
Pro-rata refund: noStatutory cooling-off: 14 days in UK + EU on new subs

How long does a GitHub refund take?

Most merchants agree to a straightforward refund within 1 to 3 working days of a well-written email request. Once agreed, the money itself takes another 3 to 5 working days to land, that part is card-network processing and no merchant can skip it. If nothing has arrived 10 working days after a written “refund approved”, reply on the same thread asking for the ARN (acquirer reference number), which your bank can trace.

What you can claim

The law where you live is the strongest hook, lead with it when you contact the company.

United States

  • Fair Credit Billing Act (FCBA)
    Dispute any credit-card charge in writing within 60 days.

    For US credit-card payments, the FCBA gives you 60 days from the statement date to dispute a GitHub charge in writing. Your card issuer is required to investigate and may withhold the disputed amount during the process.

  • California ARL refund right
    Refund if cancel was blocked or unclear.

    If GitHub made it hard to cancel under California ARL, you’re entitled to a refund of charges taken since the obstruction. Multiple class actions (including against Adobe + Hulu) have set the precedent.

Worldwide

  • Card-issuer chargeback
    Visa/Mastercard chargeback works everywhere they do.

    Open a chargeback for “subscription not cancelled” or “services not as described”, your bank initiates, GitHub has ~45 days to defend. Works regardless of where GitHub is headquartered.

  • PayPal Buyer Protection
    If you paid via PayPal, open a dispute.

    PayPal’s Buyer Protection covers “item not as described”, applies to services that didn’t deliver. Resolution typically within 20 days.

Rights in other regions (United Kingdom, European Union)

United Kingdom

  • Section 75, Consumer Credit Act
    Credit card issuer is jointly liable. £100-£30,000.

    For UK credit-card charges between £100 and £30,000, your card issuer is jointly liable with GitHub for any breach. Call your bank, say “Section 75 claim”, send evidence. Usually resolved in 2-4 weeks.

  • Consumer Contracts Regulations 2013
    Full refund within the 14-day window.

    Inside 14 days of starting any GitHub subscription, you’re entitled to a full refund of any payment taken, no questions, no policy override.

  • Citizens Advice + Trading Standards
    For repeated bad-faith refusals.

    Free escalation lane: file with Citizens Advice (08082231133), they pass it to Trading Standards. Slow (8-12 weeks) but creates a paper trail GitHub can’t ignore.

European Union

  • Consumer Rights Directive 2011/83/EU
    14-day withdrawal across all EU member states.

    EU-wide statutory right to withdraw and recover any payment within 14 days of subscription start. Mirrored in local law in every EU country.

  • ECC-Net cross-border escalation
    EU Consumer Centre network mediates against EU sellers.

    If GitHub is based in another EU country, your local European Consumer Centre will mediate the dispute for free. List of national contacts at commission.europa.eu.

The 4-step refund email

  1. Email the right address

    Use support@github.com, the route yoink has verified actually gets read for GitHub.

  2. Use a clear subject line

    Subject: Refund Request, [your account email]

  3. Send this body

    Hi GitHub team,
    
    I'm requesting a refund of the recent charge on my subscription, account [your account email].
    
    Under the FTC's Click-to-Cancel rule, cancellation must be available through a channel as simple as the one I signed up through. Please confirm by reply that the refund will be processed to my original payment method.
    
    Best,
    [your name]
  4. Wait 7-14 days, then escalate

    If you haven’t heard back in 14 days, escalate via the regional route above, a card-issuer chargeback works in every market.

Refund FAQ for GitHub

Go to **Settings → Billing & licensing → Licensing**, find the **GitHub Copilot** section, click **Manage subscription → Cancel subscription**, then confirm. You'll keep access until the end of the current billing cycle. For a refund of the unused time, you have to open a separate ticket at https://support.github.com/contact → **Billing & Payments → Copilot → Cancellation**. The virtual agent can sometimes refund immediately; otherwise escalate to a human. Annual plans are easier to refund (prorated remainder) than monthly.

Cancelling rather than claiming money back? See the GitHub cancellation guide. For every other support channel, the GitHub contact guide.

Other refund guides.

Tired of asking nicely?

yoink emails GitHub, escalates if ignored, and chases until the refund lands. You approve once. We do the rest.

Get yoink for free →