PostGate – Paywall, Membership & Stripe Subscriptions

A WordPress paywall plugin restricts access to selected content until a visitor meets a requirement such as logging in, making a one-time purchase, or having an active subscription. PostGate supports each of these access models.

Install PostGate, connect Stripe, configure the webhook, sync a product, and choose the content to protect. You can add a paywall to the entire site, a post type, category, taxonomy, individual post or page, or selected Gutenberg blocks.

PostGate lets you monetize and sell content on WordPress through individual article payments, recurring subscriptions, or both options on the same paywall. You can also restrict content to logged-in users without requiring payment.

Yes. Assign a one-time Stripe price to a post or page to sell it individually. After Stripe confirms the payment, PostGate grants the WordPress user access to the paid content.

Yes. PostGate supports a pay-per-post model by assigning a one-time Stripe price to an individual post or page. You can also offer a recurring subscription as an alternative to purchasing that article separately.

Yes. A paywall can display one-time purchase options, recurring subscription options, or both. Products and billing intervals are configured in Stripe and synchronized with PostGate.

PostGate supports recurring subscriptions, login-only content, role-based access, and membership-style content protection. Its primary focus is paywalls and paid content rather than member directories, social communities, profiles, or other features found in a complete membership plugin.

You can create a subscription-based website where registered users pay for access to protected content. If your membership website mainly needs paid articles, premium categories, or full-site subscription access, PostGate may provide a simpler setup than a traditional membership platform.

PostGate can restrict content across an entire site, supported post types, posts, pages, categories, taxonomies, and individual Gutenberg blocks. Post-level rules can override broader site-wide or category content restriction.

Yes. Add the PostGate Lock Block in the WordPress Block Editor and place the protected blocks inside it. Content outside the Lock Block remains public.

PostGate can show an indexable preview based on a selected number of paragraphs or words while the premium content remains protected. No paywall plugin can guarantee rankings, so the public teaser should be useful, descriptive, and consistent with what readers receive after purchase.

PostGate includes native Gutenberg sidebar controls and a Lock Block for block-level paywalls. Post and page restrictions can work with builders such as Elementor, Divi, and Beaver Builder when they use standard WordPress content rendering. Test your theme and page builder before accepting live payments.

Yes. A customer must register or log in so PostGate can associate the purchase or subscription with the correct WordPress user and restore access on future visits.

Yes. Enable Google Sign-In in Settings > Integrations and configure your Google OAuth credentials. The Google login button appears on PostGate login gates and paywalls and on the native WordPress login and registration forms. WordPress password login remains available. Google is the supported social login provider in this version.

Yes. Create a coupon and a linked promotion code in Stripe, then enable Allow promotion codes in Settings > Payments > Products. Customers can enter discount codes in new Stripe Checkout sessions for one-time purchases and subscriptions. Stripe determines whether the code is eligible for the selected purchase.

Stripe is required for paid-content purchases and subscriptions. Login-only content restriction can be used without a payment. Stripe availability and Connect capabilities vary by country.

PostGate uses the payment methods and currencies available to the connected Stripe account and selected Stripe Checkout configuration. Availability depends on the account country, business type, currency, and capabilities.

Yes. Use PostGate and Stripe Sandbox mode to test products, Checkout, webhooks, purchases, subscriptions, and content access without processing live payments.

PostGate is free to download and install from WordPress.org. A 5% PostGate platform fee applies to successful transactions, in addition to Stripe processing fees. Stripe fees depend on the connected account and country.

Stripe sends a supported webhook event to PostGate. PostGate then revokes the access associated with the canceled subscription according to the recorded order and content rules.

For supported Stripe refund events, PostGate updates the related order and revokes the content access associated with the refunded payment.

Yes. Choose a Compact or Classic template, customize the badge, heading, description, buttons, login message, and surrounding HTML, or override PostGate templates in your theme.

It can, but logged-in and personalized paid-content pages should not be served from a shared public cache. Confirm that your caching plugin excludes logged-in users and test purchase, login, cancellation, and access flows before launch.

No. PostGate connects directly to Stripe so you can sell paid articles and recurring access to premium content without WooCommerce or a separate shopping cart.