A membership website sells continuity, not a single transaction. The customer pays today, expects access tomorrow, and expects the same access next month for as long as they keep paying. That promise sounds simple, but it hides a billing engine, an access-control layer, a content delivery system and a support workload. Businesses that treat it as “a normal website with a login” usually discover the gap in month three, when renewals fail silently, expired members still see paid content and the finance team cannot reconcile what was charged.
This guide is for owners and managers deciding whether a membership model fits their business, how to price it, how to charge for it in Egypt, and what a sound technical build looks like. It is written from engineering practice and from public gateway and plugin documentation. It quotes no fees and no Kemetova prices, and every number in the worked example is labelled as an assumption.
When a membership model makes sense
Membership works when the value you deliver is repeated and cumulative. If a customer would buy once and never return, a shop or a booking form is the right tool. If they would return every week or month for something they cannot easily get elsewhere, a membership can turn that repeat demand into predictable revenue. Five patterns justify the build.
- Gated knowledge. Courses, technical libraries, templates, market reports, regulatory updates. The content is the product and access is the paywall.
- Recurring service access. A gym, a coworking space, a dive club, a clinic programme. Members buy the right to use a physical service on a schedule, and the website manages entitlement, booking and payment.
- Community and network. Professional associations, buyer clubs, developer groups. The product is who else is inside, plus a directory, events and private discussion.
- Wholesale or partner access. Trade customers who see prices, stock and documents that the public cannot. This is closer to a B2B portal than a classic membership, and the same access-control layer applies.
- Loyalty tiers. Paid or earned tiers with discounts, early access or priority service, attached to an existing shop or hospitality business.
A membership is the wrong answer when the content is thin, when you cannot produce new value every cycle, or when the audience expects to pay once. The most common failure is not technical. It is a monthly fee attached to a static PDF library, followed by a cancellation wave once members have downloaded everything. Before you spend money on a build, write down what a member receives in month one, month three and month twelve. If month twelve looks the same as month one, the model needs redesign.
Choosing a pricing and access model
Pricing structure drives both the revenue pattern and the technical complexity. Decide it before you choose a platform, because some models are cheap to run and others need real engineering.
Flat subscription
One plan, one price, billed monthly or annually. It is the simplest model to build and to explain. It suits a single clear offer such as a course library or a private community.
Tiered plans
Two to four levels with different access, for example a basic tier with the library and a premium tier with live sessions and one-to-one support. Tiers need a rule engine that maps each plan to a set of permissions, and they need upgrade and downgrade logic with proration decisions. Keep the number of tiers small. Every extra tier multiplies the test cases.
Annual with monthly option
Offering both lets price-sensitive customers start monthly while committed customers pay once a year. Annual billing improves cash flow and reduces the number of renewal events that can fail, which matters in a market where card payments are declined for reasons the merchant cannot see.
Fixed-term pass
A season pass, a 12-week programme or a one-year licence that ends on a date and does not renew automatically. This is often the better fit for Egyptian businesses with seasonal demand, such as Red Sea tourism. It also avoids the heaviest part of subscription billing, which is storing a payment method and charging it later.
Free tier plus paid tier
A free registered account that unlocks part of the content, with a paid upgrade. It builds an email audience and a conversion funnel, and it requires clear rules about what is free, what is paid and what happens to a member who lets a paid plan lapse.
Lapse rules you must decide up front
Every model needs written answers to these questions, because the software will enforce whatever you configure and nothing else.
- What happens on a failed renewal: instant loss of access, a grace period, or a retry window?
- Does the member keep content they have already downloaded or progress they have already made?
- Can a lapsed member reactivate at the old price, or do they return at the current price?
- Are refunds allowed, and within what period?
- Who owns the member data and the content created inside the community if the member leaves?
How to charge members in Egypt
Billing is where membership projects in Egypt differ most from the examples in international tutorials. The tools you read about were designed around card networks and gateways that offer managed subscription products. Local gateways exist and work, but you should check exactly what each one provides before you promise automatic renewals to your customers.
What local gateway documentation actually describes
Kashier’s public developer documentation states that it does not offer a managed subscriptions or billing-plans API. The merchant runs the billing schedule. The documented flow is: your backend creates a payment session with an agreement object describing the schedule and with card saving enabled; the customer completes the first payment on Kashier’s page; after success, Kashier sends a card token and an agreement identifier to your server webhook; your server stores both; and for each later cycle your backend calls the order endpoint with the stored token and agreement ID, marked as a continuing authorisation. The documentation recognises two agreement types, a scheduled recurring type and an unscheduled card-on-file type.
Paymob’s public documentation describes charging a saved card token by sending a server-side request to its payment endpoint, with a source identifier of type token. Its recurring-payment page says the merchant first asks Paymob’s technical contact to enable recurring payments, which provides an additional integration ID. The page does not cover scheduling or subscription logic, so the same principle applies: the gateway charges a token when you tell it to, and your system decides when and how much.
Both descriptions come to the same architecture. The gateway is a payment executor. The subscription itself, meaning plan, price, billing date, retry policy, status and access rights, lives in your own database. Read the current documentation for your chosen gateway and confirm in writing with the provider that recurring or card-on-file charging is enabled on your merchant account, on which card types, and what the customer-consent and 3-D Secure rules are for later charges. Those details change and differ by account.
Automatic renewals versus manual renewals
WooCommerce Subscriptions, the best-known WordPress subscription extension, separates the two modes clearly in its documentation. With automatic renewals, the plugin creates a renewal order on the due date and the gateway charges the saved payment method with no customer action. With manual renewals, the subscription goes on hold, the customer receives an invoice email, and they must log in and pay through checkout. The documentation notes that only some gateways support automatic renewals and that any gateway can process manual ones. It also describes an optional payment-recovery feature that retries failed automatic payments and emails the customer.
This distinction is the most useful planning tool for an Egyptian membership. If your chosen gateway has no ready-made integration with your subscription plugin, you have three realistic options.
- Manual renewal by invoice. The member receives a reminder with a payment link and pays each cycle. Revenue per member is lower in practice because some members forget, but there is no stored card and the build is simpler. Suited to annual and quarterly plans.
- Token-based automatic renewal built to the gateway API. A developer writes the scheduler, the token vault, the retry rules and the webhook handlers against the gateway documentation. This gives true automatic renewal and costs more to build and test.
- Fixed-term passes. No renewal at all. The member repurchases when the pass ends, helped by reminders.
Our companion article on connecting Paymob, Kashier or Fawry to WooCommerce or Laravel covers callbacks, idempotency and reconciliation in detail. The same discipline applies here, with one addition: a renewal that the gateway accepted but your server never recorded is a charged customer with no access, and that produces a support ticket and sometimes a chargeback.
Bank transfers and wallets
Many Egyptian customers prefer to pay by transfer or wallet. A transfer cannot be charged automatically, so it fits the manual or fixed-term models. If you accept transfers, design a reconciliation step where staff match a payment to a pending membership and activate it. Without that step, the finance team ends up activating members by hand from a spreadsheet.
The technical anatomy of a membership site
Whatever platform you choose, a membership system has the same six layers. Weakness in any one of them shows up as a business problem.
1. Identity and registration
Accounts need email verification, password reset, optional social login, and protection against fake sign-ups. Decide early whether one account can be shared by a company team or whether each seat needs its own login. Account sharing is the most common leak in paid communities, and rate limits on concurrent sessions help.
2. Plans, entitlements and access rules
A plan is a commercial object. An entitlement is a technical permission. Keep them separate: a plan grants a set of entitlements, and content is protected by entitlement, not by plan name. This lets you rename a plan, launch a new tier or run a promotion without touching every protected page. Check access on the server for every request. Hiding a menu item is not protection.
3. Billing and subscription state
A subscription should be a state machine with a short list of states, for example pending, active, past due, on hold, cancelled and expired, and a written rule for every permitted transition. Store each charge attempt, its outcome and the gateway reference. When a member disputes a charge or asks why access ended, the answer should be one database query, not an investigation.
4. Content delivery
Protected pages are the easy part. Protected files are harder. A direct link to a PDF or a video file will keep working after the membership ends unless the file is served through an authorised route, with expiring signed URLs or a streaming service that checks entitlement. For video, use a host that supports domain-restricted and token-protected playback rather than a public link.
5. Communication
Welcome sequence, renewal reminders before the due date, failed-payment notices, win-back messages after cancellation. These emails are part of the revenue engine, not decoration. For Egyptian audiences, a WhatsApp message often gets read faster than an email. We cover the options in our guide to WhatsApp on a business website, including the opt-in and template rules that apply to messages you send first.
6. Administration and reporting
Staff need to find a member, see their plan and payment history, extend access, issue a refund, add a manual payment and export a list for events. Reporting should answer five questions without a developer: how many active members, how many joined, how many cancelled, how many renewals failed, and what the recurring revenue is. If the admin area cannot answer these, the business is steering blind.
WordPress plugin, custom build or SaaS platform
Three routes are available and each fits a different stage.
Membership plugin on WordPress
Mature plugins handle registration, restriction rules, drip content and integration with WooCommerce for payments. This route is the fastest and the cheapest to start, and it suits a flat or two-tier subscription with content as the main product. Its limits appear when you need an unusual gateway, complex tier logic, deep integration with an internal system or a high volume of members. You also inherit the plugin’s update cycle and security exposure, so budget for maintenance. We discuss the trade-offs between WordPress and a custom system in WordPress or Laravel: how to choose.
Custom membership system
A Laravel application with a purpose-built subscription model gives full control over billing rules, local gateway integration, entitlements, member dashboards and API access for a mobile app. It costs more to build and requires a team that can maintain it, so it is justified when membership is the core of the business and not an add-on. A common hybrid keeps WordPress as the public marketing site and runs the member area and billing engine as a separate application. For the wider picture of dashboards and member areas, see our note on what a customer portal costs in Egypt.
Hosted SaaS community platform
Hosted platforms bundle community, courses and payments with no development. They are quick to launch. The trade-offs are limited design control, limited local payment support depending on the platform, platform fees, and a dependency on a vendor for your member data. Check whether the platform can charge in Egyptian pounds with a gateway your customers trust before you commit.
A decision rule
Start with the plugin if you are testing demand with one offer and fewer than a few hundred members. Move to a custom system when billing rules, integrations or member volume outgrow the plugin, or when the member experience must be a branded app. Do not start custom to test an idea you have not validated.
A worked example with stated assumptions
The numbers below are assumptions to show the arithmetic. They are not benchmarks and not Kemetova client data.
Assume a professional training provider sells a membership with a price P per month. They plan to acquire 40 new members per month and expect a monthly churn rate c, meaning the share of active members who cancel or fail to renew in a month. Assume c = 8%.
The expected lifetime of a member is roughly 1 divided by c, so 1 / 0.08 = 12.5 months. Revenue per member over that lifetime is about 12.5 x P, before gateway and tax costs. If the provider reduces churn from 8% to 6%, lifetime rises to about 16.7 months, an increase of one third in revenue per member, with no additional marketing spend.
Now compare with the steady-state size of the member base. With 40 new members a month and 8% monthly churn, the base settles near 40 / 0.08 = 500 active members. At 6% churn, it settles near 667. The difference of roughly 167 members comes entirely from retention work: better onboarding, renewal reminders, payment recovery and content cadence.
Involuntary churn, meaning renewals that fail because of an expired card, insufficient balance or a declined transaction, is part of c. Assume that a quarter of all churn is involuntary. Then 2 of the 8 points are payment failures. A retry schedule and a reminder sequence that recover even half of those failures reduce c from 8% to 7%, which is worth more than most acquisition campaigns. This is why billing quality is a commercial feature, and why the build should include failed-payment handling from day one.
Replace P and the churn assumptions with your own figures. If you have no history, start with a conservative churn estimate and measure real churn for 90 days before building anything expensive on top of the forecast.
Retention engineering
Churn is not decided at renewal time. It is decided in the first two weeks, when the member finds or does not find the value they paid for. Design for that window.
- Onboarding path. A first-session checklist that leads the member to one meaningful action within 24 hours: finish the first lesson, book the first session, introduce themselves.
- Usage signals. Record last login, content views and bookings per member. Members who stop using the service in the second week are the next cancellations, and a staff member can contact them before the renewal date.
- Pre-renewal reminders. For annual plans, a notice a few weeks before charge, then a second notice a few days before. Reminders reduce surprise cancellations and chargebacks, and some card networks and local rules expect clear notice for recurring charges.
- Payment recovery. A retry schedule over several days, an email and message asking the member to update their payment method, and a grace period during which access continues.
- Cancellation flow. Offer a pause, a downgrade or a cheaper tier before final cancellation, and ask for a reason. The reason field is the cheapest product research you will ever collect.
Compliance and data handling
A membership site holds personal data, payment references and sometimes sensitive details such as health or professional credentials. Egypt’s personal data protection law, Law 151 of 2020, applies to how you collect, store and process that data. We keep this section general: consult a qualified lawyer on consent wording, retention periods, cross-border transfers when your servers or email tools are outside Egypt, and the rules for marketing messages.
On the technical side, the baseline is straightforward and should not be skipped. Never store raw card numbers on your own server; use the gateway’s hosted page or tokenisation so that card data never reaches you. Store gateway tokens encrypted and restrict who can read them. Log administrator actions. Back up the member database and test a restore. Write terms of service that state what the member buys, the renewal rules, the cancellation method and the refund policy, and show them at checkout with a recorded acceptance.
Build quality checklist
Whether you buy a plugin or commission a custom system, test these scenarios before launch. Each one has caused a real incident on some membership site.
- A member pays and the confirmation callback arrives twice. The system must activate once and record one payment.
- A member pays and the callback never arrives. A reconciliation job must find the payment through the gateway and activate the account.
- A renewal is declined. The member sees a clear notice, access follows the grace rule, and the retry runs on schedule.
- A member upgrades mid-cycle. The charge, the new entitlements and the next billing date all match the written proration rule.
- A member cancels. Access continues until the end of the paid period, and no further charge is attempted.
- A direct file link is shared with a non-member. The link must fail or expire.
- An administrator extends a member’s access by hand. The action is logged with the staff member’s name and the reason.
- Arabic and English versions of every email, invoice and page display correctly, including right-to-left layout in the checkout and the member dashboard.
- The site is slow under load on a launch day when many members log in at once. Member pages are personalised and often cannot be fully cached, so test the logged-in experience as well as the public pages.
Questions to put to any supplier
Ask these before you sign a scope. The answers show whether the supplier has built subscription billing before or is planning to learn on your budget.
- Which gateway will charge renewals, and have you read its recurring-payment documentation for my merchant account?
- Will renewals be automatic, by invoice, or fixed-term, and why?
- How do you handle a webhook that arrives twice, late or not at all?
- Where are card tokens stored and who can access them?
- How are protected files and videos served so links cannot be shared?
- What does the admin screen show about failed renewals, and can staff fix them without a developer?
- Who maintains the system after launch, and how are updates tested before they reach live members?
A sensible rollout order
Launch the smallest version that tests whether people will pay: one plan, one payment method that you have verified end to end, one protected content area and a manual process behind the scenes for everything else. Invite a founding group of members at a discount in exchange for feedback. Measure activation in the first week, usage in the second, and the first renewal result in the following month. Only then automate the manual steps that cost the most staff time, add tiers, add automatic renewals if you started with invoices, and build the member dashboard. A membership that earns its first hundred paying members on a simple system has a stronger case for a custom build than a forecast ever provides.
If you are weighing a membership model for your business, our membership platform development page describes the scope we cover, and the engineering questions above are the ones we ask in the first scoping call.