> 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/settings/developer-tools/hosted-pages.md).

# Hosted Pages

**Settings → Hosted Pages** keeps a curated, friendly-named list of your billing provider's hosted payment pages — for example **Zuora Hosted Payment Pages** — so the page editor can pick from a short, readable list instead of asking builders to paste raw provider page IDs.

## Why it matters

Hosted payment pages are iframes hosted by your billing provider that securely capture card and payment details, keeping sensitive data out of PeakCommerce. Providers identify each page by an opaque ID. Maintaining the mapping here once means everyone building checkout flows selects a clear name (e.g. "USD Credit Card") rather than copying a cryptic identifier into every page.

## Add a hosted page

1. Click **New Hosted Page**.
2. Give it a **friendly name** that describes its purpose — currency, payment method, or brand are good cues.
3. Enter the provider's **hosted page ID** (from your billing provider's console).
4. Save. The entry now appears in the page editor's payment-page picker.

## How it's used

When building an ecommerce checkout, the payment step references one of these curated entries by name. See [ecommerce and payment pages](/product/using-peakcommerce/ecommerce-and-payment-pages.md).

## Gotchas

* The **page ID must match** the one configured in your billing provider, and the page must be active there — a typo or disabled page surfaces as a broken payment step.
* Keep **currency and payment method** consistent between the friendly name and the underlying provider page so builders aren't misled.
* Removing an entry that a live page still references will break that page's payment step; re-point the page first.


---

# 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/settings/developer-tools/hosted-pages.md?ask=<question>&goal=<endgoal>
```

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