# Billing

`/settings/billing` shows the plan for your personal account; every
organization has the same page at `/orgs/<handle>/settings/billing`, listed as
**Billing** in the settings navigation. Organization owners and admins can view
billing. Only owners can change the plan or billing settings.

## Plans

| Plan          | Account type                  |
| ------------- | ----------------------------- |
| Free          | Personal or organization      |
| Pro           | Personal                      |
| Team Standard | Organization, priced per seat |
| Team Premium  | Organization, priced per seat |
| Enterprise    | Contact sales                 |

Review the price, seat quantity and billing terms in Checkout before confirming
an upgrade.

The **Current plan** card names the plan, its price, a status badge (Active,
Trialing, Past due, Canceled, or No subscription) and the renewal or
cancellation date. A past-due subscription shows a payment warning.

Without an active subscription the **Upgrade** section offers the Pro card on
a personal account, and on an organization the Team card with a Standard and a
Premium seat tier plus an Enterprise card that links to sales. **Upgrade**
sends you to Stripe Checkout; the seat quantity is the current number of
seat-consuming members (outside collaborators do not use seats). After Checkout,
you return to billing with a confirmation or cancellation message. Your plan
updates after payment confirmation reaches GitCafe. If the page still shows your
old plan, refresh before starting another upgrade.

With an active subscription, **Manage payment & invoices** opens the Stripe
customer portal for payment methods, invoices, and cancellation, and returns
to the same page.

Account or organization closure is supported only for namespaces that have
never attached a Stripe customer or subscription. If closure wins a race with
the first customer creation, Checkout does not proceed and an empty, unattached
customer may remain at Stripe. GitCafe does not currently support closing a
namespace while provider billing custody remains attached; cancel and resolve
that custody before closure.

## Seats and overage

Per-seat organizations get a **Seats** card showing seats in use and an
optional **Seat limit**. Adding a member beyond the limit is rejected; leaving
it empty lets seats grow with membership. The licensed quantity in Stripe
follows the member count automatically.

The **Overage** card toggles metered usage past the plan's limits and an
optional monthly spend cap in dollars. A cap requires overage to be enabled.

## Not configured

If billing is unavailable on your instance, the page still shows the current plan
but renders "Billing is not configured for this deployment" and offers no
upgrade, portal, or save controls. Contact your instance operator if you need to change your plan.

## Plan gates

On instances that enforce plan limits, creating a private repository or
forking a private repository into an organization requires an eligible paid plan. Active, trialing and past-due subscriptions retain their plan entitlements;
other subscription statuses use the Free plan.