PostGate – Paywall, Membership & Stripe Subscriptions

WordPress Paywall, Membership, and Content Restriction Plugin

PostGate is a WordPress paywall and content restriction plugin for selling premium content with Stripe. Create paid articles, subscription-based content, members-only sections, or a complete paywall without WooCommerce or a complex membership platform.

Accept one-time Stripe payments or recurring subscriptions and automatically give customers access to protected content after payment.

Protect an entire website, category, taxonomy, post, page, custom post type, or individual Gutenberg blocks. You can also create login-only content for registered users without requiring payment.

PostGate is designed for creators, bloggers, publishers, educators, consultants, and anyone who wants a simple way to monetize WordPress content while keeping their website and audience under their control.

PostGate Quick Overview

Monetize WordPress Content with Stripe

Connect your Stripe account, sync products and prices, and offer one-time purchases and recurring subscriptions on the same paywall. Stripe-hosted Checkout handles payment details; PostGate uses verified webhooks to update orders and content access in WordPress. Test in Sandbox mode before switching to live payments.

Payment methods, currencies, processing fees, and Stripe Connect capabilities depend on the connected account’s country and configuration. PostGate does not store card details on your WordPress server.

Who Is PostGate For?

PostGate is for creators, bloggers, publishers, educators, consultants, and researchers who want to:

• Sell individual articles, tutorials, reports, or other premium content.
• Offer monthly or annual access to a subscriber-only publication.
• Protect a premium category or collection of related posts.
• Combine pay-per-article purchases with subscriptions.
• Require registration for selected content without charging readers.

Flexible Content Restriction

Choose access rules for your site, supported post types, categories and taxonomies, or individual posts and pages. Post-level rules can override broader rules. Use the PostGate Lock Block to protect selected Gutenberg blocks while leaving the rest public. Login-only protection and role-based bypass are also available.

Sell Paid Articles with One-Time Payments

Assign a one-time Stripe price to a post or page to create a pay-per-post offer. Readers register or log in, complete Checkout, and receive access to that content after successful payment confirmation. Use different products and prices for different articles or resources.

Recurring Subscriptions and Membership Access

Use Stripe recurring prices for subscriber-only articles, categories, or a site-wide paywall. Show one or more subscription options alongside individual purchases. PostGate grants subscription access after confirmed checkout and updates access following supported cancellation and refund events. Subscribers can open Stripe Billing Portal to manage payment details, invoices, and cancellation options according to your Stripe setup.

PostGate supports paid membership access to content. It does not include community profiles or member directories.

SEO-Friendly Content Previews

Show a public introduction before the paywall using a paragraph or word limit, configured globally or per item. This gives visitors context and can leave descriptive content available to search engines; it does not guarantee indexing or rankings. Write a preview that accurately reflects the protected article.

Gutenberg and WordPress-Native Controls

Configure post and page paywalls in the Block Editor sidebar, or place selected content inside the PostGate Lock Block. Access is tied to WordPress user accounts, with role-based bypass where configured. Post and page restrictions can work with builders that use standard WordPress content rendering; the Lock Block requires the Block Editor. Test your theme, page builder, and cache setup with the full purchase flow.

Google Sign-In and Stripe Promotion Codes

Optional Google Sign-In adds a Google button to PostGate login gates and native WordPress login or registration forms while keeping password login available. Configure the Google OAuth credentials in Settings > Integrations > Google Sign-In; HTTPS is required. Readers still need to purchase or subscribe to access paid content.

To offer a discount, create a coupon and linked promotion code in Stripe, then enable promotion codes for the applicable Live or Sandbox environment in Settings > Payments > Products. Readers enter eligible codes in Stripe Checkout. Stripe applies its own code and product restrictions.

Customizable WordPress Paywalls

Choose Compact or Classic layouts and customize the badge, heading, description, buttons, login messages, public preview, and HTML around product options. Developers can override templates in a theme for deeper changes.

Customer, Subscription, and Access Management

Review orders, statuses, revenue, and access grants in WordPress. PostGate includes purchase and manual-order emails, protected-content update notifications for subscribers, and Stripe Billing Portal access for subscription self-service. Notification sender details and messages are configurable.

Developer Friendly

PostGate includes theme template overrides, WordPress actions and filters, REST API endpoints, and support for eligible custom post types and taxonomies. Its administration interface uses WordPress capabilities and familiar publishing workflows.

How PostGate Works

1. Install PostGate and connect your Stripe account in Sandbox mode.
2. Configure the Stripe webhook endpoint and sync one-time or recurring products.
3. Choose the site, category, taxonomy, post, page, or Gutenberg blocks to protect.
4. Assign prices, configure the public preview, and complete a test checkout.
5. Confirm that access works, then switch PostGate and Stripe to live mode.

Documentation and Support

• Read the PostGate Quick Start Guide
• Browse PostGate Documentation
• Ask for help in the WordPress.org Support Forum

External Services

PostGate connects to Stripe when an administrator connects an account, synchronizes products, creates a Checkout Session, or processes payment, refund, and subscription events. Stripe receives the account, product, price, customer, and transaction data needed for the requested operation. Stripe is required for paid-content features; login-only content restriction does not require a payment.

PostGate also communicates with a connection service operated by QodeSphere to initiate and complete the Stripe Connect OAuth flow. During this administrator-initiated connection, the site URL and Stripe authorization data needed to return the connection to WordPress may be transmitted. This service is used only when an administrator chooses to connect a Stripe account.

• Stripe Services Agreement
• Stripe Connected Account Agreement
• Stripe Privacy Policy
• PostGate Documentation

When Google Sign-In is enabled and a user chooses to sign in or link an account, PostGate redirects the browser to Google and exchanges the authorization code with Google on the server. Google receives the OAuth client ID, callback URL, requested scopes (openid, email, profile), state and nonce; the server-side token exchange also sends the client secret and authorization code. PostGate retrieves Google’s public signing keys to verify identity tokens. Google returns the account identifier, verified email address and profile information. PostGate stores the Google account identifier on the WordPress user; new accounts also use the email address, display name, and first and last names when provided. Access and refresh tokens are not stored. Google is optional; password login remains available.

• Google Terms of Service
• Google Privacy Policy