How This Blog Runs with a PayGlue Paywall

We could have written another generic "why we built this" post. Instead, we figured the more honest demo is the page you are reading right now. This blog runs on Ghost, and somewhere below this paragraph, there is a paywall. That paywall is not a Ghost native tier. It is PayGlue, running on our own infrastructure, gating our own content.

If you want proof that PayGlue actually works before you connect your own Ghost site to it, this is that proof.

Why we are dogfooding our own product

Most SaaS landing pages ask you to trust a list of features. We would rather show you the thing running. PayGlue exists to connect Ghost CMS to payment providers beyond Stripe, and to manage member access automatically when someone pays. There is no better way to demonstrate that than to put it directly in the path of our own readers.

So here is what is actually happening on this page, mechanically:

1. You are reading this post as a public visitor (or a free member, depending on what you have signed up for).
2. Somewhere below, the content stops and a paywall block appears.
3. If you pay through one of our connected payment providers, a webhook fires.
4. You complete checkout via a connected payment provider (Polar in this demo)
5. Polar sends a webhook to PayGlue
6. PayGlue verifies the webhook signature and confirms the payment is genuine
7. PayGlue calls the Ghost Admin API and adds a payglue-active label to your account
8. The JavaScript snippet on this page reads that label from Ghost's member API and removes the paywall overlay instantly on your next visit when you login

No manual approval, no spreadsheet, no "let me go check if your payment went through." The loop closes by itself.

Why this matters beyond one blog post

This blog is a small, low-stakes example. The real use case is creators who already write on Ghost and want to monetize with a payment provider Ghost does not natively support, without losing the membership and content-gating tools Ghost already gives them.

Ghost's own Stripe integration is solid, but it only covers Stripe. If your audience is global, if Stripe is not available in your country, or if you specifically want a Merchant of Record that handles tax compliance for you, you are on your own for the membership-syncing part. That gap between "payment succeeded" and "Ghost actually knows about it" is exactly what PayGlue closes.

We have written about that gap in more detail elsewhere on this blog. What we have not done until now is let you watch it happen on a real page, in real time, with our own content as the stakes.

This is a sandbox demo. No real payment will be charged.

At checkout, enter 0 to get access for free, or try a full payment flow with the test card:

Card: 4242 4242 4242 4242
Expiry: 01/30
CVC: 123

Nothing will be charged. This is Polar's sandbox environment.

What happens after the paywall

If you are reading this part, congratulations, the loop worked. PayGlue verified your sandbox payment, called the Ghost Admin API, and granted you the membership that unlocks this section. You did not sign up for a "PayGlue account." You do not have a separate login for PayGlue at all. As far as Ghost is concerned, you are just a member, exactly like someone who paid through Ghost's native Stripe integration would be.

That is the whole point. PayGlue is not a parallel membership system living next to Ghost. It is a relay that listens for payment events and translates them into the membership actions Ghost already understands. When you cancel or your subscription lapses, the same relay revokes access the same way, automatically, without anyone on our side touching a dashboard.

A few things worth knowing about how this specific setup is wired:

• We only store what is strictly necessary to verify and relay events: the Ghost Admin API key and the webhook secret for each connected payment provider, both encrypted at rest.
• Nothing about your payment details ever passes through our system. PayGlue only sees the webhook event your payment provider sends after a transaction completes or changes state, not your card number or any sensitive payment data.
• Ghost's native Stripe integration, if a site has one configured, keeps running completely independently. PayGlue does not touch it or modify it. It only adds the providers Ghost cannot handle natively.

Why we are showing you this instead of just telling you

A lot of "see it in action" demos in this space are staged: a sandbox tenant, fake test data, a recorded video where nothing is actually at risk. This is not that. If our webhook verification had a bug, or our Admin API integration broke, you would not be reading this paragraph right now. The fact that this content unlocked for you is a small but real signal that the underlying mechanics work, on a live Ghost instance, with real payment provider traffic.

We are still in private beta, and we are building in public, including the rough edges. This post is one of those rough edges turned into a feature: instead of polishing a demo video, we just let our own paywall be the demo.

If you made it this far, you have effectively beta tested PayGlue for us. Thank you for that. If you have feedback on anything about this flow, from the speed of the unlock to the wording of any step along the way, reply to this post or reach out directly. We read everything.

Be first when we launch.

Join the waitlist and lock in your Founding Member rate. Free access during beta.

Secure your spot

Pic by Call Me Fred on Unsplash