# Merchant Onboarding

The **Merchant Onboarding APIs** allow you to create and manage merchant onboarding applications. Merchant Onboarding API is designed to simplify and streamline the onboarding process for merchants seeking payment processing services. These RESTful API that utilizes secure HTTPS communication, ensuring reliable and secure data exchange for payment processing.

### **Merchant onboarding flow**

Follow the high-level steps below involved while onboarding a merchant:

{% stepper %}
{% step %}

#### Merchant data collection

Collect and submit merchant business details through Integrator application to initiate 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 using the related onboarding APIs used during the Merchant Data Collection process.

✅ 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 or business verification.
* ​**Declined** – The application does not meet compliance or risk requirements.

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

{% step %}

#### Equipment setup

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

​Automated equipment setup details:

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

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

<figure><img src="/files/fTUs0g2wV2vH1FBDoUOL" alt=""><figcaption></figcaption></figure>

* [Onboard Merchant](/api-reference/api/merchant-onboarding/onboard-merchant.md)
* [Hosted Merchant Onboarding](/api-reference/api/merchant-onboarding/hosted-merchant-onboarding.md)


---

# Agent Instructions: 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:

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

The question should be specific, self-contained, and written in natural language.
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.