To sell Discord roles, create a paid membership plan, map it to one or more eligible Discord roles, and assign those roles only after Stripe confirms payment. When the member’s entitlement ends, remove the roles that no other active membership still requires.
The role is an access mechanism. Your offer should explain the community value behind it, not just the color of a badge.
Design tiers around different member needs
Use a small number of distinct tiers. These examples illustrate a possible structure; the prices are hypothetical and do not predict demand.
| Plan | Example price | Roles granted | Member promise |
|---|---|---|---|
| Supporter | €10/month | Supporter | Support the project and join a supporter channel |
| Premium | €29/month | Premium Member | Participate in member discussions and weekly sessions |
| VIP | €99/month | Premium Member + VIP Lounge | Premium access plus a bounded small-group session |
Write down which benefits are included at each level. If VIP includes Premium, map both roles explicitly. That makes the access promise auditable and avoids depending on names or visual grouping in Discord.
For annual plans, explain the billing commitment and renewal terms. For lifetime plans, consider whether the ongoing service can be funded after the initial payment. Lifetime revenue is not recurring MRR.
Configure channel permissions first
Create your paid roles in Discord and configure the channels they unlock. Avoid assigning moderation powers to a paid role unless that is a separate, carefully reviewed operational decision. Memberalia will not assign Administrator roles.
Place the bot role above the roles it will manage. Managed integration roles and roles at or above the bot are excluded. You should never need to give a membership automation bot Administrator just to assign ordinary paid access.
Check the server with a normal member account. A server owner can see channels that a regular user cannot, which can hide a permission mistake during testing.
Create the plans in Memberalia
- Create and verify your account, then create a workspace.
- Connect the creator’s own Stripe account.
- Connect Discord and select the server.
- Create a plan with its name, price, billing interval and concrete benefits.
- Choose the eligible roles the plan grants.
- Publish checkout and share the hosted membership page.
Products, prices and payments are created on the connected Stripe account. The Memberalia subscription is billed separately. See the setup guide if the account or permission flow is unfamiliar.
Link the purchaser to the right Discord account
Ask the member to connect Discord before Checkout. Their immutable Discord user ID ties the purchase to their community identity. Do not attempt to match a payment email to a display name or ask people to post transaction receipts in a public channel.
If they already have an active membership, they should manage that billing record instead of buying the same access twice. Keep a visible support path for members who used the wrong account or have not joined the server yet.
Respect overlapping access
Suppose a customer has both Premium and VIP, and both grant Premium Member. When Premium ends, the customer still needs Premium Member because VIP requires it. Removing the role blindly on every cancellation would break the remaining purchase.
The correct question is: “Does any currently valid entitlement require this role?” Memberalia aggregates access rules before assigning or removing roles. Manual access overrides should be clearly visible and explicitly returned to automatic mode when they are no longer needed.
Change prices without rewriting existing subscriptions
A price increase for new members should not silently alter the agreement with existing subscribers. Create a new Stripe Price and use it for future checkouts. Existing subscriptions retain their original price unless you intentionally arrange a billing change in Stripe.
Similarly, changing the roles behind a plan with active subscribers changes what those people receive. Memberalia keeps those access mappings fixed once subscriptions exist; create a new plan for a materially different bundle.
Rehearse cancellation and recovery
Test a successful purchase, renewal, failed renewal and period-end cancellation. A failed payment gets three days of grace in the default flow. A scheduled cancellation keeps the role through the paid period. Once access expires, the role should disappear.
Temporarily remove the role from an active test member and run synchronization. Then move the bot below the role and inspect the resulting error. The system should explain what to repair, not report a successful role grant.
Use the fee calculator to estimate platform costs and the sell Discord roles page to review the complete workflow before publishing your offer.