If the credit card you use to pay for GitHub is declined, there are several steps you can take to ensure that your payments go through and that you are not locked out of your account.
If your card is declined, we'll send you an email about why the payment was declined. You'll have a few days to resolve the problem before we try charging you again.
Check your card's expiration date
Verify your bank's policy on card restrictions
Some international banks place restrictions on international, e-commerce, and automatically recurring transactions. If you're having trouble making a payment with your international credit card, call your bank to see if there are any restrictions on your card.
Contact your bank for details about the transaction
Your bank can provide additional information about declined payments if you specifically ask about the attempted transaction. If there are restrictions on your card and you need to call your bank, there's information you can provide your bank to move the process along:
- The amount you're being charged. The amount for your plan appears on the receipts for personal accounts and organizations.
- The date when GitHub bills you. You can find this information in the Billing section of personal accounts and organizations.
- The transaction ID number. This ID number appears on the receipts for personal accounts and organizations
- The merchant name. This would be GitHub.
- The error message your bank sent with the declined charge. This message is listed on the email sent we send you when a charge is declined.
Warning: If your card is declined the first time you've added it to GitHub, you won't have a receipt, and therefore, no transaction ID or billing date. In these cases, you should provide the bank with as much information as you can.