Almost every guide about Ghost memberships, including most of ours, is about getting somebody in. Connect a provider, map a product, watch a buyer become a member.
The other half gets far less attention, and it is the half that decides whether your paywall means anything. Somebody cancels. What happens, how fast, and how do you check it actually happened?
The short answer
The provider sends a cancellation event. PayGlue takes the access off the Ghost member and leaves everything else alone. The next time that person loads a paid post, the paywall is back.
For an immediate cancellation the whole thing takes seconds. There is no nightly job involved and nothing to click.
What actually comes off
A Ghost member created by PayGlue carries a small set of labels and a note. On a cancellation, three things change and one thing does not.
| Before | After | |
|---|---|---|
| Status label | payglue-active |
payglue-ended |
| Provider label | payglue-provider:polar |
unchanged |
| Comped flag | on, if Stripe is connected | off |
| The member | exists | still exists |
The status label flips rather than disappearing, which matters more than it sounds. A member with no status label at all could be somebody who cancelled, somebody whose purchase never granted anything, or somebody who was never a customer. Three very different situations that used to look identical.
The provider label stays because it is a different fact. Months later, “this person left” and “this person came through Ghost’s Ko-fi connection” are both things you want to know, and losing the second one when the first happens throws away the only record of where they came from.
The note keeps the story
The member note records the purchase and, once there is one, the ending:
Direct via PayGlue | Provider: polar
Product: e910af3d-e1d7-450b-8596-2b17a309eab7
Order: 2026-08-14 | Event: 5e38bc88-0ff7-4b56-a379-78f058f853a6
Ended: 2026-08-14 | Event: c583ab77-e7d3-4b77-b33c-b63ba22c28b7
Two dates and two event references, which is what you need when somebody writes in three months later asking why they cannot read anything. You can answer without opening the provider’s dashboard.
If the same person buys again, the note is rewritten for the new purchase and the ending line goes with it. A stale “Ended” line under an active membership would be worse than no line at all.
Not every provider tells you
This is the part that belongs at the top rather than in a troubleshooting section, because it decides whether a provider suits you at all.
Ko-fi has no cancellation webhook. A supporter who stops supporting generates nothing. PayGlue cannot revoke what it is never told about, so their access stays until you remove it by hand. Ko-fi is a good fit for one-off support and a poor fit for recurring access that has to end reliably.
Everything else in the list reports endings, though they use different words for them:
| Provider | What ends access |
|---|---|
| Polar | cancellation and revocation |
| Lemon Squeezy | cancelled, paused, expired |
| Paddle | cancelled, paused |
| PayPal | cancelled, suspended, expired |
| Creem | cancelled, expired |
| Gumroad | cancelled, subscription ended |
| Patreon | pledge deleted |
| Ko-fi | nothing |
Pause and suspend end access on purpose. Both are somebody stopping the arrangement rather than a payment failing, and both are reversible: when the subscription resumes, the resume event grants the access back with no work from you.
An overdue or failed payment is a different thing entirely and does not remove anybody.
Cancelled now, or cancelled at the end of the month
Most providers offer both, and they mean different things.
An immediate cancellation ends the subscription now, and the access goes with it. A cancellation at the end of the paid period means the reader keeps what they paid for until that date arrives.
PayGlue handles the second case by doing nothing yet. The cancellation event carries a flag saying the subscription runs until a date, and it is skipped rather than acted on. When the date arrives the provider sends a second event, and that one revokes.
This trips people up during testing, because you cancel, refresh, and the reader still has access. That is not a bug, and it has its own article.
Checking that it worked
Three places, in the order they are useful.
The event log. The cancellation should appear as processed. If it says skipped, look at whether it was a period-end cancellation. If it says failed, the delivery to Ghost is the problem rather than the cancellation.
The Ghost member. payglue-active gone, payglue-ended present, comped off if your site has Stripe connected.
The site itself. Log in as that member and load a paid post. The paywall should be back. This is the only one of the three that tests the whole chain, and it is the one worth doing after any change to your setup.
What the reader sees
Nothing dramatic, and no email from PayGlue. They lose access to paid posts, keep their account and keep receiving whichever newsletters they were subscribed to, because those are Ghost settings and a cancellation does not touch them.
If they cancelled themselves, the provider has usually confirmed it already. If the subscription lapsed, the provider is the one that told them.
