> 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/webhooks/working-with-webhooks/merchant-onboarding-webhooks/application-status.md).

# Application Status

Each merchant application goes through multiple stages during approval and onboarding. The Application Status webhook sends notifications when an application moves to one of the following states:

<table data-search="true"><thead><tr><th width="190" valign="top">State</th><th valign="top">Description</th></tr></thead><tbody><tr><td valign="top"><code>Pended</code></td><td valign="top">The application requires manual intervention before proceeding.</td></tr><tr><td valign="top"><code>Manual Review</code></td><td valign="top">The application is undergoing a detailed underwriting review.</td></tr><tr><td valign="top"><code>Approved</code></td><td valign="top">The application has been approved and is ready for onboarding.</td></tr><tr><td valign="top"><code>Declined</code></td><td valign="top">The application has been rejected and will not proceed further.</td></tr><tr><td valign="top"><code>Boarded</code></td><td valign="top">The merchant account has been successfully boarded to the gateway and is ready to begin processing transactions.</td></tr></tbody></table>

### Webhook event structure

The **Application Status Webhook** sends structured JSON payloads to the subscribed endpoint when an application status changes. The payload includes the following fields:

* `event` – The current status of the application.
* `merchantId` – The unique merchant account identification number.
* `payload` – An empty string for most statuses.

{% hint style="warning" %}
The `payload` field includes additional details only when the status is `Boarded`.
{% endhint %}

### Webhook examples

Below are sample webhook payloads for each application status:

#### Pended

{% code lineNumbers="true" %}

```javascript
{
  "event": "Pended",
  "merchantId": "6588000000049726",
  "payload": ""
}
```

{% endcode %}

#### Manual Review

{% code lineNumbers="true" %}

```javascript
{
  "event": "Manual Review",
  "merchantId": "6588000000049726",
  "payload": ""
}
```

{% endcode %}

#### Approved

{% code lineNumbers="true" %}

```javascript
{
  "event": "Approved",
  "merchantId": "6588000000049726",
  "payload": ""
}
```

{% endcode %}

#### Declined

{% code lineNumbers="true" %}

```javascript
{
  "event": "Declined",
  "merchantId": "6588000000049726",
  "payload": ""
}
```

{% endcode %}

#### Boarded

{% code lineNumbers="true" %}

```javascript
{
  "event": "Boarded",
  "merchantId": "88880000000123456",
  "orderId": "999990000000987654",
  "payload": {
    "terminals": [
      {
        "apiKey": "2P0H1L84133",
        "publicKey": "ABCDEFGHIJK123456789",
        "name": "Merchant Name"
      }
    ]
  }
}
```

{% endcode %}

{% hint style="warning" %}
The Boarded status includes additional merchant details, including terminal API keys and encryption keys.
{% 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/api-reference/webhooks/working-with-webhooks/merchant-onboarding-webhooks/application-status.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.