I have multiple Ghost blogs — how do I set up PayGlue correctly?
Each Ghost blog you connect lives in its own PayGlue organization, with its own webhook URL and its own set of product mappings. If you run several blogs, follow this rule:
Create one payment provider product per blog, and map each product only within the organization for that blog.
Do not map the same provider product (the same Polar product, the same Creem product, and so on) inside more than one organization. If you do, every purchase of that product triggers the webhook in every organization it is mapped in, and PayGlue creates the buyer as a Ghost member on every one of those blogs — not just the one they actually bought access to.
This happens because mapping isolation works per organization, not per product. PayGlue does isolate webhook delivery correctly (each organization has its own webhook URL, filtered by that organization’s slug), but it has no way to know that the same underlying provider product was intentionally reused across two blogs versus mapped there by mistake.
If you sell access to multiple blogs from the same payment provider account, create a separate product per blog in that provider, even if the price and description are identical. Then map each product only in the one organization it belongs to.
Do readers need a free Ghost account before they can buy?
No. A visitor can buy straight from a PayGlue buy button, paywall or pricing table without signing up in Ghost first. Your payment provider takes the payment and sends PayGlue a webhook, and PayGlue creates the Ghost member on the spot, with the labels or the comped flag that unlock your content, and lets Ghost send the welcome email you chose in the mapping. With the magic link email, the buyer is signed in after one click.
If a free member with the same email address already exists, PayGlue updates that member instead of creating a second one. The one thing worth telling your readers: use the same email at checkout that they used for their free account, otherwise they end up with two member records.
How do I show the paid options to readers who just signed up for free?
Ghost’s Portal only lists paid tiers when Stripe is connected, so a free signup through the Portal never sees your PayGlue offers there. Ghost has no general “after signup, go to this page” setting either, but every tier has a welcome page.
- Create a membership page in Ghost, for example
/membership/, and embed your pricing table on it. Use the Free sign-up CTA type for the first column and your provider products for the others.
- In Ghost Admin, go to Settings > Membership > Tiers, open the Free tier and set its Welcome page to that membership page.
A new free member who clicks the magic link now lands on the membership page and sees the paid options right away. Put the same page in your navigation and point your paywall overlays at the same offers, so a reader who hits a wall sees the same choice as a reader who arrives via the menu.
I tested a purchase and now there is a test member in my Ghost site. What happens to it?
It gets whatever your rule says, including the newsletter, because a test is there to show you the real flow. What sets it apart is the label payglue-test. Delete test members in Ghost by filtering on that label, or set the rule’s newsletter option to No while you test. Details: Test members.
Open Settings > Support in your dashboard. Pick a topic (integration issue, billing, something broken, a feature or provider request, account or team, or something else), describe what’s happening, and submit — you’ll get a reference number immediately and a confirmation email, and you can track the request’s status from the same page. You can also email team@payglue.io directly at any time.
Owners and admins additionally see a Support Access PIN section above the form. This is not required to submit a request — it’s a short-lived code (valid 24 hours, revocable any time) that you generate and hand to PayGlue support only when asked, to authorize us to make active changes to your account while resolving a ticket. Support can already see logs and debug information without it.
