> 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/onboard-merchant.md).

# Onboard Merchant

The following endpoints help you manage the merchant onboarding process, from creating a merchant application to submitting it for review and approval.

The following steps help you onboard a merchant:

{% stepper %}
{% step %}

#### Create merchant profile

Submit a request to the [Application Management](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/application-management.md) ([Create application](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/application-management/application#post-api-boardingmanagement-v1.0-applications-create)) API using your assigned portfolio MID. This merchant identifier is a unique 16-digit identifier provided during integration setup and represents your merchant portfolio.

In the request:

* Set the `MerchantId` HTTP header to your portfolio’s merchant identifier.
* ​Include the `HierarchyNodeKey` in the request body to define where the new merchant belongs in the hierarchy.

The response returns a new 16-digit merchant identifier (MID). Use this MID in all subsequent onboarding API requests.
{% endstep %}

{% step %}

#### Create merchant application

Use the [Create application](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/application-management/application#post-api-boardingmanagement-v1.0-applications-create) endpoint to create the merchant application using the assigned MID. This step collects required onboarding details such as business name and hierarchy placement before submitting the application for underwriting and setup.
{% endstep %}

{% step %}

#### Provide merchant demographic and business details

Collect and submit merchant demographic and business information through [Merchant Demographics](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/merchant-demographics.md). This process ensures that the merchant account includes all required information for verification and underwriting.

{% hint style="warning" %}
Once a merchant is initially created, the system pre-generates empty demographic records such as mailing address, physical address, taxpayer information, and sales profiles. Update these records using the related `PUT` endpoints.
{% endhint %}
{% endstep %}

{% step %}

#### Configure pricing plan

Use the [Pricing Plans](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/pricing-plan-and-reference/pricing-plans.md) to create or update merchant pricing plans during onboarding. This configures transaction fees, service charges, and other cost-related settings that align with each merchant’s business needs.

Customizable pricing plans are flexible pricing structures based on business requirements. Each plan can include specific fee types, rates, and service charges.

Configure pricing using predefined templates or customize plans to match individual business requirements.
{% endstep %}

{% step %}

#### Add equipment, documents, and compliance data

Complete the equipment survey to order equipment using the [Equipment order API](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/equipment/equipment-order). This streamlines the configuration and ordering of devices required for payment processing.

You can select supported devices, such as POS terminals, card readers, and other payment hardware. Once submitted, the system provisions the hardware and links it to the corresponding Merchant ID (MID).

To configure equipment:

1. Retrieve available equipment products.
2. Retrieve the [equipment configuration survey](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/equipment/equipment-configuration-survey) for the selected device.
3. Complete and submit the required survey configuration.
4. Submit the equipment order.

After submission, the system provisions the hardware and associates it with the merchant MID.
{% endstep %}

{% step %}

#### Submit application signature

Merchant consent is collected through signature submission to complete the onboarding application.

You can submit signatures electronically or through uploaded signed documents.

**Electronic signature submission**

To submit electronic signatures:

1. Mark at least one business contact as a signer.
2. ​Present the legal terms and conditions to the signer for review.
3. ​Provide a method for the signer to accept the agreement (for example, a checkbox).
4. ​Submit the signature using the [Submit signatures](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/application-management/application#post-api-boardingmanagement-v1.0-applications-merchantnumber-submitsignatures) endpoint.

**Signature submission via document upload**

Merchants preferring physical signatures can print, sign, and upload documents using the following process:

1. Mark at least one business contact as a signer.
2. ​Allow the merchant to upload the signed documents through your application.
3. ​Submit the uploaded document using the [Upload document](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/merchant-demographics/documents#post-api-demographics-v1-documents-merchantnumber) endpoint.
4. Submit the signature confirmation using the [Submit signatures](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/application-management/application#post-api-boardingmanagement-v1.0-applications-merchantnumber-submitsignatures) endpoint.

Once a merchant submits the signature, the system validates the submitted information. If it finds errors, it returns them in the response. If the data is valid, it accepts the signatures and completes the submission.

After a successful submission, no further changes can be made to the merchant through the Merchant Onboarding API. This process ensures Xplor Pay receives the required authorization while supporting flexible signature submission options.
{% endstep %}

{% step %}

#### Submit application for review and approval

Submit the application for processing after all required onboarding data and signatures are completed.

After submission, Xplor Pay validates onboarding information, including business contacts, banking information, and compliance details. It then performs automated underwriting and compliance reviews.

* ​**Underwriting review** – The submitted data is reviewed for compliance and risk evaluation.
* ​**Equipment activation** – Provisions configured payment hardware.

This step transitions the merchant from onboarding to operational status.

​After successful review and approval, the response returns HTTP `200 OK` with confirmation that the merchant application is approved. The merchant account is activated and ready to process payments.
{% endstep %}
{% endstepper %}

After onboarding is complete, proceed to [Payments](https://docs.xplorpay.com/api-reference/api/payments.md).

* [Application Management](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/application-management.md)
* [Merchant Demographics](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/merchant-demographics.md)
* [Pricing Plan and Reference](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/pricing-plan-and-reference.md)
* [Equipment](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/equipment.md)
* [Merchant Legal Documents](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/merchant-legal-documents.md)
* [eDocs Reporting](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/edocs-reporting.md)


---

# 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/onboard-merchant.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.
