> 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/how-they-pay.md). # How They Pay **How they pay** shows one row for each **place** a customer of this market can arrive — each signup journey and each portal — and the hosted payment page that place serves, in this market's currency. ## Places, not grids A place is anywhere a payment form can appear: * a **signup journey** (your public acquisition checkout), * the **Customer portal** (a customer adding or replacing a card in self-service), * the **CSR**, **Sales**, and **Partner portals** (your teams taking a payment method on a customer's behalf). Each place needs a payment page that matches the market's currency, because a hosted payment page validates and tokenizes the card against a specific billing-system page — and that page carries its own currency, styling, and allowed domains. A Canadian customer in your customer portal and a Canadian prospect on your signup page are both in the Canada market, but they are on different hosts, so they get different pages. ## Reading a row Each row shows the place, the payment page routed for it, and the page's live **health**: * **Healthy** — the most recent real request for this page succeeded. * **No traffic yet** — nothing has exercised this page since it was configured. Not an error; it flips to healthy on the first successful checkout. * An error state names the failure from the last attempt, so a misconfigured page is visible before a customer finds it. Select a row to open the **inspector**, which shows the full resolution for that place: the route that matched, the payment configuration it names, and the underlying page registration. ## Payment configurations A **payment configuration** is the registration of one hosted payment page with the platform: its provider (for example, a Zuora Hosted Payment Page), the page reference, and the currencies it serves. Configurations are shared across markets — the **Payment configurations** view in the left rail lists all of them with their health. If a place shows **no page**, the market has a gap: either no configuration exists in this currency for that kind of place, or no route connects them. The [setup checklist](/product/using-peakcommerce/market-studio.md#the-setup-checklist) counts these gaps, and the market cannot activate while any remain. ## Routing by brand If your tenant has [brands](/product/settings/organization/brands.md), each route can serve one brand or **Any brand**. Choose it in the route's **Brand** field; the route row shows a brand badge. * A checkout on a brand's domain uses routes for **that brand** or for **Any brand**. If a brand route and an any-brand route would both match, the brand's own route wins. * A brand's checkout **never falls back** to the market's default configuration. With no matching route, the customer sees that payment isn't set up rather than getting another brand's page. * A configuration that a brand route points at belongs to that brand, and isn't used as the default for checkouts that have no brand. When customers pick a payment method on the page first (for example **Debit or credit card**, **American Express** or **Bank account**), the route's configuration must offer that method. To give one brand three methods, create three routes for that brand, each pointing at a configuration that declares one method (Card, Amex or ACH). The **By brand** table under **How they pay** shows, for each brand and method, which configuration a checkout resolves to in this market. **No route** marks a gap; **shared** means an any-brand route answers it. Use **＋ Route** on a row to add a route for that brand. ## One important property The page shown here is the page a customer actually gets. Checkout resolves the visitor's market and serves this routing — there is no per-page override that can silently substitute a different payment page. If you want a place to serve a different page, change it here. --- # 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/how-they-pay.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.