How to Pay for GitHub Copilot in 2026: Plans, Card Rules, Virtual Cards

2026-11-12 / Kenneth Lau / 6 min read

Filed: Cross-Border Payments
First run: 2026-11-12
Length: 1367 words

How to Pay for GitHub Copilot in 2026: Plans, Card Rules, Virtual Cards

GitHub Copilot's pricing page is easy reading. The payment part is not. The official plans page gives you a free tier that asks for no card at all, and paid tiers starting at $10 a month. Meanwhile, buried in GitHub's billing documentation, sits one sentence that decides whether your card will ever work: prepaid credit and debit cards are not accepted. That single line knocks out a large share of the virtual cards people buy specifically for overseas subscriptions. This guide walks through the plans, the payment rules, and where virtual cards actually stand — everything official was checked against GitHub's own pages on November 13, 2026, and anything from community reports is labeled as such.

The plans and what your money buys

Individual accounts get four tiers plus a free student path. Straight from the pricing page:

Plan	Price	Monthly AI credits	What stands out
Free	$0	Small allowance	2,000 completions/month, Copilot CLI, no credit card required
Pro	$10/user/mo	$15	Unlimited completions, cloud Copilot and code review, third-party agents (Claude Code, Codex), model selection
Pro+	$39/user/mo	$70	Premium models including Opus, audit logs, 4x+ usage vs Pro
Max	$100/user/mo	$200	Priority access to new models, 2.9x+ usage vs Pro+

One thing worth understanding before you pay: the credits. Agent mode, code review, the cloud agent, and the CLI all draw from a shared pool of GitHub AI Credits, and GitHub explicitly says flex allotments can change over time. Translation: heavy agent users should budget by consumption, not by sticker price. On the organizational side, GitHub's banner now says GitHub Enterprise includes Copilot access, and enterprises settle seats through Billing & Licensing with more options than individuals get (invoices, Azure subscriptions). This article sticks to personal accounts.

What GitHub officially accepts

Per Supported payment methods for GitHub, checked November 13, 2026: personal accounts pay by credit card or PayPal. Azure subscription IDs aren't available for personal accounts; invoices and ACH are managed-account territory. A detail that matters if you read older tutorials: Copilot standalone accounts, which historically required an Azure subscription, can now be paid by credit card too.

And the line in the same document that kills most prepaid setups: prepaid credit and debit cards are not accepted as a valid form of payment. Written policy, not a rumor.

The prepaid wall, and where virtual cards hit it

Here's the practical translation. Rejection happens at two layers. The first is card classification: anything the issuer registers as prepaid hits GitHub's written rule head-on. The second layer is risk control — GitHub processes payments through Stripe, which weighs the card's BIN, billing address consistency, and the merchant's fraud rules. Virtual cards issued in credit-card form with clean, matching records are not named in any exclusion and do get through. But GitHub has never promised to accept virtual cards either, so treat "it worked once" and "it will work for you" as different claims.

Community reports (unverified): through 2026, GitHub Community discussions and Reddit threads describe prepaid and virtual cards being declined specifically on Copilot's recurring billing. One recurring complaint: the same card still clears one-time purchases while Copilot's subscription charge fails, and after three failed attempts the subscription cancels outright, forcing a fresh checkout. Plausible, repeatedly reported, and nowhere confirmed by GitHub — that's exactly why it stays in the community bucket.

Checkout mechanics: the hold and the activate button

The most common confusion goes like this: you see a small charge hit the card, then Copilot stays on the free plan. The official getting-started doc explains both failure modes. During checkout, GitHub may place a temporary authorization hold to verify your payment method — it is not the subscription charge. And if verification fails, or you never click the final "Activate Copilot Pro/Pro+/Max" button, the plan simply doesn't activate. If you paid and still see Free, check Billing & Licensing for the plan status, then redo the checkout if needed.

Practical corollary (community guidance): don't load your card with exactly $10. A verification hold stacked on the first month's charge can trip an insufficient-funds decline when the balance hugs the subscription price. Keep a few dollars of headroom.

When the charge fails: retries, grace, and lockouts

GitHub's own declined-card troubleshooting is surprisingly specific. First, check the card's expiry and update it. Second, ask your bank whether it restricts international, e-commerce, or automatically recurring transactions — plenty of banks ship with those switched off by default, and that's a five-minute fix on the bank's end, not GitHub's. Third, if the card is fine, call the bank with the merchant name (GitHub), the transaction ID, and the billing date from your receipt. PayPal works as the fallback, and a PayPal error 10417 just means the funding source failed — switch to another card or balance in the wallet and retry.

Let it slide, though, and the meter runs. Per the locked-account documentation, past-due accounts get their paid features locked; paying unlocks them again without back-charging the locked period. Remove your payment method while subscribed and the subscription auto-cancels at the next renewal date. Community accounts of the end state: repeated failed charges eventually drop you back to the Free tier — repos intact, usage and models trimmed.

AVS and 3DS: the two invisible checkpoints

Stripe runs Address Verification. The country, state, and ZIP you enter in GitHub's billing profile need to match what the issuing bank has on file. Mismatched geography — a US-issued virtual card paired with your local home address — is among the most reported decline causes in community threads (unverified, but consistently reported). The second checkpoint is 3D Secure: if checkout throws an OTP challenge, the code has a short shelf life, so make sure you can receive the prompt before you hit submit.

The student path is free

If you have a verifiable academic identity, don't pay at all. The pricing page states that verified students get the GitHub Copilot Student plan — complete GitHub Education verification and the $10 tier drops to $0, no card attached. It beats wrestling any card through Stripe.

FAQ

Does the free plan need a card?

No. The official page marks the Free tier "No credit card required" — 2,000 monthly completions and the CLI work out of the box.

Can I pay with a prepaid or gift card?

No. GitHub's payment methods documentation states prepaid credit and debit cards are not accepted. That's policy, not risk-engine bad luck.

Will every virtual card be rejected?

No, and that's the nuance. Prepaid-form cards sit inside the written exclusion; credit-card-form virtual cards with consistent AVS details have a real track record. GitHub promises nothing, so plan for the decline case.

My charge was declined — does the subscription vanish instantly?

No. GitHub emails the reason, allows a few days to fix it, then retries. Continued failure locks paid features (recoverable by paying) or drops you to Free.

Is PayPal an option?

Yes, for personal accounts, officially listed alongside credit cards. If PayPal fails with error 10417, change the funding source and retry.

Is there an annual discount?

The official pricing page checked here lists monthly billing only. Annual prices circulating on third-party sites are unverified — don't budget around them.

Risks and limits

Everything here was verified on November 13, 2026. Plan structure, credit allowances, and flex allotments can change — GitHub says so explicitly — so confirm against the live pages before you commit.
Virtual cards carry genuine rejection and subscription-cancellation risk on GitHub, prepaid-form cards especially. Don't bind cards of unclear provenance to accounts holding your code.
AVS behavior, 3DS timing, and retry cadence come from community reports and are labeled unverified; your own checkout flow is the final authority.
The prepaid-card exclusion is a written GitHub policy. Quote it as fact, not as "sometimes enforced."

Official sources (checked November 13, 2026)

阅读中文版