Add note about sponsorship cancellation when switching enterprise plan#44342
Add note about sponsorship cancellation when switching enterprise plan#44342slincoln75 wants to merge 1 commit into
Conversation
When an organization upgrades or switches their enterprise plan, the existing payment method is not carried forward. This note warns users that active paid subscriptions, including GitHub Sponsors sponsorships, are automatically cancelled if a new payment method is not added before the next billing cycle. Closes github/docs-content#22561 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
There was a problem hiding this comment.
Pull request overview
Adds a warning to the “Upgrading to the GitHub Customer Agreement” documentation to prevent billing surprises (specifically around payment methods not carrying forward and the impact on paid services like GitHub Sponsors).
Changes:
- Adds a new NOTE callout warning that existing payment methods aren’t carried forward when upgrading/switching an enterprise plan.
- Explains that paid subscriptions (including GitHub Sponsors sponsorships) may be canceled if a new payment method isn’t added before the next billing cycle.
- Links readers to billing documentation for managing payment information and GitHub Sponsors billing.
Show a summary per file
| File | Description |
|---|---|
| content/organizations/managing-organization-settings/upgrading-to-the-github-customer-agreement.md | Adds a NOTE callout about payment method carry-forward behavior and potential sponsorship cancellation, with links to billing docs. |
Copilot's findings
- Files reviewed: 1/1 changed files
- Comments generated: 1
| 1. To agree to the {% data variables.product.company_short %} Customer Agreement on behalf of your entity, click **Accept terms**. | ||
|
|
||
| > [!NOTE] | ||
| > When you upgrade or switch your enterprise plan, your existing payment method is not carried forward. If you do not add a new payment method before your next billing cycle, active paid subscriptions—including {% data variables.product.prodname_sponsors %} sponsorships—are automatically cancelled. To avoid disruption, add a payment method immediately after upgrading. For more information, see "[AUTOTITLE](/billing/how-tos/set-up-payment/manage-payment-info)" and "[AUTOTITLE](/billing/concepts/third-party-payments/github-sponsors)." |
Summary
Adds a note to the Upgrading to the GitHub Customer Agreement page warning that existing payment methods are not carried forward when switching enterprise plans, and that active sponsorships will be cancelled if a new payment method is not added.
Why
This addresses repeated incidents where organizations lost active GitHub Sponsors sponsorships after upgrading their enterprise plan without realizing their payment method would not carry over.
Closes github/docs-content#22561