> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/using-peakcommerce/market-studio/adding-a-market-or-currency.md). # Adding a Market or Currency Because a market *is* a currency, "we want to start selling in GBP" and "we need a UK market" are the same project. This page is the end-to-end runbook. ## Before you start — in your billing system Market Studio routes customers to hosted payment pages, so the pages must exist first: 1. **Create the hosted payment pages** for the new currency in your billing system — one per place kind you serve (for example: one for public signup, one for the customer portal, one for the internal portals). Each page carries the new currency. 2. **Allow your domains on each page.** Hosted payment pages only render on the domains listed in their configuration. Add every host the page will appear on (your signup domain, your portal domains) — a page missing a domain shows a "not allowed for this host" error instead of a card form. 3. **Confirm the product catalog carries prices** in the new currency for every plan you intend to sell — a plan with no price in a currency cannot be offered in that market. ## In PeakCommerce 4. **Register the pages** under **Settings → Integrations** (hosted pages for your billing integration), so the platform can sign requests for them. 5. **Create payment configurations** — one per new page — naming the provider, the page, and the new currency. They appear in Market Studio's **Payment configurations** view as *no traffic yet*. 6. **Add the currency to your sellable-currency list.** This list drives the currencies offered to visitors (for example in a coverage-gap chooser). There is no dedicated settings page for it yet — it is one API call (`PUT /api/currencies`); your PeakCommerce contact can apply it with you. 7. **Create the market** in **Commerce → Market Studio** with the new currency as its currency. It starts inactive, with the setup checklist open. 8. **Assign surfaces** on [Where they arrive](/product/using-peakcommerce/market-studio/where-they-arrive.md) — the signup journeys and portals this market serves. 9. **Complete** [**How they pay**](/product/using-peakcommerce/market-studio/how-they-pay.md) — connect each place to its payment configuration until no gaps remain. 10. **Add sentences** on [Who gets what](/product/using-peakcommerce/market-studio/who-gets-what.md) if the new market needs its own language or profile decisions; at minimum confirm **Otherwise** covers it sensibly. ## Verify, then activate 11. [**Trace a customer**](/product/using-peakcommerce/market-studio/trace-a-customer.md) in the new currency through every place — each path must complete at the new pages. 12. **Activate** the market (the button enables once the checklist is green). 13. **Run one real checkout** in the new currency on your staging environment and confirm: the correct page rendered, the order completed, and the customer account in your billing system carries the new currency. The page's health badge flips from *no traffic yet* to *healthy* on the first live success. ## Rollout notes * **Entry links**: a visitor arriving with `?currency=` on a journey link is placed in that market directly — update your marketing/pricing pages to offer the new currency where you want it promoted. * **Existing customers keep their market.** Adding GBP does not move anyone; accounts stay in the market they purchased in. * **One market per currency.** If the Studio reports two markets claiming the same currency, fix that before activating — ambiguous claims make routing undefined. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.peakcommerce.com/product/using-peakcommerce/market-studio/adding-a-market-or-currency.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.