Skip to content

Commit e4c586d

Browse files
authored
Merge pull request #39911 from github/repo-sync
Repo sync
2 parents 9aaf157 + af72b4b commit e4c586d

31 files changed

+652
-561
lines changed

content/billing/concepts/third-party-payments/github-marketplace-apps.md

Lines changed: 36 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
---
22
title: GitHub Marketplace app subscriptions
3-
intro: 'If you install a paid app in {% data variables.product.prodname_marketplace %}, your subscription shares your account''s existing billing date, payment method, and receipt.'
3+
intro: Understand how billing works for paid {% data variables.product.prodname_marketplace %} apps, including shared billing date and payment method, proration, free trials, unit limits, and plan changes.
4+
permissions: '{% data reusables.permissions.marketplace-org-perms %}'
45
redirect_from:
56
- /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-marketplace
67
- /articles/about-billing-for-github-marketplace
@@ -16,32 +17,38 @@ topics:
1617
shortTitle: GitHub Marketplace apps
1718
contentType: concepts
1819
---
19-
{% data variables.product.prodname_marketplace %} includes apps with free and paid pricing plans. After you purchase and install an app, you can upgrade, downgrade, or cancel at any time.
20+
21+
{% data variables.product.prodname_marketplace %} includes apps with free and paid pricing plans. After you purchase and install an app, you can upgrade, downgrade, or cancel **at any time**. This article explains the billing model, that is, what happens when you start, trial, change, or cancel a paid app subscription.
2022

2123
{% data reusables.marketplace.marketplace-apps-only %}
2224

23-
{% data reusables.marketplace.marketplace-org-perms %}
25+
## Core billing model
26+
27+
All paid {% data variables.product.prodname_marketplace %} app subscriptions for a personal account or organization share:
28+
* The existing payment method on file.
29+
* The same monthly or yearly billing date.
30+
* Consolidated receipts listing all paid {% data variables.product.prodname_dotcom %} products and app subscriptions.
2431

25-
## Payment methods and billing cycles for {% data variables.product.prodname_marketplace %} purchases
32+
**If no payment method exists when you first choose a paid plan**:
2633

27-
You will have the same payment method for all paid plans and subscriptions across {% data variables.product.prodname_dotcom %}.
34+
* You must define a payment method for the account.
35+
* The billing cycle for your account starts immediately and that day is the billing date for the account.
36+
* The full plan amount is charged.
37+
* The receipt is sent to the primary or billing email address on file for your personal account or organization.
2838

29-
If your personal account or organization doesn't have a payment method on file, when you choose a paid plan for an app:
30-
* Your billing date is today.
31-
* You must add a payment method to your personal account or the organization in which you want to install the app.
32-
* Your payment method is charged the full amount of your subscription.
33-
* Your receipt is sent to the primary or billing email address on file for your personal account or organization.
39+
**If a payment method already exists**:
3440

35-
If your personal account or organization has an existing payment method, when you choose a paid plan for an app:
3641
* The payment method on file is immediately charged a prorated amount based on the time remaining until your next billing date.
3742
* The monthly or yearly billing date for your app subscription is the same as the account or organization's regular billing date.
3843
* On your next billing date, your receipt lists charges for your paid {% data variables.product.prodname_dotcom %} plan and your app subscription.
3944

40-
When you choose a paid plan with a free trial:
45+
## Free trials
46+
47+
**When you select a paid plan that includes a free trial:**
4148
* You must have an existing payment method or add a new payment method for your personal account or the organization in which you want to install the app.
42-
* If you don't have any other paid plans or subscriptions, you are charged the full amount of your subscription at the end of the 14-day free trial.
43-
* If you have other paid plans or subscriptions, once your 14-day free trial ends, the payment method on file is immediately charged a prorated amount based on the time remaining until your next billing date.
44-
* If you have other paid plans or subscriptions, on your next billing date, your receipt lists charges for your paid {% data variables.product.prodname_dotcom %} plan and your app subscription.
49+
* If this is your only paid subscription, the first full charge occurs after the 14‑day trial ends.
50+
* If you already have other paid subscriptions, the end of the 14‑day trial triggers an immediate prorated charge for the remainder of the current cycle, then the plan renews on the shared billing date.
51+
* On your next billing date, your receipt will list charges for your paid {% data variables.product.prodname_dotcom %} plan and your app subscription.
4552

4653
{% data reusables.user-settings.context_switcher %}
4754

@@ -50,17 +57,25 @@ When you choose a paid plan with a free trial:
5057
5158
## Unit plan limits
5259

53-
If you choose a unit plan (for example, a plan that charges per user), and you exceed the units that you're paying for, the integrator may disable your access until you upgrade the app. For more information, see [AUTOTITLE](/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app).
54-
55-
## Downgrading a {% data variables.product.prodname_marketplace %} app
60+
For plans that charge per unit (for example, per user), exceeding the purchased units can lead the developer to restrict or disable app access until you move to a plan that covers the higher usage. For more information, see [AUTOTITLE](/billing/managing-billing-for-github-marketplace-apps/upgrading-the-billing-plan-for-a-github-marketplace-app).
5661

57-
If you downgrade your app subscription to a less expensive plan or if you cancel a paid app subscription, your changes will take effect at the end your current billing cycle. Your subscription will be moved to your new plan on your next billing date.
62+
## Plan changes and cancellation
5863

59-
If you cancel an app on a free plan, your subscription will immediately end and you'll lose access to the app.
64+
* **Upgrading or adding capacity** takes effect immediately; a prorated amount may be charged for the rest of the cycle (if applicable).
65+
* **Downgrading a paid plan or canceling a paid app** takes effect at the end of the current billing cycle; access continues until then. Your subscription will be moved to your new plan on your next billing date.
66+
To learn how to downgrade a paid plan or cancel a paid app, see [AUTOTITLE](/billing/how-tos/pay-third-parties/downgrade-marketplace-app) and [AUTOTITLE](/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app).
67+
* **Cancelling a free plan** ends the subscription immediately with loss of access.
68+
* **Canceling a free trial** on a paid plan ends the trial immediately and access stops.
6069

6170
{% data reusables.marketplace.downgrade-marketplace-only %}
6271

63-
If you cancel a free trial on a paid plan, your subscription is immediately canceled and you will lose access to the app. For more information, see [AUTOTITLE](/billing/managing-billing-for-github-marketplace-apps/canceling-a-github-marketplace-app).
72+
## Privacy
73+
74+
Publishers get only what they need to provision service, such as purchaser context (user or organization), plan identifier, effective dates, seat or unit counts, required usage metrics.
75+
76+
Publishers don't see your full payment details, other product invoices, or unrelated account data.
77+
78+
GitHub processes payments and issues receipts. Publishers cannot directly charge your payment method outside the standard plan billing flow.
6479

6580
## Further reading
6681

content/billing/concepts/third-party-payments/github-sponsors.md

Lines changed: 31 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: GitHub Sponsors billing
3-
intro: You will be billed for your sponsorships with the rest of your paid products and features.
3+
intro: Understand how sponsorship payments appear in your billing, how they align with your existing payment method and billing date, and what fees apply.
44
redirect_from:
55
- /github/setting-up-and-managing-billing-and-payments-on-github/about-billing-for-github-sponsors
66
- /articles/about-billing-for-github-sponsors
@@ -16,14 +16,42 @@ topics:
1616
shortTitle: GitHub Sponsors
1717
contentType: concepts
1818
---
19+
20+
This article describes the billing model for {% data variables.product.prodname_sponsors %} from the sponsor’s point of view.
21+
1922
{% data reusables.sponsors.sponsorship-details %}
2023

21-
{% data reusables.sponsors.no-fees %}
24+
## What a sponsorship billing entry represents
25+
26+
A sponsorship is a monetary commitment you make to a sponsored developer or organization through {% data variables.product.github %}. Each active recurring sponsorship produces a charge on its renewal date; one‑time sponsorships produce a single charge. For more information, see [AUTOTITLE](/sponsors/getting-started-with-github-sponsors/about-github-sponsors).
2227

23-
{% data reusables.dotcom_billing.view-all-subscriptions %}
28+
## Unified payment method and billing date
29+
30+
Your sponsorships use the same stored payment method as your other paid products for the relevant personal account or organization. They follow the existing billing date/cycle for that account.
31+
32+
You can review active sponsorships alongside other paid subscriptions for the account to understand total ongoing commitments and historical charges.
33+
34+
If you sponsor from multiple accounts (personal vs organization), each account’s sponsorship charges stay separate and align with that account’s own billing cycle.
2435

2536
{% data reusables.user-settings.context_switcher %}
2637

38+
## Fees
39+
40+
{% data reusables.sponsors.no-fees %}
41+
42+
## Privacy
43+
44+
Sponsored parties see sponsorship details required for recognition or fulfillment, not your underlying payment method details.
45+
46+
## How sponsorship billing works
47+
48+
1. You create a one‑time or recurring sponsorship at a chosen amount (tier or custom amount if permitted).
49+
1. The amount is charged (immediately for one‑time, and on each renewal cycle for recurring).
50+
1. Changes to amount or cancelation affect future cycles (the current paid period continues until the next renewal unless you selected a one‑time sponsorship).
51+
1. Ended sponsorships stop appearing as future charges but remain in historical billing records.
52+
53+
Proration is generally not part of sponsorship billing: changing an amount updates future renewals rather than retroactively adjusting the in‑progress period.
54+
2755
## Further reading
2856

2957
* [AUTOTITLE](/sponsors/getting-started-with-github-sponsors/about-github-sponsors)

content/subscriptions-and-notifications/concepts/about-notifications.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,8 @@ To keep your subscriptions manageable, review your subscriptions and watched rep
5959

6060
To customize how you'd like to receive updates for specific pull requests or issues, you can configure your preferences within the issue or pull request. For more information, see [AUTOTITLE](/account-and-profile/managing-subscriptions-and-notifications-on-github/viewing-and-triaging-notifications/triaging-a-single-notification#customizing-when-to-receive-future-updates-for-an-issue-or-pull-request).
6161

62+
Each email notification that {% data variables.product.prodname_dotcom %} sends contains header information that you can use to filter notifications in your email client. For information about the headers included, see [AUTOTITLE](/subscriptions-and-notifications/reference/email-notification-headers).
63+
6264
You can customize and schedule push notifications in the {% data variables.product.prodname_mobile %} app. For more information, see [AUTOTITLE](/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications#managing-your-notification-settings-with-github-mobile).
6365

6466
## Reasons for receiving notifications

0 commit comments

Comments
 (0)