Billing & licensing

Submitt keeps checkout and subscription management inside the Submitt website while Stripe securely processes card details, recurring invoices and payment authentication in the background.

Plans and server slots

Paid plans provide either one or three Discord server slots. Premium uses standard Submitt branding; White Label enables the additional per-server branding controls. Ticket panels, application panels and normal workflow usage are not limited by a panel-count quota.

Embedded checkout

When you choose a plan, Stripe Elements renders the secure payment fields directly within Submitt. The website never needs to receive raw card numbers. Promotion codes can be applied or removed before confirmation, and the displayed totals come from Stripe's checkout state.

If your bank requires 3D Secure or another authentication step, Stripe can request it during payment. Returning from authentication should resume the same checkout attempt instead of creating a second subscription.

Subscription provisioning

The browser success screen is informational. Submitt grants entitlement only after Stripe's verified billing events confirm the correct customer, plan/Price ID, active subscription and paid initial invoice. This protects against interrupted redirects or manually opening a success URL.

Server-slot management

After subscription activation, open Dashboard → Servers. Installing the bot does not by itself consume a paid slot. Click Use server slot when you are ready to license a specific guild. Releasing it makes the slot available again.

Changing your payment method

Open Dashboard → Subscription → Change payment method. The new method is collected securely through Stripe Elements and, after confirmation, becomes the default method used for future Submitt subscription invoices.

Upgrading

Capability upgrades—such as Premium to White Label or one server to three servers—may create an immediate prorated amount. Submitt uses Stripe's payment-gated subscription update behavior so the higher entitlement is not granted unless the required upgrade payment succeeds.

Downgrading

Changes that reduce server capacity or remove White Label are scheduled for the next renewal rather than stripping features you already paid for during the current billing period. Before a server-limit downgrade takes effect, decide which guilds should keep the remaining slots.

Cancel and resume

Cancellation is normally scheduled for the end of the current paid period. Until that date, the subscription remains usable under its current entitlement. If cancellation has not yet taken effect, use Resume to restore automatic renewal from the Subscription page.

Invoices

Recent Stripe invoices appear directly in Submitt. Where Stripe provides an invoice PDF, the dashboard exposes a download action without requiring the customer to open a separate Stripe portal.

Payment failures and grace behavior

If a renewal fails, Submitt synchronizes Stripe's subscription status and can allow the configured past-due grace behavior. A billing subscription can remain recoverable in Stripe even when product entitlement has expired; Submitt keeps those concepts separate so a customer cannot accidentally buy a second subscription while the original one still needs payment recovery.

Promotion codes

Promotion codes are evaluated by Stripe. Customer-restricted, first-time-customer or usage-limited codes can still be rejected by Stripe even when the text is entered correctly. Submitt uses the customer's persistent Stripe Customer record so eligibility is evaluated consistently across checkout attempts.