joshswebservices

PayGate Content Restriction lets you create membership tiers, restrict any post or page to specific tiers, and process payments via Stripe Checkout — all from within WordPress without any external middleware.
Key Features:
<ul>
<li>Create unlimited membership tiers with custom pricing and features</li>
<li>Restrict individual posts, pages, or custom post types</li>
<li>Three paywall designs: Modern, Minimal, and Classic</li>
<li>Stripe-native payments (Checkout Sessions + Subscriptions)</li>
<li>Real Stripe webhook handling with signature verification</li>
<li>Admin member management dashboard</li>
<li>Analytics dashboard with conversion charts</li>
<li>Bulk content restriction tools</li>
<li>Member self-service dashboard (view/cancel subscription)</li>
<li>Transactional email notifications (welcome, cancellation, payment failed)</li>
<li>Theme template override support</li>
<li>WP-CLI demo seeder for testing</li>
</ul>
Paywall Templates:
<ul>
<li>Modern — Card with blur fade-in effect and tier grid</li>
<li>Minimal — Clean HR divider with stacked full-width CTA buttons</li>
<li>Classic — Badge icon, tier cards in flex row, “Most Popular” label</li>
</ul>
No dependencies on page builders, shortcode soup, or external services beyond Stripe.
<h3>External Services</h3>
This plugin connects to the following external services:
<h4>Stripe</h4>
PayGate Content Restriction uses Stripe to process payments and manage subscriptions.
<ul>
<li>What data is sent: When a user subscribes, their WordPress user ID, email address, and selected membership tier are used to create a Stripe Customer and initiate a Checkout Session. Stripe receives whatever billing information the user enters during checkout.</li>
<li>When it is sent: Only when a logged-in user clicks a “Get Access” or “Subscribe” button to initiate checkout, or when a Stripe webhook event is received and verified.</li>
<li>Stripe’s terms of service: https://stripe.com/legal</li>
<li>Stripe’s privacy policy: https://stripe.com/privacy</li>
</ul>
<h4>Freemius (Pro version only)</h4>
The Pro version of this plugin uses Freemius for license management and automatic updates.
<ul>
<li>What data is sent: WordPress site URL, plugin version, and (with user consent) basic site and admin contact information for license activation.</li>
<li>When it is sent: Only when the Pro version is active and a license is being activated or checked.</li>
<li>Freemius terms of service: https://freemius.com/terms/</li>
<li>Freemius privacy policy: https://freemius.com/privacy/</li>
</ul>

PayGate Content Restriction

Restrict post and page content behind membership tiers with Stripe-native payments. No page builders needed.

meceware

<a href="https://www.meceware.com/docs/block-permissions-for-gutenberg/" rel="nofollow ugc">Full Documentation</a>
<h3>How To Use</h3>
<ul>
<li>Activate ‘Block Permissions’ plugin.</li>
<li>Edit any page with Gutenberg editor.</li>
<li>If Block Permission is chosen for ‘Show’, the block content will be shown if the settings are validated. Otherwise block content will be hidden.</li>
</ul>
<h4>Show</h4>
<ul>
<li>
If ‘Everyone’ is selected as the permission, the block content will be shown for everyone.
</li>
<li>
If ‘Members’ is selected as the permission, the block content will be shown for the logged in users.
</li>
<li>
If ‘Members with Selected User Roles’ is selected as the permission, the block content will be shown only for the members with specified user roles.
</li>
<li>
If ‘Selected Users’ is selected as the permission, the block content will be shown only to the specified users.
</li>
<li>
If ‘Selected Devices’ is selected as the permission, the block content will be shown for the specified devices, such as Desktops, Phones and/or Tablets.
</li>
<li>
If ‘Date Range’ is selected as the permission, the block content will be shown between the specified dates.
</li>
<li>
If ‘Time Range’ is selected as the permission, the block content will be shown between the specified times.
</li>
<li>
If ‘Day Of Week’ is selected as the permission, the block content will be shown on the specified days.
</li>
<li>
If ‘PHP Function’ is selected as the permission, the block content will be shown according to the return value of the specified PHP function.
</li>
</ul>
<h4>Hide</h4>
<ul>
<li>
If ‘Everyone’ is selected as the permission, the block content will be hidden from everyone.
</li>
<li>
If ‘Members’ is selected as the permission, the block content will be hidden from the logged in users.
</li>
<li>
If ‘Members with Selected User Roles’ is selected as the permission, the block content will be hidden from the members with specified user roles.
</li>
<li>
If ‘Selected Users’ is selected as the permission, the block content will be hidden from the specified users.
</li>
<li>
If ‘Selected Devices’ is selected as the permission, the block content will be hidden from the specified devices, such as Desktops, Phones and/or Tablets.
</li>
<li>
If ‘Date Range’ is selected as the permission, the block content will be hidden between the specified dates.
</li>
<li>
If ‘Time Range’ is selected as the permission, the block content will be hidden between the specified times.
</li>
<li>
If ‘Day Of Week’ is selected as the permission, the block content will be hidden on the specified days.
</li>
<li>
If ‘PHP Function’ is selected as the permission, the block content will be hidden according to the return value of the specified PHP function.
</li>
</ul>

Block Permissions

Show Gutenberg editor blocks only to target audience depending on their user attributes such as user role, log in information and user names.

PayGate Content Restriction vs Block Permissions