Keep one card for Copilot so the subscription stays apart from your other GitHub spend.
Home/Virtual cards/GitHub Copilot
AI & SoftwarePay GitHub Copilot with a ZyloCard virtual card
Copilot renews monthly or yearly through GitHub billing, and orgs adding seats can watch the charge jump past a capped card. Some regions hit declines on the first charge.
GitHub Copilot is the AI pair-programming subscription for individuals and organizations.
Why it works
Why pay GitHub Copilot with ZyloCard
Cap the card at your seat total so adding a Copilot seat cannot charge more than you approved.
Cap the card at your GitHub Copilot budget so a usage spike or a looping script cannot run up a surprise bill.
Freeze or delete the card the moment you cancel so GitHub Copilot cannot renew behind your back.
Step by step
How to pay GitHub Copilot in four steps
- 1Top up ZyloCard with crypto and issue a card named for GitHub Copilot.
- 2Set a monthly cap at or just over your expected GitHub Copilot spend.
- 3Add the card as your payment method in GitHub Copilot billing.
- 4Clear the small authorization and start using GitHub Copilot.
Smart moves before you pay
- ✓On an org plan, set the cap above the combined seat cost so the bigger charge clears.
- ✓Watch for a 3D Secure prompt on the first GitHub Copilot charge and clear it to turn billing on.
- ✓Keep a small buffer on the card for the initial authorization hold GitHub Copilot may place.
FAQ
Straight answers
Usually a cap below the seat total or a region issue. Raise the ZyloCard cap and match the billing country.
Cancel inside GitHub Copilot, then freeze or delete the ZyloCard card so nothing else can post.
Yes. Add a funded ZyloCard card in billing and keep the cap above the plan price.