> 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/partner-portal/partner-portal/guides/merchant-onboarding-via-partner-portal/reviewing-and-submitting-application.md).

# Reviewing & Submitting Application

The **Review & Submit** step is the final stage of the merchant onboarding process in the Partner Portal. This step allows users to verify all entered details, resolve any outstanding errors, and submit the application for approval.

Watch the interactive walkthrough below to review onboarding errors, upload missing documents, and submit the merchant application.

{% embed url="<https://app.guideflow.com/player/qp79xqvcjr>" %}

### **Review application**

<figure><img src="https://content.gitbook.com/content/Us4U42giioY3jQj0TJQl/blobs/vWB0FCjLqWtXHDmdKhZ4/Merchant%20Onboarding%20via%20PP%20-%20Submitting%20Application.jpg" alt="" width="563"><figcaption><p>Screenshot: Review &#x26;submit page</p></figcaption></figure>

{% stepper %}
{% step %}

#### **Accessing the review & submit page** <a href="#id-1.-accessing-the-review-and-submit-page" id="id-1.-accessing-the-review-and-submit-page"></a>

* Navigate to the **Partner Portal**.
* Click on **Review & Submit** in the top navigation menu.
* The **Review & Submit** page will be displayed, showing any errors that need resolution and a list of required submission documents.
  {% endstep %}

{% step %}

#### **Resolving errors** <a href="#id-2.-resolving-errors" id="id-2.-resolving-errors"></a>

If there are any outstanding errors preventing submission, they will be displayed under the **Errors to Resolve** section. Users must review and correct these errors before proceeding. Common errors may include:

* Invalid characters in business contact names.
* Missing required signatures for sections such as **Merchant Agreement, Personal Guarantee, Bank Disclosure,** and **W-9**.
* Missing electronic signature agreements.
* Missing required equipment validation.

Once all issues are addressed, the system will allow resubmission.
{% endstep %}

{% step %}

#### **Reviewing submission documents** <a href="#id-3.-reviewing-submission-documents" id="id-3.-reviewing-submission-documents"></a>

Below the **Errors to Resolve** section, users will find the **Submission Documents** panel. This displays the status of essential documents:

* **Application** (✔ / ❌)
* **Personal Guarantee** (✔ / ❌)
* **Bank Verification** (✔ / ❌)

To upload any missing documents:

* Click the **Add a Document** button.
* Select and upload the required file.
* Ensure all documents are successfully added.
  {% endstep %}

{% step %}

#### **Reviewing merchant information** <a href="#id-4.-reviewing-merchant-information" id="id-4.-reviewing-merchant-information"></a>

At the bottom of the page, merchant-related details such as **Service Organization, Compensation Type,** and **Referral Partner** will be displayed. If necessary, users can edit this information:

* Click **Edit Info**.
* Make the necessary updates.
* Save the changes.
  {% endstep %}

{% step %}

#### **Submitting the application** <a href="#id-5.-submitting-the-application" id="id-5.-submitting-the-application"></a>

After resolving all errors and ensuring all required documents are uploaded:

* Review all information for accuracy.
* Click the **Submit** button.
* The application will be sent for processing and approval.
  {% endstep %}
  {% endstepper %}

### **Submit application**

Merchant Onboarding uses an Application Access PIN to protect in-progress applications and sensitive merchant data. This 4-digit PIN allows merchants to securely resume and complete an application if the session is interrupted or abandoned.

To complete the merchant onboarding application:

{% stepper %}
{% step %}

#### **Set application acceptance PIN**

To protect sensitive application data, merchants are required to create a 4-digit security PIN when starting their application. This PIN helps prevent unauthorized access to the in-progress application.

When a merchant starts the onboarding application, the system prompts them to create a 4-digit Application Access PIN.

* The PIN secures the sensitive in-progress application data.
* The merchant must use the same PIN to resume the application if the session ends.
* Select Continue after you enter the PIN.

<figure><img src="https://2473171143-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUs4U42giioY3jQj0TJQl%2Fuploads%2FF8n9evqU4S0yd0QCY5Xy%2Fimage.png?alt=media&amp;token=337ba34b-39a9-49e8-a04f-4991716d6113" alt=""><figcaption><p>Screenshot: Create PIN screen</p></figcaption></figure>
{% endstep %}

{% step %}

#### **Resume an incomplete onboarding application**

To continue an incomplete application, enter the previously created 4-digit PIN. This unlocks the saved progress and resumes the application where it was left off.

To continue an application that was not submitted, the merchant enters the previously created 4-digit PIN.

* The system unlocks the saved application.
* The merchant resumes the application from the last completed step.

<figure><img src="https://2473171143-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUs4U42giioY3jQj0TJQl%2Fuploads%2FDpbf6DYWhl1S8kyGYQYM%2Fimage.png?alt=media&amp;token=98a0ef4a-23bc-43f7-a6e5-a59c9f6cb536" alt=""><figcaption><p>Screenshot: Enter four-digit PIN screen</p></figcaption></figure>
{% endstep %}

{% step %}

#### **Reset a forgotten or invalid PIN**

Click **Forgot PIN?** if the merchant forgets the PIN or enters an invalid PIN. A PIN reset link is sent to the provided email address in the `emailAddress` field of the `merchantInformation` object during merchant creation.

<figure><img src="https://2473171143-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUs4U42giioY3jQj0TJQl%2Fuploads%2FmNBhmolLheKOQa12Cbsj%2Fimage.png?alt=media&amp;token=78246d24-cd32-456d-90b6-42c8d6a2de77" alt=""><figcaption><p>Screenshot: Forgot PIN screen</p></figcaption></figure>

Click the reset link to invalidate the existing PIN. You can create a new access PIN and resume the hosted merchant onboarding application from where it was left off.

<figure><img src="https://2473171143-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUs4U42giioY3jQj0TJQl%2Fuploads%2Fs5q0wCRemzkQhTd1NVhV%2Fimage.png?alt=media&amp;token=4a6d1a58-0f41-448c-9f3c-06b2b0d73ab3" alt=""><figcaption><p>Screenshot: Reset PIN screen</p></figcaption></figure>
{% endstep %}

{% step %}

#### **Validating and submitting the application**

Before submission, the system automatically validates the application to confirm all required information is complete and formatted correctly. Validation checks include the required fields completion, email and phone number format validation, and data consistency across application sections.

​Once all sections pass validation, the merchant proceeds to **Review & Sign** to finalize the application.

<figure><img src="https://2473171143-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUs4U42giioY3jQj0TJQl%2Fuploads%2FyloQUv8Hy9wPur2q6z9D%2Fimage.png?alt=media&amp;token=7f551a12-250c-4da5-ae6e-e47290817f60" alt=""><figcaption><p>Screenshot: Review &#x26; Sign screen</p></figcaption></figure>

These measures ensure data accuracy, maintain compliance, and provide a secure, seamless onboarding experience.
{% endstep %}

{% step %}

#### **Signing the merchant agreement**

To complete onboarding, designated signer provides **Electronic Records and Signature Consent**. This consent authorizes the use of electronic documents and digital signatures. The signer reviews and signs all required documents online. This process eliminates the need for printing, scanning, or mailing paperwork.

During the application process, the system displays the Electronic Records and Signature Consent form. The signer reviews the document and electronically signs to confirm acceptance and continue. This action confirms your acceptance and allows the onboarding process to continue without delay.

<figure><img src="https://2473171143-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUs4U42giioY3jQj0TJQl%2Fuploads%2FNYrGaiWzv9cnhe97kspU%2Fimage.png?alt=media&amp;token=4720bb38-736b-4b90-b446-ec60f1722001" alt=""><figcaption><p>Screenshot: Sign agreement screen</p></figcaption></figure>
{% endstep %}

{% step %}

#### **Finalizing the application terms**

After all required documents are signed, the Hosted Merchant Onboarding completes the application using guided, electronic workflows. The platform can automatically redirect the user to a configured URL, such as to confirmation page, a resource hub, or a custom destination to streamline the overall onboarding experience.

<figure><img src="https://2473171143-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUs4U42giioY3jQj0TJQl%2Fuploads%2FvmJXduT4Zf0pD2w74NaW%2Fimage.png?alt=media&amp;token=ddc7a35f-4223-4b49-bfc4-e370fa4748d7" alt=""><figcaption><p>Screenshot: Onboarding success screen</p></figcaption></figure>
{% endstep %}
{% endstepper %}

Once submitted, the application will be reviewed by the system. Users may receive notifications regarding the approval status or additional actions required.

{% hint style="warning" %}
Ensure all steps are completed accurately to avoid delays in the approval process.
{% endhint %}


---

# 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/partner-portal/partner-portal/guides/merchant-onboarding-via-partner-portal/reviewing-and-submitting-application.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.
