Billing and subscription questions
Use the selected-server Plan page, protected hosted billing flow, and safe support path without unsupported pricing or subscription promises.
- Audience
- server admin
- Availability
- private beta access · feature flagged
- Maturity
- alpha · partial
Last reviewed
On this page
Confirm billing authority and server scope
Billing controls belong to one selected Discord server. The viewer needs dashboard access, Plan-page visibility, and the effective plan-management permission. Discord Administrator alone does not create owner-console or global billing authority.
| Check | Why |
|---|---|
| Selected server name and ID | Prevents managing the wrong server. |
| Current plan/status | Provides the before-action state. |
| Plan-management permission | Separates viewing from checkout/portal actions. |
| Official hosted destination | Avoids phishing or copied payment links. |
| No private moderation data in the browser handoff | Billing and moderation evidence must remain separate. |
Use the current hosted billing flow
Read the Plan page
Record the selected server, public plan, subscription/access status, and period end when shown.
Check: The administrator has the authoritative before state.
Use only a visible supported action
Choose Upgrade or Manage Billing only when the page exposes it and the server is eligible.
Check: The application requests a protected hosted URL or returns a specific error.
Review the hosted page
Confirm the official provider/server context and read the terms it presents before submitting anything.
Check: The billing decision is informed by the current hosted terms.
Return to the same server
After completion or cancellation, return to Billing & Plan and read the visible result.
Check: The browser is back in the intended server context.
Wait for status synchronization
Refresh the Plan page after the subscription event is processed; do not rely only on the return URL.
Check: Feature gates reflect the processed server subscription state.
Check one read-only feature
Open a non-destructive read/status surface included by the expected plan.
Check: The entitlement change is confirmed without a high-impact action.
Interpret billing and subscription states
| State | Meaning | Response |
|---|---|---|
| Free/no active Premium | Premium-gated features are not currently included unless a controlled preview says otherwise. | Use Free/core workflows or current approved preview. |
| Active/trialing | The stored subscription/override can provide Premium inclusion for an approved server. | Still check rollout, permission, and maturity. |
| Pending synchronization | Hosted checkout returned before the authoritative subscription event updated ModFlow. | Refresh later; do not open duplicate checkout. |
| Paused/past due/canceled/inactive | Current inclusion can be limited according to processed status. | Read the current Plan page and hosted portal; do not promise grace/restoration behavior. |
| Billing unavailable | The flow, configuration, permission, or eligibility is not available for this server/account. | Preserve the message and use support; do not invent a workaround. |
Recover from an unclear billing result
Checkout or portal is unavailable
What you see: The control is missing, returns no hosted URL, or reports billing unavailable.
What may be happening: The viewer can lack plan-management permission, the server can be ineligible, the hosted integration can be unconfigured, or general alpha purchase access can be unavailable.
What to do
- Confirm the selected server and plan-management permission.
- Read the current Plan page and public alpha/preview notice.
- Do not reuse a copied hosted URL or attempt owner/global APIs.
- Contact the published support path with server ID, time, and visible status only.
Checkout completed but Premium is not visible
What you see: The hosted page returned success, but the selected-server plan or feature remains unchanged.
What may be happening: Subscription synchronization can still be pending, the wrong server/account can have been used, or the event can have failed.
What to do
- Return to the same server's Plan page and refresh.
- Check hosted billing status when the portal is available.
- Do not create another checkout while the first outcome is uncertain.
- Send support the server ID, hosted-flow time, and visible status—never payment details.
A Premium feature remains unavailable
What you see: The Plan page shows Premium, but one command/page is hidden or denied.
What may be happening: Feature flag, private-beta approval, team permission, target/state check, or maturity/placeholder status can still restrict it.
What to do
- Open the feature guide and read every access axis.
- Check current autocomplete/page response.
- Ask a server administrator to review only the narrow permission/flag.
- Use a documented alternative when the feature is reserved or incomplete.
Commercial and documentation limits
This handbook does not publish prices, taxes, currency, purchase availability, cancellation effective time, downgrade behavior, refunds, payment-failure rules, grace periods, credit, invoicing, or restoration promises. Use the terms shown by the current hosted billing surface and official ModFlow communication for the approved server.
A prior screenshot, another server's subscription, internal tier name, or branch test cannot override the current selected-server Plan page.
Review access after a plan change
A subscription, owner-approved override, feature flag, and product maturity are separate. A downgrade can hide controlled data or leave queued and scheduled work in a plan-blocked state rather than executing. Historical records may remain readable where policy permits, and ending paid access does not delete them automatically.