A membership cancellation policy should state how a member requests cancellation, when billing stops, how long access remains, what happens to pending benefits and how confirmation is delivered. The operational workflow must produce the same answer as the policy every time.
This is a process template, not legal advice. Subscription, renewal, notice, cooling-off and refund rules vary by country, customer type and offer. Have qualified counsel review the final terms for the markets you serve.
Define Five Dates
| Date | Meaning |
|---|---|
| Request date | When the member submits cancellation |
| Current paid-through date | End of access already funded |
| Next billing date | Next scheduled collection if nothing changes |
| Effective cancellation date | Date the membership changes to ended |
| Access-lock date | When protected content stops opening |
These dates may coincide, but never assume they do. An “immediate cancellation” could mean stop future renewal while access continues through a paid period, or it could mean end service now. Use explicit language.
Choose Immediate or Notice-Period Handling
PayRequest supports product-level cancellation modes. Its current cancellation-request documentation describes immediate cancellation or a request flow with a configurable notice period, reason collection and an effective date.
Use a notice period only when it matches the agreement and applicable rules. Do not add friction merely to prevent cancellation. Members should be able to find the route, understand the consequence and receive confirmation.
Build the Cancellation State Record
Record one lifecycle rather than relying on an inbox thread:
- Active: membership renews and access is open.
- Cancellation requested: timestamp, reason and member message recorded.
- Pending end: effective date visible; duplicate requests blocked.
- Withdrawn: request closed and membership continues, when allowed.
- Ended: future collection stopped and access changed on the defined date.
Keep refund state separate. Cancellation controls future service and renewal; a refund changes a past payment. One does not automatically imply the other.
Use a Confirmation Template
Send a durable confirmation immediately after the request:
Subject: Cancellation received for [membership name]
“We received your request on [request date]. Your membership is paid through [date]. No further renewal is scheduled after [date]. Member access remains available until [access-lock date]. [Outstanding benefit/refund statement]. You can view the request or contact us at [route].”
Only include a withdrawal option when it actually exists. Never send a retention offer that hides or delays the cancellation confirmation.
Map Billing to Protected Access
For PayRequest Page memberships, active and trial members can open members-only posts. A cancellation can retain access while the underlying subscription remains active through the paid period; when membership ends, protected access locks.
Test the boundary with a separate customer account. Open a protected post before cancellation, immediately after the request, one day before the effective date and after the end. Confirm the visible message always matches the real state.
The PayRequest customer portal lets customers view subscriptions and, where self-management is enabled, pause, resume or cancel them. Decide which controls are available per product and document the support path for exceptions.
Handle Pending Benefits Explicitly
List benefits that may outlive billing: scheduled calls, mailed goods, event access, downloadable resources or moderation privileges. For each, define whether it remains available, is fulfilled, is credited or ends with access. Do not invent the answer after a valuable member cancels.
Protected posts are different from files a customer lawfully downloaded during an active period. State what remains in the customer's possession and what requires live membership access.
Run the Cancellation Red-Team
Test at least these cases:
- cancellation one day after renewal;
- cancellation one day before renewal;
- cancellation during trial;
- withdrawn cancellation;
- failed payment while cancellation is pending;
- admin cancellation and refund as separate actions.
For each case, compare checkout promise, policy, portal dates, provider billing, access and email confirmation. Fix any disagreement before launch.
Use PayRequest Memberships for the recurring membership and cancellation requests for a structured member-initiated workflow. Start with one test membership and verify every state before accepting customers.
