> For the complete documentation index, see [llms.txt](https://docs.xplorpay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/hosted-merchant-onboarding.md).

# Hosted Merchant Onboarding

The Hosted Merchant Onboarding API provides a prebuilt, secure hosted flow for merchant onboarding. Merchants can enter their business details, review and sign terms, and complete the application to onboard easily.

This solution automates key onboarding steps, including merchant account creation, data validation, and pricing configuration.

Hosted Merchant Onboarding is designed for quick integration. It requires minimal development effort while relying on Xplor Pay to manage the onboarding workflow and validation.

{% hint style="warning" %}
Hosted Merchant Onboarding was previously referred to as *Launch for Integrator* (*L4I*). You may still see references to *L4I* in system messages, APIs, or legacy documentation.
{% endhint %}

### Hosted merchant onboarding steps

Follow the steps below to onboard a merchant using the hosted application:

{% stepper %}
{% step %}

#### **Generate application URL**

To get an onboarding application URL, use the [Create New Merchant](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/hosted-merchant-onboarding/merchant#post-api-launchintegratorsetup-v1.0-integratemerchant-hierarchynodekey) endpoint to initiate onboarding for a merchant under your partner hierarchy node. This endpoint supports both minimal and complete payloads and applies default values when optional fields are not provided.

{% hint style="warning" %}
The application creation endpoint accepts partial requests and fills in default values where applicable.
{% endhint %}

Submit the required minimal merchant details, such as `DBA name`, `email address`, and `MCC`, to generate an application URL. This option is suitable when you collect only basic merchant information upfront and allow the merchant to complete the remaining details in the hosted flow.

{% code lineNumbers="true" %}

```
{
  "merchantInformation": {
    "dbaName": "test-L4I",
    "emailAddress": "felicita.silvester@xplortechnologies.com"
  },
  "salesProfile": {
    "mccCode": "4582"
  },
  "pendEmailAddress": "user@example.com"
  "secondaryPendEmailAddress": "rsd@example.com"
}
```

{% endcode %}

The API creates a new merchant application and returns an application URL in the `applicationURL` field.

In the request body, the `pendEmailAddress` field specifies the email address that receives application status update notifications, such as Signed, Approved, Pended, or Declined. The optional `secondaryPendEmailAddress` field specifies an additional email address that receives merchant correspondence.

{% hint style="info" %}

* If `pendEmailAddress` is provided, the system sends application status update notifications to this email address.
* If `pendEmailAddress` is not provided, the system uses the address <no-reply@xplorpay.com> as the default.
* If `secondaryPendEmailAddress` is provided, the system sends merchant correspondence to this email address.
* If `secondaryPendEmailAddress` is not provided, no secondary recipient is added.
  {% endhint %}
  {% endstep %}

{% step %}

#### Submit complete payload (optional)

Submit additional merchant details to prefill the hosted application and reduce manual data entry. Providing a [complete payload](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/hosted-merchant-onboarding/merchant#post-api-launchintegratorsetup-v1.0-integratemerchant-hierarchynodekey) improves the onboarding experience and helps merchants complete the application faster.

Use this approach when merchant data is already available, such as business details, addresses, bank accounts, ownership information, and pricing configuration.
{% endstep %}

{% step %}

#### **Redirect merchant**

The application URL directs the merchant to the hosted onboarding page to complete the application.

{% hint style="info" %}
Xplor Pay triggers a welcome email to the merchant containing the same link.
{% endhint %}
{% endstep %}

{% step %}

#### **Complete application**

The onboarding page shows the required fields for submitting the application. Merchants can enter business details and review additional required information.

In the onboarding page, the merchant can:

* Review and complete application details
* Upload required documentation
* Digitally sign agreements

{% hint style="warning" %}
The application URL remains valid for ***30 days***. After expiration, generate a new application to complete onboarding.
{% endhint %}
{% endstep %}

{% step %}

#### **Submit application**

When a merchant submits the application, Xplor Pay validates the data and allows the merchant to sign the agreement digitally.
{% endstep %}

{% step %}

#### **Pricing configuration**

The hosted onboarding application applies the default pricing plan based on your partner account structure. You can configure the pricing using custom or empower pricing.
{% endstep %}
{% endstepper %}

To apply and configure default, custom, or empower pricing for eligible merchants, see [Pricing Plan and Reference](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/pricing-plan-and-reference).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xplorpay.com/api-reference/api/merchant-onboarding/hosted-merchant-onboarding.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
