Connect Stripe to Discord by linking a customer’s Discord identity to their purchase, processing verified Stripe events, and mapping the resulting membership entitlement to Discord roles. A Checkout success page alone is not proof of payment.
You can build that integration yourself or use a focused service such as Memberalia. Either way, the access model should handle renewals, failed payments and cancellations, not just the first purchase.
The flow you are building
Discord OAuth → immutable Discord user ID
↓
Stripe Checkout → signed webhook → subscription snapshot
↓
entitlement
↓
Discord role
Stripe is authoritative for billing. The entitlement is authoritative for desired access. The Discord role is the current provider state. Keeping those records separate lets you say “payment confirmed, role assignment needs attention” instead of presenting an API error as a failed payment.
Prepare the server and bot permissions
Create the role that should unlock paid channels. Give that role the appropriate channel permissions, then place the Memberalia bot role above it. The bot requests Manage Roles; it does not need Administrator permission.
Discord’s role hierarchy matters even when the bot has Manage Roles. A bot cannot assign a role at or above its own highest role. Memberalia also excludes managed roles and roles containing Administrator permission.
Read the official Discord permissions documentation when reviewing the install. Test with a non-administrator account to confirm that your channel permissions do what you expect.
Connect your creator Stripe account
In Memberalia, create a workspace and verify your email. Select Connect Stripe and authorize an eligible Standard account. Complete any Stripe account activation requirements before publishing a paid plan.
Memberalia creates the community’s product, price and Checkout session in that connected account. This is a direct-charge arrangement: the creator’s Stripe account receives the payment. Memberalia’s €19/€39/€79 software subscription belongs to a separate platform billing flow.
Stripe documents subscriptions on connected accounts. If you build your own integration, verify the account context on every customer, price, checkout and portal request; mixing platform and creator objects causes both functional and ownership problems.
Create the plan-to-role mapping
In Communities, connect Discord and select a server you can manage. In Membership plans, create Premium at €29/month and choose Premium Member. You may choose multiple eligible roles when one offer needs several access areas.
Publish the plan, then open the hosted page with a normal member identity. The member connects Discord before proceeding to Stripe Checkout. This avoids having to guess which Discord account belongs to an email address after payment.
If the member has not joined the server, they need a server invite. A paid entitlement cannot make a role visible to someone who is not yet a guild member. Memberalia retries synchronization after the member joins.
Handle the events that change access
| Stripe event or state | Access decision |
|---|---|
| Checkout confirmed and subscription active | Activate the entitlement |
| Invoice paid on renewal | Keep access active |
| Invoice payment failed | Start the configured grace period |
| Cancellation scheduled | Retain access to the paid period end |
| Subscription ends | Expire or revoke access |
The Stripe webhook signature must be checked against the raw request body. Store the event ID and make repeated delivery harmless. Events can arrive more than once or out of order, so read the current subscription when updating desired access. See Stripe’s subscription webhook guidance.
For a custom implementation, do not scatter checks like stripeStatus === 'active' throughout the UI and role handlers. Resolve a single entitlement state and have every access job reread it before acting.
Test removal as carefully as assignment
Use Stripe test mode and a test Discord server. Confirm a successful payment grants the correct role. Then schedule cancellation and check that access remains until the paid date. Test immediate cancellation separately. Trigger a failed renewal and confirm the grace deadline does not move forward with each repeated failure.
Finally, remove the paid role manually while the entitlement remains active and run Sync now. The integration should repair it. If two active plans require the same role, canceling one must not remove the role while the other still grants it.
Troubleshooting checklist
- Role is not selectable: move the bot above it and remove privileged permissions from the membership role.
- Payment exists but access is missing: check the entitlement, Discord identity and server membership before repeating checkout.
- Webhook delivery fails: check the endpoint’s account scope and signing secret. Platform billing and Connect events use separate destinations.
- Canceled member still has access: distinguish a scheduled cancellation from an expired paid period, then inspect synchronization status.
The Stripe Discord bot page explains the product workflow. For plan limits and zero Memberalia transaction commissions, see pricing.