License Status and Plan

Your license drives everything in Benecaster’s paid tier — subscriber tokens, private feeds, membership plugin bridges, and the notification system. This page covers what the status indicators mean, how to read the Account tab, and what happens when something needs attention.

The Account Tab

Go to Benecaster → Settings → Account to see your full license state at a glance.

Shows hides the upgrade link on Multi-Show and Studio (no show limit).

Subscriber Usage Bar

The usage bar fills as your paying subscriber count approaches your plan limit. At 80% it turns amber and shows an upgrade prompt. At 100% it turns blue — on Launch the message reads “You’ll automatically move to Starter at your next billing period”; on paid plans it reads “Upgrade to [next plan] to keep growing →”.

The usage bar is hidden on Pro, Multi-Show, and Studio — those plans have no paying subscriber limit.

Status Values

Active

Your license is valid, validated within the last 24 hours, and all premium features are running. No action needed.

Expiring Soon

Your subscription renews within the next 30 days and the renewal payment has not been taken yet. Nothing is wrong and there is nothing to do — this status simply means the renewal date is close. Subscriptions renew automatically; if the payment fails when it is attempted, Benecaster will tell you then.

Expired / Cancelled / Suspended

These three states share the same plugin behavior (see Grace Period Behavior below). They differ in why they occurred:

• Expired — the subscription lapsed (failed payment not recovered, or annual subscription not renewed)
• Cancelled — you cancelled the subscription at benecaster.com
• Suspended — a payment failed and was not resolved. Subscribers are unaffected for the first 30 days — their private feed URLs continue to deliver their tier-specific content normally. No notification is sent to them. After the 30-day window closes without recovery, subscriber tokens are deactivated and private feeds stop working entirely — they do not fall back to your public feed. Your public feed itself keeps working normally. Recovery via billing update at any point restores full private access on the next daily license validation. See Payment Failure and Recovery → for the full timeline and reminder cadence.

In all three cases, visit benecaster.com/my-account/ to resolve.

Unlicensed

No license key is activated on this site. The plugin runs as the WordPress.org free version — public feed only, no subscriber management.

Grace Period Behavior

The details differ by status, but all three inactive states share some behaviors:

New token generation stops in all three states. New subscribers who sign up through your membership plugin will not receive a feed URL until the license is restored.

All your data is preserved in all three states. Subscriber tokens, episodes, show settings, and tier mappings are completely untouched. Nothing is deleted.

A persistent non-dismissible banner appears across all Benecaster admin screens explaining the license is inactive, with a link to your account to resolve it.

Your public feed keeps working throughout, and after. This is the part worth being clear about, because “private feeds stop working” reads worse than it is. When a license lapses, the site falls back to exactly the free WordPress.org version of Benecaster — your episodes, your public RSS feed, your listener support links, all running normally. What stops is the paid part: the token-specific feed URLs that deliver subscriber-only content.

You lose subscriber delivery. You do not lose your podcast, your episodes, or your public audience.

And it is a state, not a conversion — renewing puts everything back. Nothing is downgraded, deleted, or migrated. Your subscriber records, tokens, tier mappings, episodes and settings all stay exactly where they are; the tokens are switched off, not destroyed. Renew or reactivate and the next validation check turns them back on, on the same feed URLs your subscribers already have.

This works whether you resolve it on day 5 or day 45. There is no point after which recovery stops being possible — a license that lapsed months ago restores in full the moment it is brought current. Your subscribers do not need to do anything, and you do not need to reissue tokens or resend welcome emails.

The one exception is a subscriber whose podcast app gave up and removed the show during the cutoff. Their URL works again, but the app no longer holds it, so they will need to re-add it. After a long cutoff, tell your subscribers rather than waiting for them to notice.

Suspended (payment failed)

Private subscriber feeds continue working normally for 30 days from the first payment-failed response. Subscribers receive no notification and see no change. After 30 days without recovery, subscriber access is blocked — tokens stop delivering content entirely until the license is restored. Your public feed carries on unaffected.

See Payment Failure and Recovery → for the full timeline, the reminder email cadence, and recovery steps.

Expired / Cancelled

When a license expires or is cancelled, Benecaster gives existing subscribers access until the end of the current billing period. After that, their tokens are deactivated and private feeds stop working — they do not fall back to your public feed. Your public feed itself is untouched and keeps publishing.

Subscribers will notice: their podcast app reports an error or an empty feed rather than quietly showing fewer episodes. That is deliberate. Someone whose paid access has ended should be told, not moved onto the free tier without knowing it. Episodes they already downloaded stay on their device.

⚠ Stop your subscribers’ billing yourself — Benecaster will not do it for you. This is the single most expensive thing to get wrong when winding a show down, and it applies to every state where private feeds stop: cancellation, expiry, and a payment failure that runs past day 30.

Your subscribers keep being charged. Whatever takes their money has no idea your license lapsed and will bill on its own schedule indefinitely. They would be paying full price for a feed that has stopped working — and the first you hear of it is likely to be a refund request, or a chargeback.

Do this before you cancel, not after:

• External membership plugin (Restrict Content Pro, Paid Memberships Pro, WooCommerce Subscriptions, Patreon, and the rest) — cancel or pause the subscriptions there. Benecaster cannot reach into another plugin’s billing, and there is no setting that changes that.
• Built-in membership — cancel or pause them in Benecaster → Memberships. Note that this is still a manual step today: taking your license out of good standing stops subscriber feeds, but it does not stop subscriber payments.

Do it in this order: stop the billing first, then cancel your Benecaster license. The reverse leaves a window where subscribers are paying for feeds that have already gone dark.

Restoring full access: Renew or reactivate your license at benecaster.com/my-account/. The next validation check (automatic or triggered manually from Settings → Account) restores private feed delivery and new token generation with no other steps required.

Validation Failure — When the Server Can’t Be Reached

Benecaster runs a validation check once daily via WordPress’s built-in cron. If the license server is unreachable — a network outage, a firewall rule, or a problem on our side — Benecaster keeps operating normally rather than assuming the worst. This is the fail-open design: a connectivity issue is not a license issue, and a temporary outage should never cost you your subscribers.

Fail-open has a limit, though, and it is 30 days. See below for what happens at each stage. On low-traffic sites the daily check can run several hours late — see Cron isn’t firing on time → if validations feel delayed.

Days 1–7: The failure is logged locally but nothing changes. Private feeds continue serving tier content as normal.

Day 8 onward: A warning appears in your Benecaster admin telling you how many days the license server has been unreachable and that features will be restricted after 30 days. You can dismiss it, but it comes back every 7 days while the problem persists.

This warning is the one to act on. It almost always means something on your side is blocking outbound HTTPS — a firewall rule, a security plugin, a host-level egress restriction, or a DNS problem. Benecaster cannot fix it from here.

Days 15–29: From day 15 each daily check also has a chance of alerting the Benecaster team, so a sustained outage usually reaches us within a few days of that point. We may reach out to help you diagnose it.

Day 30: If validation has not succeeded in 30 consecutive days, premium features are restricted, new token generation stops, and private feeds stop working. Subscribers do not fall back to your public feed. The site drops to the free WordPress.org version of Benecaster — your public feed and episodes keep running as normal.

Thirty days is a deliberate limit rather than a technical one. Benecaster cannot tell the difference between a site that genuinely cannot reach us and a site that has been configured not to — so an indefinite grace period would simply be a way to run a paid plan without paying for it. A month of full service on an unverified license is generous; unlimited is not something we can offer.

In practice this should never reach you by surprise. You will have had the admin warning since day 8, repeating weekly, naming the 30-day consequence. Everything is restored by the next successful validation — no data is lost, no feed URL changes, and subscribers need do nothing.

Recovering: Once your site can reach the license server again, the next validation check clears all failure state and fully restores operation. Trigger it manually from Settings → Account → Validate now if you want immediate confirmation.

This is distinct from an explicit "invalid" response from the server, which takes effect immediately regardless of how many days have passed.

The Notification Center

The bell icon in the Benecaster top bar is your notification center. A badge appears when there are unread notices. Click to open the slide-in panel.

Notices fall into five severity tiers:

Dismiss individual notices with the ✕ on each card, or use ✓ Dismiss all to clear all dismissible notices at once. Critical notices have no dismiss button — they stay until the condition resolves.

Persistent Banners

Critical notices also appear as a full-width red banner between the Benecaster top bar and the page content, visible on every Benecaster screen. A banner with no close button cannot be dismissed — the condition itself must be resolved first.

Specific Warnings

Suspicious Subscriber Count Drop

If the license server detects an unusually large drop in your subscriber count, a persistent amber warning appears in the notification panel:

“Unusual subscriber count change detected — see benecaster.com/my-account/ for details.”

This notice is non-dismissible and clears automatically on the next successful validation once the license server resolves the flag. Common causes: a bulk membership cancellation batch, a bridge misconfiguration that temporarily reported zero active memberships, or running a large data cleanup. Contact support if you’re not sure what triggered it.

Downgrade Not Yet Eligible

After you upgrade from Launch to a paid plan, downgrading back to Launch requires your subscriber count to have remained at or below 10 for 30 continuous days. If you attempt a downgrade before that condition is met, a warning notice explains when eligibility is expected. Contact support if you believe this is an error.

Show Limit Reached

If you try to create a new show but have already reached your plan’s show limit, a persistent admin notice appears:

“Your show limit has been reached — you can’t create another show on this plan. Upgrade your plan at benecaster.com.”

Feed delivery and subscriber access on your existing shows are unaffected — only the attempt to create a new show is blocked. Upgrade to Multi-Show or Studio for more shows at benecaster.com/my-account/.

See also: Show Limits and Multi-Site Use →

80% Upgrade Notices

Two independent notices appear as you approach your plan limits:

Paying subscriber notice: Appears when paying subscribers reach 80% of your subscriber limit. Shows your current count and limit with an upgrade link. Has a 30-day per-admin-user cooldown — dismissing it on one admin account doesn’t affect others. Reappears after 30 days if the condition persists.

Total token notice: Appears when the combined count of paying and free subscribers reaches 80% of your total token cap. This is separate from the subscriber notice — both can appear simultaneously and each is dismissible independently.

Checking License Status Manually

To trigger an immediate validation check, go to Settings → Account and click Validate now. Use this after renewing an expired license or fixing a connectivity issue — the page updates immediately with the current license state.