To run a paid community on WordPress with Stripe, you need four things: a community engine for the members, a Stripe account to collect money, a set of plans that decide who gets into which Space, and a place where members can manage their own billing. BuddyNext covers the first and third inside WordPress, Stripe covers the second and fourth, and Reign makes the member-facing pages look like your brand. This guide walks from tier design to launch day.
Stripe details here come from Stripe’s own documentation, and BuddyNext details from buddynext.com and the BuddyNext release notes, all read in October 2026. Both change often, so check the current pages. Wbcom makes BuddyNext and Reign.
In this guide
- Paid community versus membership site
- Plans and pricing
- How Stripe works
- What BuddyNext adds
- Setup, step by step
- Failed payments, refunds and disputes
- Tax and legal basics
- Reign for account pages and gated layouts
- Other ways to charge
- Questions people ask
What is a paid community, and how is it different from a membership site?
A paid community is a members-only space where the thing people pay for is each other. A membership site sells access to content. A paid community sells access to people, conversations and a place to belong, usually with content added on top.
That difference changes the build. A content site can be a library behind a login. A community needs a feed, profiles, groups, messages and moderation, because those are what members stay for. If you only need to lock a few pages, read our guide to a members-only content area instead. If you want a payment plugin attached to BuddyPress, our Paid Memberships Pro playbook covers that route, and our post on paid communities for coaches and consultants covers pricing around your own time.
This guide follows BuddyNext’s built-in Stripe plans from the first pricing decision to the first month of renewals. It also explains how Stripe itself works, because most payment problems on community sites are Stripe settings nobody looked at.
Still deciding whether to use WordPress? Start with the self-hosted community platform comparison and what you keep on Patreon, Substack and Circle.
How should you structure plans and pricing for a paid community?
Start with the smallest structure that is honest: one paid plan, one clear promise, and a free way to look around. Add more plans only when real members ask for something the first plan does not give them. This section deliberately has no price points, because the right number depends on your audience, your niche and what you deliver. Look at what members in your space already pay for comparable access, then set your own.
One paid plan or several?
A single paid plan is easier to explain, easier to support and easier to test. Several plans make sense when you have genuinely different groups, for example people who want the community only and people who also want live sessions with you.
Each extra plan makes members compare, ask which to pick and sometimes feel they chose wrong. If you cannot say in one sentence what separates two plans, merge them.
A free plan is worth keeping as a public front door, where people can join, post in an open Space and see what the paid area promises. BuddyNext supports Free-plan and trial-day setups on its tiers, and its release notes describe a member whose paid plan ends being moved back to the Free plan rather than being locked out of the site.
Monthly or yearly?
Offer both. Monthly lowers the barrier to joining. Yearly pays you earlier, gives members a reason to commit, and means fewer renewal moments where a card can fail or a member can drift away.
The trade is that a yearly payment is a bigger single charge. That makes a refund request or a dispute larger too, and it asks more trust of a new member. A sensible pattern is to let people start monthly, then show the yearly option inside the account page once they have had a few weeks of value. BuddyNext lets a plan offer both intervals, shows a Monthly and Yearly toggle on the pricing table, and lets members switch between them on their own.
If the yearly option is there to improve cash flow, make the saving clear. State it in words on the pricing page so no one has to work it out.
Should you offer a free trial?
Offer one only if members can reach their first real moment of value inside the trial. A community has a slow start: the feed looks quiet until you have posted, replied and met people. A trial that ends before that happens converts badly and creates refund requests.
If you run a trial, tie it to onboarding: a welcome message, one Space to introduce yourself in, one thing to do in week one. Our post on member onboarding with welcome sequences shows the idea.
Stripe also lets you choose whether a trial needs a card up front. Collecting it makes conversion automatic but can put people off starting. Skipping it brings in more trial members, and fewer convert. Pick based on whether your bigger problem is sign-ups or conversion.
What about founding members?
A founding-member offer rewards the first people who join before the community has momentum. Keep it small, give it an end date, and describe exactly what they get. Common choices are a rate that stays fixed while they remain subscribed, a profile badge, or a say in early decisions.
Be careful with the word lifetime. Define it: of the community, of your involvement, or of the software? A vague promise becomes a support problem. BuddyNext supports one-time plans next to monthly and yearly ones, and its release notes say access lasts on one-time plans. A one-time plan brings in cash now and nothing later, so use it sparingly and not as your main plan.
BuddyNext can also grant a plan to someone directly over its REST API, which the release notes describe as a way to give complimentary access. That is handy for speakers, moderators and early supporters you want to thank without charging them.
How does Stripe work for a paid community?
Stripe is the payment processor. It collects the card, stores the payment details, bills again every cycle and tells your website what happened. Four Stripe pieces matter for a community.
Checkout: where the member pays
Stripe Checkout is Stripe’s prebuilt payment page. Stripe’s documentation describes a full-page option that is either embedded on your site or reached by a redirect to a Stripe-hosted page, an embedded form, and a more manual Elements route that takes the most upkeep. The full-page option is the one Stripe recommends. It accepts one-time and subscription payments, and its order summary can show free trials, discounts and promo codes.
The BuddyNext release notes say its Stripe integration moved to hosted Checkout, so that payment is collected before a membership is granted. That is the safe order for a paid community: money first, access second.
Subscriptions: what bills again every cycle
A Stripe subscription is a recurring payment arrangement. Stripe creates an invoice each cycle, tries to collect and updates the subscription’s status. The statuses you will meet are trialing, active, past due, unpaid, canceled and paused.
Stripe’s documentation says to provision access when a subscription is active and to revoke it when it is unpaid, because by then Stripe has already tried and retried the payment. A past due subscription sits in between: the latest invoice failed, and Stripe may still retry. What your site does at each status is the heart of a paid community.
Webhooks: how Stripe tells your site
A webhook is a message Stripe sends to your website when something happens, such as a payment succeeding or failing. Your site listens and changes the member’s access to match. If the webhook never arrives, Stripe thinks the member paid and your site thinks they did not.
The BuddyNext release notes record exactly this failure in an early version, a buyer whose webhook never arrived and was left without a membership. They also say the Payment Gateways screen now names every Stripe webhook event it needs and flags any that are missing from your Stripe webhook. It is the first place to look when someone says they paid and has no access.
The customer portal: where members manage themselves
The Stripe customer portal is a Stripe-hosted page where a customer manages their own account. Stripe’s documentation lists these actions: update billing information and tax IDs, update payment methods, switch or cancel subscriptions immediately or at the end of the billing period, and view, pay and download invoices. It can also offer a coupon when someone tries to cancel and collect their reason for leaving.
Two details from Stripe’s documentation matter for communities. The portal has to be activated in your Stripe Dashboard before it works. And by default, a customer who changes a subscription that is in a free trial ends the trial and triggers an immediate invoice, unless you set the portal to continue the trial.
What does BuddyNext add for charging members?
BuddyNext connects Stripe to the community itself, so a plan decides what a member can see and join. Per buddynext.com, membership and monetization features need a paid licence, so check the product page for what your licence includes. The community features themselves, such as the activity feed, Spaces and profiles, are described separately on the site.
The table below lines up what you need to do against what BuddyNext and Stripe each handle. It uses the wording on buddynext.com and in the BuddyNext release notes as of October 2026.
| What you need | BuddyNext | Stripe |
|---|---|---|
| Plans in several billing styles | Membership tiers: monthly, yearly or one-time, with per-tier perks and numeric caps | Holds the products, prices and recurring billing |
| Trials | Free-plan and trial-day support; a plan with a free trial starts it at the payment provider | Runs the trial and the first charge |
| Paid-only Spaces | Gate whole Spaces behind a plan; one plan can open many Spaces, and a Space can be gated behind more than one plan | Not involved after payment |
| Locked posts and sections | Protect posts or sections inline, showing a teaser and a lock | Not involved after payment |
| Taking payment | Pricing page, coupons, checkout hand-off | Hosted Checkout page |
| Self-service billing | My Membership page; members can cancel, switch interval and see billing history in the app | Customer portal for payment methods and invoices |
| Renewals and failed payments | Automatic renewals and past-due handling; renewal reminders | Retries, dunning and subscription status changes |
| Revenue overview | A Billing screen with MRR and ARR projections and a Received figure | Dashboard reports |
| Refunds and disputes | A Stripe refund or dispute revokes paid access; partial refunds supported | Issues the refund, runs the dispute process |
Two limits. First, Wbcom’s own BuddyNext versus MemberPress comparison says MemberPress has a more granular rules engine for restricting content and supports more payment gateways out of the box. If your main need is intricate content rules across hundreds of pages, a dedicated membership plugin may suit you better. BuddyNext’s case is a paywall that sits inside the community instead of next to it. Second, wording about payment gateways varies across Wbcom’s pages, so check the product page for which gateways are supported today. This guide covers Stripe.
MRR means monthly recurring revenue, the predictable subscription income you can expect in a month. ARR is the same idea over a year. They are projections from your current subscribers, not money in the bank, which is why the Received figure beside them is useful.
How do you set up a paid community on WordPress with Stripe, step by step?
You set it up in eight steps, and you should test each one before you move on. Do the first run in Stripe’s test mode so no real card is charged.
Step 1: Build the community first
Install WordPress, the Reign theme and BuddyNext, and run BuddyNext’s setup wizard to the end. Create the Spaces you plan to charge for and a few open ones. Try the BuddyNext live demo first if you want to see a working community before you install anything.
To confirm it worked, log in as a test member and check that you can post in an open Space and see profiles and the directory.
Step 2: Create and verify your Stripe account
Sign up at stripe.com and complete the account details Stripe asks for. Stripe also provides a sandbox, where simulated transactions do not move funds, and test cards that simulate successful payments, declines and authentication. Use that for every test in this guide.
To confirm it worked, you should be able to open your Dashboard and switch into the sandbox from the account picker.
Step 3: Activate the customer portal in Stripe
In the Stripe Dashboard, activate the customer portal and choose what members may do in it. Decide whether members can switch plans, cancel at once or at period end, and whether to offer a cancellation coupon. The BuddyNext release notes say the Stripe setup steps include activating the customer portal, which the Update payment method link needs.
To confirm it worked, open Stripe’s portal preview and check that branding, cancellation and payment method options look the way you intended.
Step 4: Connect Stripe inside BuddyNext
Open the payment gateway settings in BuddyNext, add your Stripe keys and create the Stripe webhook endpoint that the settings screen describes. Then compare the webhook events in Stripe against the list on BuddyNext’s Payment Gateways screen, which flags any that are missing.
The release notes also say a live site is warned when a gateway is left in test mode. Do not ignore that warning at launch.
To confirm it worked, the Payment Gateways screen should report no missing webhook events.
Step 5: Create your plans
Create each plan with its billing interval, trial settings and the Spaces and features it includes. According to the release notes, plans start inactive, so remember to activate each one. A plan can also be unlisted, which keeps it off the pricing page while anyone with its link can still subscribe. Use that for founding-member offers or private partner deals.
Set the Spaces that need a paid plan, and decide what non-members see when they reach a gated Space. The release notes say a gated Space names the required plan in its refusal message, and members-only content shows a teaser and a checkout call to action.
To confirm it worked, open each plan’s pricing page logged out and check the monthly and yearly toggle, the trial wording and the price shown.
Step 6: Build the pricing page and the upgrade path
The BuddyNext release notes describe the pricing page as a normal editable WordPress page, built from blocks, with a membership-pricing block. Design it with Reign’s layouts like any other page. Keep it plain: what each plan includes, who it suits, one button each, and short answers on refunds, cancelling and billing dates.
To confirm it worked, click every call to action as a free member and check each one lands on the right plan.
Step 7: Test the whole journey in test mode
Use Stripe’s test cards to run the full cycle: sign up, start a trial, pay, access a gated Space, switch interval, cancel and let a payment fail. Use Stripe’s documented test cards for success, declines and authentication, and check what the member and the admin each see at every step.
To confirm it worked, a test member gains access on payment, keeps it until the paid period ends after cancelling, then loses it.
Step 8: Go live and make a real purchase
Switch BuddyNext and Stripe to live mode, swap in live keys, recreate the webhook and buy your own plan with a real card. Then refund yourself from the Stripe Dashboard and check that BuddyNext revokes the access, as the release notes say it should after a Stripe refund or dispute.
To confirm it worked, you should see the real payment in Stripe, the order in BuddyNext’s billing screen and the access change after the refund.
What happens when a member’s payment fails?
When a renewal fails, Stripe marks the subscription past due, retries the payment on a schedule and, if every retry fails, moves the subscription to the state you chose. Many failed payments are not members leaving, and recover if you handle them kindly.
Stripe recommends Smart Retries, which picks retry times using signals about each payment instead of a fixed timetable. You can also set a custom schedule. In your Stripe failed-payment settings you choose what happens after the last retry: cancel, mark unpaid, leave past due, or pause. Stripe’s documentation also notes that some declines are hard declines, such as a lost or stolen card, which are not retried until the customer supplies a new payment method.
Three things help.
- Tell the member, in plain words. Stripe recommends notifying customers so they can update their payment method. A short, friendly email that links to the customer portal works better than a warning.
- Decide on a grace period. Stripe’s documentation says to revoke access when a subscription is unpaid. Between past due and unpaid, you decide how much slack to give. Being suddenly locked out of your friends feels worse than losing access to a PDF, so lean towards patience.
- Make fixing it easy. The portal lets members update their card themselves. BuddyNext’s release notes say its Update payment method link opens the billing portal, including for members who paid with a different email.
BuddyNext describes automatic renewals and past-due handling on its features page, plus renewal reminders that warn members before a membership renews or ends. The release notes add that a past due subscription stays past due and a free trial stays a trial, so a stalled payment does not quietly turn a trial member into a paying one.
To confirm your failed-payment flow works, use a Stripe test card that declines on renewal, then check that the member sees a clear message, the portal link works and access follows the policy you chose.
How do refunds and disputes work?
A refund is money you send back on purpose. A dispute, also called a chargeback, is money the customer’s bank pulls back after the member questions the charge. Refunds are cheaper and kinder than disputes, so make refunds easy to ask for.
Stripe’s documentation says you can refund all or part of a payment from the Dashboard or the API, and that you can issue more than one refund against a charge as long as the total stays within the original amount. The original processing fees are not returned. A refund goes back to the original payment method and, depending on the bank, reaches the customer several business days later.
A dispute works differently. Stripe’s documentation explains that the card issuer reverses the payment immediately, and Stripe debits your balance for the amount and a dispute fee. You can respond with evidence in the Dashboard. A clear refund policy makes disputes less likely.
On the WordPress side, BuddyNext’s release notes say a Stripe refund or dispute revokes paid access, partial refunds adjust the price and leave the member’s plan alone, and a refunded or ended paid plan leaves the member on the Free plan. Decide your policy before you launch: how long after joining members can ask for a refund, whether it applies to yearly plans, and what happens to the content and posts they made.
What are the tax and legal basics for charging for a community?
Charging for a community makes you a seller, and sellers have obligations. This is not legal or tax advice. The answers depend on where you and your members live, so check your local rules or speak to a qualified adviser.
Tax
Ask whether you must collect sales tax, VAT, GST or similar on digital subscriptions, and from which customers. Stripe’s documentation says that before you collect tax with Stripe Tax you must register with the local tax authority, and that without a registration in the customer’s location the calculation returns zero tax. Stripe Tax can calculate tax on subscriptions and Checkout, monitor where you might need to register, and help with filing in many countries. Stripe also describes a Managed Payments option where Stripe handles sales tax and VAT in a list of countries. Availability and terms vary, so read the current pages and check them against your situation.
Decide whether your displayed prices include tax or add it on top. BuddyNext’s release notes state that the price shown includes tax, so confirm how this behaves on your site before you publish prices.
Consumer and subscription rules
Many places have rules about clear pricing, automatic renewal notices, easy cancellation and cooling-off periods for digital purchases. Stripe maintains a page on compliance requirements for trials and promotions, and its documentation notes that Stripe-hosted reminder emails are sent before a trial ends. Whatever the rules are for you, say plainly on the pricing page how much and how often members are charged, when the first charge happens, how to cancel and what the refund policy is.
Terms, privacy and content
Publish terms of service, a privacy policy and a refund policy. Add house rules about conduct and about what happens to posts when someone leaves. If you collect personal data, check which data-protection rules apply to you. Review all of it before launch and whenever you change plans.
How does Reign handle member account pages and gated layouts?
Reign is the design layer. It styles the community, pricing page and account screens so the paid area looks like part of your site, with five header layouts, colour tokens and dark mode, set without code.
Three places benefit most.
- The pricing page. Because BuddyNext’s pricing page is an ordinary WordPress page, Reign’s layouts, headers and colours apply to it. Keep one decision per plan.
- The member’s account area. Per the release notes, members manage their plan under Settings, then Membership, and see any queued plan change. Reign keeps those screens in your brand, which matters because the account page is where a member decides whether to stay.
- Gated Spaces and locked content. A locked Space or post should show what is inside, who it is for and one button to join. Use the teaser and lock pattern, check it on a phone, and make sure the upgrade button has enough contrast in dark mode.
See how to build a paid membership community with the Reign theme for a wider look at layout choices, and how to create a membership site that converts for page-level advice.
What are the other ways to charge for a community?
Charging through BuddyNext is one route among several. The right one depends on how much you value having the paywall inside the community versus having the widest range of payment and restriction options.
| Option | What it does well | Where it is weaker or unclear |
|---|---|---|
| BuddyNext with Stripe plans (Wbcom’s product) | Paywall, Spaces, profiles and messages in one WordPress install; gated Spaces and inline locks; MRR and ARR on a billing screen | Monetization needs a paid licence; Wbcom’s own comparison says MemberPress has more granular rules and more gateways |
| Paid Memberships Pro with BuddyPress and Reign | A dedicated membership plugin that handles levels, billing and content restriction; our playbook shows the full setup | Needs an integration plugin to tie levels to groups, per our guide; more parts to keep updated |
| FluentCommunity | A WordPress community and course plugin with a feed, spaces and an LMS, per fluentcommunity.co | Its homepage does not describe paid memberships or Stripe, so check its site for paywall support before choosing it for a paid community |
| Hosted platforms such as Circle or Skool | Quick to start, payments and hosting handled for you; see our Circle and Skool comparisons | You rent the platform, and member data and design sit on someone else’s terms |
A hosted product is faster to start. WordPress suits you if you want your own domain, member list and brand. Our post on monetizing your community with subscriptions, courses and paid groups covers more models.
What should you check before launch day?
Before you open the doors, confirm six things. Stripe is verified and live. The customer portal is active. BuddyNext’s Payment Gateways screen shows no missing webhook events. You have made and refunded one real purchase. Gated Spaces behave for a logged-out visitor, a free member and a paid member. Your terms, privacy notice and refund policy are linked from the pricing page.
Then launch to a small group first. Ten real members will find problems no checklist can. Fix them, then widen the door.
Frequently asked questions
How do I charge for a community on WordPress?
Run a community plugin such as BuddyNext on a WordPress site, connect a payment processor such as Stripe, create paid plans, and gate the Spaces or content that paying members get. BuddyNext’s monetization features need a paid licence, so check the product page for details.
Do I need a separate membership plugin as well as BuddyNext?
Not for the setup in this guide, since BuddyNext includes membership tiers and Stripe checkout in its paid features. A separate membership plugin makes sense if you need very detailed content-restriction rules or a payment gateway BuddyNext does not offer. Wbcom’s own comparison says MemberPress is stronger in those two areas.
Can members manage their own billing?
Yes, in two places. Stripe’s customer portal lets customers update payment methods, switch or cancel subscriptions and download invoices. BuddyNext adds a My Membership page where members can cancel and see their plan, and its release notes say members can read their billing history in the app.
What happens to a member’s access when they cancel?
Per the BuddyNext release notes, a member who cancels keeps access for the time they have paid for, then moves to the Free plan. A refund or dispute revokes access straight away.
Who is responsible for tax on membership payments?
You are, as the seller, and the rules depend on where you and your members are. Stripe Tax can calculate and help file tax, but Stripe’s documentation says you must register with the local tax authority before collecting it. Check your local rules or ask an adviser.
Reign ties this together by styling the community, pricing page and account area. See the Reign theme page for features and demos, read about BuddyNext, and try the live demo before you decide on a plan structure.