Choose a one-time Discord pass when you sell a defined access period or a finite program. Choose a recurring membership when members pay for continuing community value. PayRequest Discord Memberships supports timed one-time passes, unlimited one-time access and native recurring subscriptions, each connected to a Discord role.
The decision changes your promise to members, your future workload and when managed access ends. This guide helps creators and workshop hosts choose the offer before following the paid Discord role setup guide.
Compare the three access promises
| Model | Example offer, not a recommended price | PayRequest configuration | Access boundary |
|---|---|---|---|
| Timed one-time pass | €29 for 30 days of a study community | Service product; 30 access days | Ends when that paid access period expires |
| Recurring membership | €12 each month for an ongoing creator circle | Native subscription product; monthly, interval count one | Eligible paid renewals extend access |
| Unlimited one-time access | €89 for an alumni community without automatic expiry | Service product; Unlimited access | No automatic time expiry; refund and dispute rules still apply |
A one-time pass supports 1–3,650 access days. Recurring periods can be daily, weekly, monthly or yearly, with an interval count of one. Eligible products need a positive price and one unit. Free trials, provider-managed subscriptions and another automatic delivery integration are not supported by this version.
“Unlimited” means no automatic expiry in this integration. It should not become an undefined promise that you will personally provide coaching forever. State the actual benefit, expected community availability and your published terms before taking payment.
Work through a two-product community example
Imagine an illustration community with two offers. Studio Circle gives ongoing discussions and monthly critique sessions for a fictional €12/month. Workshop Pass gives 30 days in a focused workshop space for a fictional €29 once. These amounts illustrate offer design; they are not PayRequest fees or a forecast.
Connect Studio Circle to the Community role and Workshop Pass to the Workshop role. Give each role access only to its promised channels. A workshop buyer should not receive permanent access to ongoing sessions simply because both products share a server.
In a full paid month, ten Circle purchases at €12 and four Workshop purchases at €29 produce €120 + €116 = €236 before platform/provider fees, refunds and any applicable taxes. Only the Circle is recurring. Do not treat the €116 workshop amount as guaranteed recurring revenue or assume every member renews.
This model uses two products connected to different Discord roles. It is separate from the one-plan PayRequest Page membership used for protected posts on your Page. Choose the destination your members actually need.
Decide with four practical questions
- Does the benefit end? A defined workshop or short challenge fits a timed pass. Continuing discussion, new events or regular support may fit recurring billing.
- Will you keep delivering value? A subscription creates an ongoing service expectation. Price the time and capacity you can actually provide.
- Which channels are included? Write the role-to-channel mapping before creating products. Keep staff powers separate from paid access.
- What should happen after the last paid day? Explain expiry and cancellation plainly. Avoid a vague “lifetime” claim when you mean no automatic expiry.
A starting offer template is: “Buy [product] for [price and currency]. It unlocks [channels/benefits] through [timed period / each paid recurring period / no automatic expiry]. To claim access, use your purchase email, connect your Discord account, join the server and accept its rules.”
Add your own support, cancellation and community conduct information. The template helps communicate product behavior; it is not a substitute for your terms.
Understand what renewal and cancellation really do
According to the Discord Memberships documentation, an eligible paid purchase is recorded once. Repeated provider notifications or access checks do not extend the same purchase again. Native paid renewals extend the paid period; an unpaid renewal does not.
A future scheduled cancellation does not remove access early. Timed access ends when its paid period expires or cancellation takes effect. Paused or suspended subscriptions do not grant current access. Do not use a different cancellation promise in your sales copy.
Refunds, credit notes, chargebacks and unresolved payment disputes stop the affected purchase from granting automatic access. Partial refunds or credits need seller review. Unlimited access has the same protections: no automatic expiry does not make a refunded purchase eligible forever.
If two valid purchases grant the same role, one expiring purchase does not remove it while the other still qualifies. PayRequest retains roles present before it took responsibility for granting them. This is why dedicated roles and a review of manual assignments matter.
Finalize terms before the first checkout
Saved product terms become fixed once an order, invoice, subscription or recorded access exists. Before that point, the same active role connection can explicitly switch from a fixed one-time duration to unlimited access while preserving the role and original connection date. This is a narrow setup exception, not a way to rewrite live entitlements.
Role changes, shorter access, disabled connections and other changes require a new product. Selecting an already connected product loads its saved settings. Only purchases created after the product was connected qualify; your old customers are not imported automatically.
Disabling delivery removes managed access at the next successful check, but does not stop subscription billing. If retiring an offer, review billing and communicate with affected members separately. The integration does not issue refunds, cancel billing, kick or ban members, or change channel permissions.
Keep checkout and access together
You can sell from a Payment Page without setting up a shop. After paying, buyers open Continue to Discord, sign in with the purchase email, connect their Discord account and join the server. Checks happen automatically, with retry controls and recovery checks; queues and Discord limits can delay delivery.
Choose one clear access promise, map its role, and use the Discord Memberships feature to connect the corresponding product. Review current PayRequest pricing separately from your membership price and provider fees.
*Prepared with AI assistance from first-party documentation on 1 November 2026. The two-product model, template and €236 calculation are hypothetical planning examples, not customer results or a tested sales forecast.*
