I have multiple Ghost blogs. How do I set up PayGlue correctly?
Use one provider product per blog and map it in one organization only.
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.
Warning: 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.
See Product Mapping for how mappings are created, and Webhook URLs for how the per-organization webhook URL works.
Was this helpful?
Your feedback shapes what we write next.
How do I show the paid options to readers who just signed up for free?
Next →I tested a purchase and now there is a test member in my Ghost site. What happens to it?
