> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/customizations-and-bolt-ons/hosted-checkout-landing-pages.md).

# Hosted Checkout Landing Pages

Create branded campaign landing pages that send customers to a preconfigured Reach hosted checkout.

Use this capability for campaign pages, partner pages, or pages on your existing site. The hosted checkout applies your brand theme and continues into activation, account management, and other Reach experiences.

{% hint style="info" %}
**Best for:** teams that need a focused campaign experience and a streamlined path to checkout.
{% endhint %}

### At a glance

{% columns %}
{% column %}

#### Your brand owns

* Page design and campaign messaging
* Traffic sources and attribution
* Post checkout destination
  {% endcolumn %}

{% column %}

#### Reach manages

* Hosted checkout and brand theming
* Secure session creation
* Activation and account journeys
  {% endcolumn %}
  {% endcolumns %}

### Create a campaign ready checkout

Your landing page passes campaign context into checkout. Customers arrive with the offer already configured.

#### Configure the customer experience

* **Plan selection:** Send customers directly to checkout with a selected plan in their cart.
* **Promotions:** Apply a campaign promo code automatically. Invalid or expired codes never block checkout.
* **Multiple lines:** Prefill the number of lines. POST can also pass names, email addresses, and SIM type.
* **Checkout controls:** Choose whether customers can switch plans, edit promos, or add lines. All are locked by default.
* **Return destination:** Send customers to a campaign page, thank you page, or another destination after completion, cancellation, or an error.

#### Preserve campaign attribution

Standard UTM and custom attribution parameters persist through the handoff. Reach stores them in the session and forwards them to your configured analytics destination.

If customers leave and return, Reach restores their session context. Promotions are validated again. Back navigation returns customers to your campaign page.

### Choose an integration method

{% tabs %}
{% tab title="POST (Recommended)" %}
Use a browser form POST to submit an encoded payload to Reach. This method supports the richest checkout configuration.

Use POST when you need:

* Details for each line
* SIM preferences
* Granular checkout controls

Checkout data never appears in the URL or browser history.
{% endtab %}

{% tab title="GET for simple links" %}
Use a static link with query parameters for a lightweight campaign. Pass the plan, line count, promo, and return URL.

GET works well in emails, banners, QR codes, and paid campaigns. Do not use it for customer details.
{% endtab %}
{% endtabs %}

Reach validates every handoff, creates a secure session, and opens the matching hosted checkout with the supplied context.

### Launch your landing page

{% stepper %}
{% step %}

#### Enable the capability

Work with your account manager to add Hosted Checkout Landing Pages to your platform subscription.
{% endstep %}

{% step %}

#### Prepare your page

Reach must approve the source domain before launch. Build your page within the Landing Page Guidelines.
{% endstep %}

{% step %}

#### Integrate and test

Implement the GET or POST handoff. Validate plan identifiers against your brand catalogue. Test the complete redirect flow in QA.
{% endstep %}

{% step %}

#### Submit for approval

Send the completed landing page to Reach for review before implementation.
{% endstep %}
{% endstepper %}

### Approval and compliance

{% hint style="warning" %}
Where Reach is the carrier of record, Reach must approve every landing page before implementation. Submit all later page changes for approval before publication.
{% endhint %}

Landing pages must meet applicable regulatory, advertising, and brand requirements. This includes broadband labels, accessibility, disclosures, carrier references, data privacy, and legal documents.

### Implementation resources

Use the [Landing Page to Hosted Checkout Integration](https://docs.reachplatform.com/technical/bolt-on-setup/landing-page-to-hosted-checkout-integration) guide for payload structures, parameters, code examples, and the prelaunch checklist.

Use the [Landing Page Compliance Guide](/customizations-and-bolt-ons/hosted-checkout-landing-pages/landing-page-approval-guide.md) for content, compliance, disclosures, and required documents.


---

# 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.reachplatform.com/customizations-and-bolt-ons/hosted-checkout-landing-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.