Sell memberships with Stripe Checkout, activate Discord roles after payment, and remove access when billing changes.
Guest checkout
Customers pay before Discord activation
0% transaction fee
Creator revenue stays in Stripe
Setup in minutes
Connect Discord, Stripe, and a role
Live workflow demo
MRR
$4,820
+14%
Active roles
312
Synced
Failed syncs
0
Today
1. Creator setup
Creator selects server and paid role
2. Customer checkout
Customer pays through hosted Stripe Checkout
3. Discord activation
Customer connects Discord after payment
4. Role assigned
GuildPass grants the VIP role automatically
5. Cancellation handled
Canceled memberships keep or lose access based on Stripe status
GuildPass is for creators who want recurring revenue without manually checking payments, assigning roles, or cleaning up access.
The hard part is not charging money. It is keeping payment state and Discord access clean as members join, recover, fail payments, and cancel.
Customers pay first, then GuildPass activates the Discord role.
Stripe webhooks keep role access aligned with subscription status.
Hosted Checkout, recovery links, and member management stay in one flow.
Creators follow a clear setup checklist. Once connected, the dashboard shows what is ready and what still needs attention.
Connect the services, choose the role, save a monthly plan, then share your join link.
Discord connected
Creator VIP Club
Paid role selected
@VIP Member
Stripe connected
Checkout ready
Join link live
/join/cmpj...
The core loop is intentionally focused: checkout, activation, role sync, member messaging, cancellation cleanup, and creator visibility.
Active subscriptions get access. Ended subscriptions lose access.
Customers subscribe first and connect Discord after payment.
Post new paid member messages after successful role assignment.
Send helpful private onboarding DMs after access is active.
Paid customers can recover activation if they close the success page.
Role removal follows Stripe subscription lifecycle events.
GuildPass uses Stripe for billing, Discord OAuth for identity, and webhook-driven logs for role automation visibility.
Card details stay in Stripe. GuildPass stores IDs and subscription state, not full card numbers.
Creators connect Discord to choose servers they manage, and customers connect Discord only after payment.
Customer membership payments go to the creator's connected Stripe account.
Creators can see subscription activity, role sync status, notifications, and lifecycle events.
Start small with a real paid membership workflow. Upgrade when your community grows past the Free plan limits.
$0 / month
$29 USD / month
The practical questions creators ask before trusting a paid Discord automation tool.
Creators connect Discord, connect Stripe, create a membership plan, and share a join page. Customers pay with Stripe, connect Discord after checkout, and GuildPass syncs the paid role.
No. Customer membership payments run through the creator's connected Stripe account. GuildPass does not take a transaction fee from customer membership revenue.
Yes. Use Stripe test mode first, verify Discord role assignment and cancellation behavior, then switch to live Stripe keys and reconnect Stripe.
Creators are responsible for their own refund policy. Customers manage billing through Stripe, and refund decisions belong to the creator.
The GuildPass bot needs Manage Roles permission, and its bot role must sit above the paid role in Discord.
If Stripe says the membership is still paid through the period, access stays until the subscription fully ends.
No. Customers can pay as guests, then connect Discord after checkout to activate the role.
Yes. Customers can use membership management to find an active membership by email and open Stripe's billing portal.
Built for creators who want Stripe checkout, Discord automation, customer recovery, welcome DMs, and cancellation cleanup in one focused workflow.