> 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/adding-hierarchy-and-compensation-details.md).

# Adding Hierarchy & Compensation Details

**Hierarchy and Compensation** section ensures that the merchant is correctly classified within the organization, and compensation preferences are set.

Watch the interactive walkthrough below to add hierarchy and compensation details.

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

To enter hierarchy and compensation details:

<div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/Us4U42giioY3jQj0TJQl/blobs/XeJouKJ25v0KmiAUwM8s/Merchant%20Onboarding%20via%20PP%20-%20Adding%20Hierarchy%20&amp;%20Compensation%20Details.jpg" alt="" width="563"><figcaption><p>Screenshot: Hierarchy page</p></figcaption></figure></div>

{% stepper %}
{% step %}

#### **Enter DBA name** <a href="#id-1.-enter-dba-name" id="id-1.-enter-dba-name"></a>

* In the **DBA (Doing Business As) Name** field, enter the merchant’s business name.

{% hint style="warning" %}
**Note**: Ensure that the name follows the required format and does not contain invalid characters.
{% endhint %}
{% endstep %}

{% step %}

#### **Select service organization/hierarchy** <a href="#id-2.-select-service-organization-hierarchy" id="id-2.-select-service-organization-hierarchy"></a>

* Click inside the **Choose a Service Organization/Hierarchy** field.
* Use the **search icon** to find and select the appropriate service organization.
  {% endstep %}

{% step %}

#### **Specify merchant type** <a href="#id-3.-specify-merchant-type" id="id-3.-specify-merchant-type"></a>

* Check the box if the merchant **belongs to a chain**.
* Select whether the business operates as **Brick & Mortar** or **E-commerce**.
  {% endstep %}

{% step %}

#### **Declare product sales information** <a href="#id-4.-declare-product-sales-information" id="id-4.-declare-product-sales-information"></a>

* Indicate if the business sells **CBD products or other goods associated with CBD program** by selecting one of the available options.
* If the business does not sell CBD products, select **No**.
  {% endstep %}

{% step %}

#### **Set compensation preferences** <a href="#id-5.-set-compensation-preferences" id="id-5.-set-compensation-preferences"></a>

* Choose how you would like to be compensated upon the completion of the onboarding process:
  * **All Residual**: Receive ongoing residual payments.
  * **Signing Bonus with Residual**: Get a one-time bonus along with residuals.
    {% endstep %}

{% step %}

#### **Enter additional merchant identifiers (optional)** <a href="#id-6.-enter-additional-merchant-identifiers-optional" id="id-6.-enter-additional-merchant-identifiers-optional"></a>

* If applicable, enter a **Referral Partner** name.
* To associate this merchant with an external system, enter:
  * **SFOpportunityId** (Salesforce Opportunity ID)
  * **ExternalCustomerId** (Customer ID from another system)
    {% endstep %}
    {% endstepper %}


---

# 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/adding-hierarchy-and-compensation-details.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.