Stores

Why multiple stores

• Separate brands or business lines under one login
• Per-store coin allowlists - one store BTC-only, another full coverage
• Per-store webhooks and API keys, so integrations stay isolated
• Per-store reporting: the dashboard and payments list filter by store

Managing stores

Under Account → Stores, add stores and configure each one:

• Store Cloud Token - the publishable token for that store's embeds and checkout links (copy or rotate)
• Store API key - a per-store server credential, if the integration must be scoped to one store
• Webhook URL + secret - per-store webhook target; store webhooks take priority over the global one (see Webhooks)
• Test webhook - send a signed test delivery to that store's URL

The store selector in the console header switches the active store for link generation, and transactions carry their store so history stays clean.

Isolation

Store scoping is enforced server-side: a store-scoped token or key sees only that store's checkouts and transactions, never the account's other stores. On white-label instances the isolation runs deeper still - per-instance databases (see White-Label).

Stores and integrations

E-commerce integrations attach to a store: the Shopify app, for example, takes the store's Cloud Token. Give each sales channel its own store and its payments, links, and webhooks never mix.