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

# Merchant Demographics

The **Merchant Demographics API** allows you to create and manage comprehensive demographic details for a merchant.

This API enable access to detailed merchant profile, including business contact information, addresses, taxpayer details, banking information, and other essential data required for transaction processing and compliance.

{% hint style="warning" %}
You need an authorization token to authenticate requests.
{% endhint %}

{% hint style="info" %}
Ensure you have the appropriate role-based access permissions.
{% endhint %}

Merchant demographic configuration, pricing setup, equipment ordering, and document submission can be completed independently. However, all required onboarding steps must be completed before submitting the application.

### Data categories <a href="#data-categories" id="data-categories"></a>

This API provides access to the following demographic data categories:

* [**Merchant profile**](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/merchant-demographics/merchant) – Basic merchant details such as business name and contact details.
* [**Business contacts**](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/merchant-demographics/business-contact-1) – Contact details for individuals associated with the merchant, including owner's details.
* [**Addresses**](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/merchant-demographics/merchant#get-api-demographics-v1-merchantphysicaladdresses-merchantnumber) – Physical and mailing address details of the merchant.
* [**Bank accounts**](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/merchant-demographics/bank-account-1) – Bank account details used for transaction settlement
* [**Taxpayer information**](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/merchant-demographics/tax-payer) – Tax identification details such as TIN and legal business name.
* [**Sales profile**](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/merchant-demographics/sales-profile-1) – Sales and business activity details such as MCC, transaction types, and processing volume.
* [**Site survey**](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/merchant-demographics/site-survey-1) – Onboarding verification details such as business type and identity checks.
* [**Supporting documents**](https://docs.xplorpay.com/api-reference/api/merchant-onboarding/onboard-merchant/merchant-demographics/documents) – Uploaded documents such as voided checks, signed applications, and additional files.

To manage equipment orders and submit required legal documents, see:

* [Equipment](/api-reference/api/merchant-onboarding/onboard-merchant/equipment.md)
* [Merchant Legal Documents](/api-reference/api/merchant-onboarding/onboard-merchant/merchant-legal-documents.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/merchant-demographics.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.