Discord Server Subscriptions: US Eligibility, Fees and Mobile Price Differences

Discord Server Subscriptions are available to qualifying creators who can complete US payout onboarding. For a successful desktop or browser payment, the standard model applies 6% processing first and then Discord’s 10% platform fee to the reduced amount; iOS uses an app-store deduction and a higher subscriber-facing checkout price, while Android purchases are unavailable.

The practical payout is therefore not simply 90% of the tier price. Payment processing, transaction taxes, other transaction fees, refunds and chargebacks can all affect the result, and the amount paid by an iOS subscriber may differ from the price shown on desktop.

Who can enable Server Subscriptions?

The geographic restriction applies to the creator receiving payouts, not to every member of the server. Discord’s creator eligibility FAQ requires the account holder to be at least 18, provide US-based banking information and identification to Stripe, verify an email address and phone number, enable two-factor authentication and maintain an account in good standing; it also states that Server Subscriptions are unavailable to creators outside the United States.

Check the following conditions before building a paid-content plan:

• The server owner can complete the US identity and banking checks.
• The owner has no active violation, recent safety violation, suspicious-activity flag or unpaid Discord balance.
• Email and phone verification are complete.
• Two-factor authentication is enabled.
• The proposed offering is not covered by Stripe’s prohibited or restricted-business rules.
• The owner is prepared to create the separate Stripe account required for Discord onboarding.

These conditions are minimum requirements rather than a guarantee of approval. Safety and security signals are not limited to the examples in the checklist, and Discord retains discretion over access to monetization features.

A US audience, mailing address or collaborator does not replace the payout recipient’s required identity and banking information. Resolve eligibility before promising paid benefits or committing production resources to a subscription launch.

Set the tier price from the cost of delivery

A server owner controls the price and benefits of each tier. Begin with the recurring cost of delivering those benefits: moderation, exclusive posts, member support, live sessions, contractor payments and production time can continue even when subscriber growth slows.

Record three separate amounts for every tier:

• Base tier price: the amount used to configure and evaluate the offering.
• Subscriber checkout total: the amount the member sees in a particular supported purchase channel.
• Expected creator payout: the amount remaining after processing, the platform fee and transaction-specific adjustments.

Do not use these values interchangeably. An iOS checkout can exceed the base price, while desktop processing makes the creator payout lower than a simple 90% calculation based on the customer payment.

Describe benefits precisely and price them against a conservative net payout. Fixed deliverables—such as a specified number of posts or sessions per month—are easier to cost than an open-ended promise of direct access, and creators remain responsible for supplying the offering as described.

Purchase-channel fee map

Discord’s Monetization Terms list a 6% processing fee and a 10% platform fee for desktop or browser Server Subscriptions. The schedule lists 30% iOS processing, reduced to 15% for retained auto-renewing subscriptions after more than one year on a given tier as determined by Apple; it also lists 15% Google Play processing for auto-renewing subscriptions and 30% for other Google Play purchases.

• Desktop app or browser: 6% processing, applicable transaction fees and a 10% platform fee.
• iOS: normally 30% app-store processing, with the documented 15% retained-subscription category subject to Apple’s qualification rule, plus the 10% platform fee.
• Google Play: the legal schedule contains rates, but those rates do not establish that Android purchasing is currently offered.

The platform fee is calculated from the customer payment after applicable transaction taxes, payment-processing fees and other transaction fees. Consequently, adding 6% and 10% and treating the result as a flat 16% desktop deduction slightly overstates the standard deduction: the 10% is applied to a smaller base.

Additional transaction charges should remain in a separate forecast column. Currency conversion, payout-provider charges and other third-party costs can apply to particular transactions, but they are not defined as one universal additional percentage.

Eligible payouts are due within 45 days after the end of the relevant calendar month, subject to payout-account provisioning. The minimum balance is $100 for the first payout and $25 for subsequent payouts, so earned revenue can remain pending even when the fee calculation is correct.

Worked desktop and iOS payout examples

Let C represent the customer payment, T transaction taxes, R payment processing and X other transaction fees. A practical estimate of the platform fee is 10% × (C − T − R − X), making the estimated payout before later adjustments:

C − T − R − X − [10% × (C − T − R − X)]

For a conditional desktop example, assume a customer pays $10, no transaction tax or additional transaction fee applies, and the payment is not reversed. Processing is $0.60, leaving a $9.40 platform-fee base; the platform fee is $0.94, and the estimated creator payout is $8.46.

Across 100 successful desktop payments under the same assumptions, customers pay $1,000 in total. Processing is $60, the calculated platform fee is $94 and the estimated pre-adjustment payout is $846. This is an arithmetic illustration, not a guaranteed deposit.

The appropriate iOS comparison starts with the same base tier value rather than forcing the desktop and iOS checkout totals to be identical. In a simplified standard-fee model, grossing up a $10 base so that $10 remains after a 30% store deduction requires a customer payment of approximately $14.29 before store price-point restrictions, rounding and taxes. About $4.29 covers processing, after which a $1 platform fee leaves an estimated $9 payout before other adjustments.

Under the conditional 15% retained-subscription rate, the corresponding grossed-up payment is approximately $11.76. Processing of about $1.76 again leaves a $10 platform-fee base and an estimated $9 payout before other adjustments.

A calculation that starts with a fixed $10 iOS checkout and produces $6.30 after sequential 30% and 10% deductions answers a different question. It does not represent a $10 base tier whose mobile checkout has been increased to cover store processing, so it should not be used as the expected payout for that base tier.

Why members can see a higher iOS price

Discord’s member purchase guidance, updated July 1, 2026, confirms that Server Subscriptions can be purchased in the iOS app, that iOS subscribers see a higher checkout price to account for Apple’s additional 30% fee, and that subscriptions are not available to purchase on Android.

This distinction resolves an important ambiguity in the legal fee schedule. A listed Google Play rate can define the contractual economics for a transaction category without proving that members currently have access to that purchase route. For forecasting, count only purchase channels that members can actually use.

Do not promise one universal subscriber price across channels. The benefits may be identical while the checkout total differs, so communicate the base tier value and advise members to review the final amount displayed by their selected purchase route.

A hand-calculated iOS price should not be presented as authoritative. App Store price points, rounding, transaction taxes and any different terms displayed during checkout can alter the final total; the live confirmation screen controls the subscriber-facing amount.

Taxes, refunds and chargebacks require separate ledger lines

Transaction taxes are distinct from creator revenue and platform revenue. Where required, applicable sales tax or a similar transaction tax is collected from the purchaser and remitted to the relevant authority, while creators remain responsible for their own income and business-profit tax obligations.

Refunds and chargebacks can occur after the original sale and reduce a later payout. Amounts owed can be offset against future payments, while forfeited chargeback amounts and associated fees or fines may also become the creator’s responsibility when they result from the creator’s conduct or offering.

Maintain separate columns for gross customer payments, transaction taxes, processing, other transaction fees, platform fees, refunds and chargebacks. This prevents a reversal from being mistaken for a change in the standard fee rate and explains why a bank deposit may differ from the month’s successful sales total.

Also separate accrued revenue from cash received. Payout timing, minimum balances and account provisioning affect when money reaches the bank, even though they do not change the fee calculation for an individual successful transaction.

Build the forecast around the actual channel mix

Multiplying a listed tier price by subscriber count is not a reliable revenue forecast. Start with the number of successful purchases in each supported channel and apply the relevant processing path to each group.

1. Confirm that the owner can complete US monetization and payout onboarding.
2. Record the base tier price and live checkout amount for desktop, browser and iOS.
3. Separate desktop transactions from iOS transactions instead of immediately applying an average rate.
4. Calculate the platform fee from the post-tax, post-processing and post-transaction-fee base.
5. Post refunds and chargebacks when they affect the payout.
6. Reconcile the estimate with the Payments area and the amount ultimately sent through the payout provider.

Create both a base case and a conservative case. The base case can use your observed channel mix; the conservative case should allow for weaker renewals, higher delivery costs and a reversal reserve based on your own records. Avoid inventing a refund percentage before you have transaction history.

Make the launch decision from the conservative net amount

Before publishing a tier, verify that the owner passes the US eligibility checks, inspect the purchase routes currently visible to members and record the live checkout totals. Then calculate whether the conservative payout covers the recurring cost of every promised benefit.

If the economics work only when every member buys through the cheapest channel or no refunds occur, the tier has little operating margin. Adjust the price, narrow the benefits or delay the launch until the offering remains sustainable under a realistic channel mix.

Also read:

• How to Fix Fuzzy Pictures on Desktop, Online, and Mobile
• How to Use YouTube’s Refreshed Mobile Engagement Stats