> 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.md).

# Merchant Onboarding

The **Merchant Onboarding APIs** let you create and manage merchant onboarding applications. They simplify the onboarding process for merchants seeking payment processing services. These RESTful APIs use secure HTTPS communication for reliable and secure data exchange for payment processing.

### Merchant onboarding flow

Follow these high-level steps to onboard a merchant:

{% stepper %}
{% step %}

#### Merchant data collection

Collect and submit merchant business details through the Integrator application to start onboarding. Your application integrates with Xplor Pay backend systems to create and manage merchant profiles.

After submission, the system validates the merchant information and returns a response for verification.
{% endstep %}

{% step %}

#### Data validation and correction

After the application is submitted, the system validates the merchant data. If corrections are required, the [Application Fixes Webhook](https://docs.xplorpay.com/api-reference/webhooks/working-with-webhooks/merchant-onboarding-webhooks/application-fixes) notifies the integration system.

Key validations include:

* **Business contact validation** – Verifies business ownership details.
* **Bank validation** – Confirms banking details to help prevent transaction errors.

To resolve validation issues:

✅ Implement webhook notifications.

✅ Display validation issues to merchants.

✅ Collect corrected merchant information.

✅ Resubmit the corrected data through the related onboarding APIs.

✅ Proceed with signature submission and application submission.
{% endstep %}

{% step %}

#### Merchant agreement and application submission

Merchants review the onboarding application, electronically sign the agreement, and submit the application for processing.

Supported application submission methods include:

* ​**Electronic signature** – Merchants sign the agreement online.
* ​**Document upload** – A pre-signed agreement can be uploaded instead.
  {% endstep %}

{% step %}

#### Automated underwriting and decision

After the application is submitted, Xplor Pay performs automated underwriting and compliance review. The system reviews the merchant data for risk and compliance.

Possible review outcomes include:

* **Approved** – The merchant proceeds to underwriting with equipment setup and activation.
* **Manual review** – Additional verification, such as supporting documents, may be required.
* ​**Declined** – The application does not meet compliance or risk requirements.

The system sends real-time application status notifications through [Webhooks](https://docs.xplorpay.com/api-reference/webhooks).
{% endstep %}

{% step %}

#### Equipment setup

For approved merchants, Xplor Pay configures payment devices and provisioning details for transaction processing.

​Automated equipment setup details:

* Configure payment devices, such as POS systems and card readers.
* Assign API credentials and processing configurations.
  {% endstep %}
  {% endstepper %}

Each API section includes integration guidance and implementation details to help you complete the merchant onboarding process.

<div align="left" data-with-frame="true"><figure><img src="https://1781171437-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fj9heLdoDRsfnChUQohvj%2Fuploads%2FtLES6SZdvYvc68eD1q96%2Fimage.png?alt=media&amp;token=756aa425-f899-496b-8205-a8a0e6be40c3" alt=""><figcaption><p>Screenshot: Merchant onboarding process flow</p></figcaption></figure></div>

* [Onboard Merchant](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant.md)
* [Hosted Merchant Onboarding](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/hosted-merchant-onboarding.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.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.
