Description
PaywallProject helps publishers sell access to protected content with Stripe-powered subscriptions, gifts, coupons, subscriber management, and reporting.
Learn more, read the documentation and get support at paywallproject.com.
Payments and fees
Payments go through Connect with Stripe. Connect your Stripe account in one click, with no API keys or webhooks to set up. PaywallProject charges a platform fee of 10% on each payment, on top of Stripe’s own fees. The fee is shown on the Connect button before you agree to it.
Gift articles
Let subscribers share single stories with people who don’t subscribe. Turn it on per level under Levels → Gift articles and set how many gifts each subscriber gets a month. Each gift is a link that unlocks one article for one reader, once, and expires after 72 hours. A level gifts every article by default. You can limit it to some categories, or allow every category except some. A category includes its subcategories. When a level is limited to some categories, posts with no category can’t be gifted. When it allows every category except some, posts with no category can be gifted, and so can post types without categories. Gift links already sent keep working until they expire, even if you change the categories.
AI Shield
Keep AI companies from crawling your stories while Google, Bing and other search engines index your site as before. Turn it on under Settings → AI Shield and PaywallProject adds a rule for each AI crawler to your robots.txt — training crawlers such as GPTBot, ClaudeBot and CCBot, and AI search and assistant fetchers such as ChatGPT-User and PerplexityBot. robots.txt only stops crawlers that respect it, so the tab also gives you a ready-to-copy Cloudflare WAF rule that blocks the same crawlers at the edge, which works even when your pages are served from a full-page cache. Untick any crawler you want to let in. Googlebot, Bingbot, Applebot and DuckDuckBot are never blocked. Off by default.
AI and MCP
Connect your staff’s MCP client to your own site to read subscriber data and run support actions. MCP needs WordPress 6.9 or newer and the separate MCP Adapter plugin. Tested with MCP Adapter 0.7.1. Each staff member connects with an Application Password and the permissions of their WordPress account. Write tools allow 30 attempts per minute per Application Password. Read tools do not use the write allowance.
Open PaywallProject → Settings → AI and MCP to set it up in three steps: install the MCP Adapter with one click, connect, and copy the ready-made setup for Claude Code, Cursor, or Claude Desktop. A Test connection button checks it works. Support staff connect from their own Profile page. The bundled MCP connection guide covers manual setup.
External services
This plugin connects to the third-party services below. Nothing is sent to a service until you configure it.
Stripe
Stripe processes all payments. The plugin calls the Stripe API (api.stripe.com) when a reader checks out, buys a gift, changes or cancels a subscription, when tax is calculated at checkout, and when an administrator manages subscribers or coupons. It sends the reader’s email address, name, billing and shipping address, the plan and price, and for tax estimates without an address, the reader’s IP address. Checkout pages load Stripe.js from js.stripe.com, which collects card details directly; card numbers never reach your site.
- Terms: https://stripe.com/legal/ssa
- Privacy: https://stripe.com/privacy
PaywallProject Connect hub (paywallproject.com)
Used for all payments made through Connect with Stripe. Before you connect, the plugin asks the hub for the platform fee rate and sends your site URL. When you connect, disconnect, or refresh the connection, it sends your site URL and the connection credentials. While connected, every Stripe API request listed above goes through the hub (https://paywallproject.com/wp-json/ppconnect/v1), which forwards it to Stripe and applies the platform fee. That includes the reader data listed under Stripe.
- Terms: https://www.paywallproject.com/terms-of-service/
- Privacy policy: https://www.paywallproject.com/privacy-policy/
Google reCAPTCHA
Used only when reCAPTCHA is selected as the signup protection. Registration and checkout forms load the reCAPTCHA script from google.com, which collects data about the visitor’s browser. When a form is submitted, the plugin sends the captcha token, your secret key and the visitor’s IP address to Google to verify it.
- Terms: https://policies.google.com/terms
- Privacy: https://policies.google.com/privacy
Cloudflare Turnstile
Used only when Turnstile is selected as the signup protection. Registration and checkout forms load the Turnstile script from challenges.cloudflare.com. When a form is submitted, the plugin sends the Turnstile token, your secret key and the visitor’s IP address to Cloudflare to verify it.
- Terms: https://www.cloudflare.com/website-terms/
- Privacy: https://www.cloudflare.com/privacypolicy/
Slack
Used only when you enter a Slack webhook URL. When a subscriber signs up, renews or cancels, the plugin posts a message with the subscriber’s email address and plan to that webhook.
- Terms: https://slack.com/terms-of-service
- Privacy: https://slack.com/trust/privacy/privacy-policy
Minilytics
Used only when you switch on the Minilytics integration and enter the address of your own Minilytics installation. Every page then loads the Minilytics tracking script from that address, which records the visit and keeps a visitor ID in a first-party cookie. For logged-in readers it also sends their email address and name. When a reader pays, or a payment is refunded, the plugin sends the amount, currency, the reader’s visitor ID, account ID, email address and name to your Minilytics installation. Minilytics is self-hosted, so this data goes to a server you run.
- Source and terms: https://github.com/rizaardiyanto1412/minilytics
Outgoing webhooks (Zapier and others)
Used only when you add a webhook URL. On the subscriber events you select, the plugin posts the event name and subscriber details (email address, name, plan and status) to the URL you entered. The data goes to whichever service owns that URL, under that service’s terms.
Installation
- Upload the plugin files to the
/wp-content/plugins/paywallprojectdirectory, or install the plugin through the WordPress plugins screen. - Activate the plugin through the Plugins screen in WordPress.
- Go to PaywallProject, choose Connect with Stripe, and set up your access settings.
FAQ
Does this require Stripe?
Yes. Stripe is the supported payment gateway for this version.
Is there a fee?
Yes. PaywallProject takes a platform fee of 10% of each payment made through Connect with Stripe. Stripe’s own fees apply as well.
Can my theme check whether a reader is a subscriber?
Yes. Call ppaccess_is_active_subscriber() for the current user, or pass a user ID. To check for specific plans, pass a list of level IDs as the second argument. Group plan members count as subscribers while their group’s owner is subscribed. ppaccess_get_subscriber_level_id() returns the reader’s level ID, or 0. Wrap calls in function_exists() so your theme keeps working if the plugin is turned off.
Where can I get help?
Visit paywallproject.com for guides and support, or post in the plugin’s support forum here on WordPress.org.
Screenshots






Changelog
4.5.3
- Improvement: The account page has a small “Billing history” link next to the plan’s price, so readers can find past receipts and invoices. It opens the Stripe customer portal, like “Update payment method”, and shows whenever that button does.
- Fix: Checkout, sign-in, account and gift form fields stay white while you type on themes that change field colors on focus, such as Blocksy set to a transparent focus background.
4.5.2
- Security: Closed two ways to test stolen card numbers on your checkout without passing the CAPTCHA. The Stripe Payment Element no longer contacts Stripe until the reader submits and the CAPTCHA has passed, and gift checkout now has the same CAPTCHA (or emailed code) as regular checkout.
- Improvement: Cards that need 3-D Secure now see one bank prompt at checkout instead of two.
- Improvement: Minilytics lists free and paid paywall views as separate goals,
paywall_shown_freeandpaywall_shown_paid, so each shows up in the Goals report.
4.5.1
- Improvement: Minilytics records whether each paywall view was the free or the paid wall, so you can compare free sign-ups and paid clicks against views of each.
- Fix: On sites using reCAPTCHA, the paywall’s sign-up form no longer shows Google’s “This site is protected by reCAPTCHA” line between the email field and the button.
- Fix: Plugin updates no longer say “Not tested” with WordPress point releases such as 7.1.4.
4.5.0
- Feature: A level can be limited by delivery postal code — only these codes, or every code except these — so a paper can be free in its own town and paid everywhere else. Readers enter their postal code first; one the level doesn’t take is pointed to the plan you name instead, with the code carried over. Checked on free sign-up, every checkout layout, redirect checkout and plan changes. Set it under the level’s Access → Postal code eligibility.
- Feature: Minilytics integration — send paid checkouts, renewals, gift purchases and refunds to Minilytics, credited to the article, campaign or referrer that brought the reader in, and record paywall views, plan picks, checkout clicks and sign-ups as goals. Under Settings → Minilytics. Off by default.
- Improvement: When reCAPTCHA or Turnstile can’t confirm a reader, they’re emailed a 6-digit code to finish signing up or paying, instead of being turned away. Throwaway email addresses can’t get a code, and checkout now allows 30 payment attempts per network per hour.
- Improvement: Clearer CAPTCHA messages. Pressing the button before ticking the Turnstile box now asks the reader to tick it instead of waiting.
- Fix: An existing subscriber whose CAPTCHA failed on the paywall was emailed a sign-up code they didn’t need. They’re now asked to sign in.
- Fix: Forms no longer hang on “Processing…” when the CAPTCHA script is blocked or slow, and the sign-in, lost-password and paywall sign-in forms send again with Turnstile on.
- Fix: A new free sign-up on the paywall is checked once — the code step no longer shows a second CAPTCHA.
4.4.0
- Feature: Free levels can let new readers choose their own password, confirm their email with a 6-digit code before the account is created, or both — under the level’s Pricing → Free sign-up. An email that already has an account is asked to sign in instead. Off by default.
- Fix: The standalone checkout page now includes what other plugins add to the page head, such as Site Kit’s Google tag — Tag Assistant reported “No Google tags found” there.
- Fix: The free sign-up form no longer says a password will be emailed — none ever was. It now says what happens next.
- Security: A confirmed email code now only works in the browser that entered it, on every free sign-up form that uses one.
4.3.0
- Feature: A level can let readers continue past their article limit without upgrading — a “No thanks, continue reading” link on the upgrade prompt, for donation-funded publishers that ask for support but can’t require it. Set the link text, and how long to wait before asking again (one day by default, or every article). It also covers readers whose subscription is canceled, expired, or past due — they’re still asked to renew each time. Off by default; visitors who aren’t signed in still have to sign up.
Older releases are listed in changelog.txt.
