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 counts these gaps, and the market cannot activate while any remain.

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.