A Members Area for Your Business: Membership Plugin, Hosted Platform or Custom Build

What a members area is, and which kind you need

A members area is a part of a site that only signed-in people can see, usually because they paid. Under that one name there are four different products: a content library (articles, recordings, files), a course with lessons in order, a community, and a client portal with personal documents. They need different tools. I have built members areas on Paid Memberships Pro and course platforms on LearnDash with WooCommerce, and the expensive mistakes I was called in to fix started with the wrong kind of tool, not with a bug.

Before you compare tools, write down four things: what a member gets, whether they pay once or every month, how many members you expect in the first year, and what should happen on the day someone stops paying. If what you sell is a structured course, read my comparison of LearnDash, Tutor LMS and a custom build as well. This article is about access: who gets in, how they pay, and what it takes to keep that running.

Route 1: a membership plugin on your WordPress site

A membership plugin adds plans, a sign-up and payment page, and rules that say which plan sees which content. The site, the content and the member list stay on your hosting. Three plugins cover most of what small businesses ask me about, and they differ mainly in how they take money.

• MemberPress: its own pages say it restricts pages, posts, custom post types, categories, tags and files, releases content on a schedule, expires access and bills automatically. Its documentation lists four online gateways (Stripe, PayPal, Square and Authorize.net) plus an offline gateway where you give access by hand when the money arrives. Which gateways you get depends on the plan.
• Paid Memberships Pro: restricts content by post, page, block, shortcode or code. Its gateway page lists Stripe, PayPal, Paystack, CCBill and Payfast, plus manual and pay-by-check options, and says all of its gateway integrations support recurring subscriptions. Since 17 October 2024 its WordPress.org listing is closed at the author's request; the company says updates come from its own license server and the core plugin stays free on its site and on GitHub.
• WooCommerce Memberships: an extension that makes membership something a WooCommerce product grants. It restricts posts, pages, custom post types and products, and can release content over time. On its own a membership is unlimited or for a set length; a monthly or yearly charge needs WooCommerce Subscriptions next to it. This is the route that reaches the Israeli processors, because their plugins are written for WooCommerce.

Route 2: a hosted course or community platform

A hosted platform such as Teachable or Kajabi runs the members area for you: hosting, video, sign-up, payment and updates are their job, and you pay a subscription. You can be live in days, and there is no server to maintain. The cost is control. You work inside the pages, the checkout and the rules the platform gives you, and the member data sits with a foreign company.

For an Israeli business the first check is payment. Teachable lists Israel among the countries where its own payment system is available. Kajabi's help center has setup guides for Kajabi Payments in the United States, Canada, the United Kingdom, Europe, Australia and the United Arab Emirates, and Israel is not on that list. Ask two more questions before you sign up: how does each payment get an Israeli tax invoice, and can members pay in shekels with the cards they actually hold. I go deeper into these platforms in LearnDash vs Teachable vs Kajabi.

Route 3: a custom build

Custom code means the sign-up, the access rules and the billing logic are written for your business. You get exactly what you need, and you pay for every part of it, including the parts a plugin gives away: password reset, failed-payment handling, receipts, an admin screen. I recommend it in a small number of cases:

• The members already log in somewhere else, an app or an existing system, and the members area has to use the same account.
• Access depends on something outside the site: a status in a CRM, a contract, membership of an organization, a combination of purchases made at different times.
• The members area is the product itself, with its own screens and data, not a set of protected pages.
• A heavy WordPress site with a shop, a membership plugin and a course plugin cannot meet the speed you need on the hosting you are willing to pay for.

Payments and recurring billing in Israel: decide this first

This is where most members-area projects in Israel go wrong. Stripe publishes the list of countries where a business can open an account, and Israel is not on it. Stripe is the gateway available on every MemberPress plan and the one built into Paid Memberships Pro, and neither plugin lists an Israeli processor among its gateways. So a plan copied from an American tutorial stops at the checkout. What is left with those two plugins is PayPal, a manual payment you approve by hand, or a custom connection to an Israeli processor that someone has to build and maintain.

The WooCommerce route is different. WooCommerce Subscriptions charges renewals automatically only when the payment gateway supports it. With any other gateway it creates a pending renewal order that the member has to pay by hand, and a subscription that started with manual renewals stays that way. So the question for your processor is specific: does your WooCommerce plugin support automatic renewals in WooCommerce Subscriptions? The Cardcom plugin on WordPress.org lists support for WooCommerce Subscriptions and tokens for recurring charges. The PayPlus plugin answers "yes" to recurring payments in its own FAQ. Tranzila sells a recurring-billing system for cards and bank standing orders, with automatic handling of failed charges, and Grow offers standing orders for periodic payments.

Then plan the failed payment, because cards expire and get replaced. By default, when an automatic renewal fails, WooCommerce Subscriptions puts the subscription on hold and emails the customer, who has to log in and pay; the linked membership is paused until then. An optional retry system tries the charge again. Decide in advance how many days a member keeps access, who gets the alert, and what the email says. My comparison of Israeli processors and the payment gateway picker cover the choice of processor itself.

• Ask the processor: automatic renewals in my checkout, yes or no, and in which plugin version.
• Ask where the card token is stored, and whether it can move if you change processor.
• Check that an invoice or a receipt is issued for every renewal, not only for the first payment.
• Run one real subscription through a full cycle, including a failed charge and a cancellation, before you open sales.

What content protection can and cannot do

A membership plugin protects pages: a visitor without the right plan gets a login screen where the content would be. Files are a separate matter. A PDF or a video uploaded to the media library has its own address, and a page rule does not cover that address. MemberPress documents file protection for a fixed list of file types, including PDF, MP4, MP3 and ZIP, and states that it needs an Apache-compatible web server and is not supported on Nginx. Many fast hosts run Nginx, so check this before you promise protected downloads.

Video should not sit on your own server at all. A video host with embed restrictions is the usual answer: Vimeo, for example, has domain-level privacy, where you list up to 50 domains that may embed a video and any other site gets an error. That stops the link from working elsewhere. It does not stop a paying member from recording the screen, copying text or sharing a password, and nothing does. Protection raises the effort; what keeps members paying is content that keeps arriving and a reason to stay. If shared accounts become a real cost, limit simultaneous logins and watch for one account that signs in from many places.

Logins: the support work nobody budgets for

The day a members area opens, you become a help desk. On the members areas I have built and maintained, most of the messages were not about content. They were about getting in: a forgotten password, a reset email that landed in spam, a payment made with one email address and a login attempt with another, a card that expired. None of it is hard, and all of it takes time if the site was not built for it.

• Send site email through a proper sending service with the domain authenticated, so reset emails arrive.
• One account page where a member sees the plan, the next charge and the invoices, updates the card and cancels.
• Login, error and email texts written in Hebrew, right to left, not left in the plugin's English.
• A short answer page for the five questions that repeat, linked from the login screen.
• An admin view where you find a member by email or phone and see the payment status in one place.

Moving to another platform later

Members and content move. Subscriptions are the hard part, because the recurring charge lives with the payment processor, not in your site. The vendors say so themselves. MemberPress writes that the subscriptions you import must be real, active subscriptions that already exist at the payment processor, and that importing does not and cannot create subscriptions or start charges. Paid Memberships Pro writes that some platforms, WooCommerce Subscriptions and most hosted tools among them, create subscriptions in ways that cannot be transferred to another system; in those cases members get an expiry date and are asked to renew.

In practice, a move between platforms or between processors means some members will be asked to enter their card again, and some of them will not. Plan the move for a quiet month, tell members in advance, and keep the old system charging until the new one has taken a real renewal. This is also why the first decision, which processor holds the cards, matters more than which plugin shows the content. A hosted platform adds one more step: export the member list and the sales records before you cancel the subscription, because the school goes offline with it.

Member data, privacy and cancellation

A members area is a database of people: names, emails, phone numbers, what they bought and what they watched. In Israel that is personal information under the Privacy Protection Law, and Amendment 13 to the law has been in force since 14 August 2025. The Privacy Protection Authority describes it as a broad reform that, among other things, gives the Authority a mechanism of financial sanctions, and the Authority runs an online service for reporting a severe security incident in a database. I am not a lawyer, and which duties apply to your business is a question for one. The engineering side is mine: collect only what the members area needs, limit who on your team can see the list, keep the site and its plugins updated, and know where the backups are.

On your own WordPress site there are built-in tools for two requests you will get: Export Personal Data and Erase Personal Data, each approved by an administrator. WordPress is clear about their limits. They cover only WordPress and plugins that take part, erasing does not delete the user account or reach into backups, and you may have to keep some records, such as sales, for legal reasons. On a hosted platform the same data sits with a foreign company, which your privacy policy should say.

Cancellation is the other legal point. The Consumer Protection and Fair Trade Authority explains that an ongoing service bought online can be cancelled within 14 days of the purchase or of receiving the contract or disclosure form, whichever is later, whether or not the service has started, and that the business must return the money within 14 days of the cancellation notice. The same page lists exceptions, so check with a lawyer how the rules apply to digital content. Whatever the answer, make cancelling as easy as joining. A member who cannot find the cancel button disputes the charge with the card company instead.

How to choose

Go through the decisions in this order, and most of the choice makes itself. I am not tied to one platform, so the answer depends on your business, not on what I happen to sell.

• Payment first: one-time or recurring, in shekels, with an Israeli invoice. If recurring, the processor and its WooCommerce plugin decide the route.
• You already run WordPress or WooCommerce and want the members on your own site: a membership plugin, with WooCommerce Memberships and Subscriptions when the charge is recurring.
• You sell mostly abroad, in dollars, and want no technical upkeep: a hosted platform, after checking payment and invoices.
• Access depends on another system, or the members area is the product: a custom build.
• Not sure yet whether people will pay: start with the simplest route that takes a real payment, and move when the numbers justify it.

What drives the cost

I do not publish prices, and I do not list the vendors' license prices either, because they change; read them on the vendor's own page on the day you decide. Every project gets a fixed quote after a short call, and the project scope estimator gives a first sense of size. What moves the scope:

• The number of plans and how they differ: what each one opens, upgrades and downgrades between them.
• The payment set-up: recurring billing, failed-payment handling, invoices, trial periods and coupons.
• The kind of content: pages only, protected files, video, a course with progress.
• Moving existing members and their subscriptions from another system.
• Connections: CRM, email marketing, invoicing, WhatsApp alerts.
• Languages, and the design of the account page and the login screens.