GitHub Copilot comes in a personal tier, Pro, a higher personal tier, Pro+, and organisation tiers, Business and Enterprise. All are billed by GitHub to a card on the account or the organisation, and GitHub does not accept crypto. Developers paid in USDT, teams in countries where GitHub rejects local cards, and companies that keep treasury in stablecoins all end up at the same solution: a crypto-funded Visa or Mastercard on the GitHub billing page. This guide shows where that card goes for each tier, how overage billing works, and how to fix declines.

Personal or organisation billing

  • Copilot Pro and Pro+: billed to your personal GitHub account under Settings, Billing and plans, Payment information. Monthly or annual.
  • Copilot Business and Enterprise: billed to the organisation under the organisation's Settings, Billing, per assigned seat, monthly in arrears.
  • Premium requests: usage above the included quota is billed per request to the same payment method if you enable a budget.

A personal card pays for Pro; an organisation card pays for every seat in Business. The same IZIPAY card can be used in both places, but teams usually prefer one card per organisation.

Step by step for Copilot Pro

  1. Register with IZIPAY, choose a virtual Visa or Mastercard, pay $49.99 in USDT, BTC or USDC. The card is ready in about two minutes.
  2. Top up with USDT on TRC20. Load the plan price plus a few dollars for the authorisation hold.
  3. On github.com open Settings, Billing and plans, Payment information, Add payment method. Enter the card and a US billing address with a valid ZIP to match the US BIN.
  4. Open Copilot in the same Billing section, choose Pro or Pro+, monthly or annual, and confirm. Copilot activates in your editor within minutes.

GitHub emails a receipt for every charge and keeps invoices under Billing history for accounting.

Copilot Business for a team

In the organisation's Billing settings add the crypto card as the payment method, then enable Copilot and assign seats. GitHub charges seats monthly in arrears, so the card must hold roughly the number of seats times the seat price at the start of each month. Set a spending limit for premium requests so an unexpected usage spike cannot drain the card.

Why GitHub declines a card and how to fix it

  • Card declined: balance below the plan price plus hold, or below seats times price for organisations. Top up with a buffer.
  • Billing address mismatch: use a US address with a valid ZIP.
  • Card not accepted: try the other brand. IZIPAY issues both Visa and Mastercard.
  • Payment failed and Copilot was disabled: GitHub retries for several days. Top up and click Retry payment in Billing; access resumes immediately.
  • Sanctions or region block on the GitHub account: a card does not change GitHub's own account restrictions; check the account status first.

What a year of Copilot costs through a crypto card

Copilot Pro at $10 per month is $120 a year, less on the annual plan. Loading monthly adds 3% top-up fees, $3.60 a year, plus twelve TRC20 transfers at about $1. Loading once for the annual plan costs one 3% fee and one transfer. Pro+ at $39 per month follows the same math. The card is $49.99 once and covers Cursor, Claude, ChatGPT and cloud bills on the same balance.

Related guides