> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payglue.io/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Frequently asked questions about running PayGlue.

## 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.

<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.
</Warning>

See [Product Mapping](/mappings/create) for how mappings are created, and [Webhook URLs](/mappings/webhook-urls) for how the per-organization webhook URL works.

## How do I contact support, and what is the Support Access PIN?

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](mailto: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.