> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eximpe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MERCHANT REJECTED

> Technical reference for the MERCHANT_REJECTED webhook event, including payload schema, field specifications, and implementation details.

***

## Event Overview

**Event Type**: `MERCHANT_REJECTED`\
**Category**: Onboarding\
**Description**: A sub-merchant's application has been declined

This webhook is sent when EximPe rejects a sub-merchant's application. It is delivered to the parent merchant's webhook URL. The sub-merchant's status is then `REJECTED`: it cannot collect payments and can no longer be edited.

It is sent once per rejection. A sub-merchant that is already `REJECTED` does not trigger it again.

A rejected sub-merchant can be removed with [Delete Merchant](https://docs.eximpe.com/api-reference/v3/merchant/delete.md). To onboard the business again, create a new sub-merchant with [Create Merchant](https://docs.eximpe.com/api-reference/v3/merchant/create.md).

***

## Payload Schema

```json Example Payload theme={null}
{
    "event_type": "MERCHANT_REJECTED",
    "event_time": "2026-12-15T14:32:18.456789",
    "version": "3.0.0",
    "sequence_number": "c81d4e2f-6b3a-4f9e-a5d7-0e1b2c3d4f5a",
    "data": {
        "merchant_id": "1380229823",
        "legal_name": "TechStore Solutions Private Limited",
        "trade_name": "TechStore Online",
        "timestamp": "2026-12-15T14:32:18.456789",
        "reason": "The business operates in a category EximPe does not support.",
        "section_reasons": [
            {
                "section": "business_details",
                "reason": "Category is outside the supported list."
            }
        ]
    }
}
```

***

## Field Specifications

> [tab] Root Level Fields
>
> **event\_type** `string` *required*
>
> Always `"MERCHANT_REJECTED"` for this webhook event
>
> **event\_time** `string` *required*
>
> UTC, no timezone suffix, e.g. `"2026-12-15T14:32:18.456789"`. Parse tolerantly — fractional seconds can be absent.
>
> **version** `string` *required*
>
> API version of your account, e.g. `"3.0.0"`
>
> **sequence\_number** `string` *required*
>
> Unique ID of this event (a UUID, not an ordering counter). A retry resends the same value; use it to de-duplicate.
>
> **Example**: `"c81d4e2f-6b3a-4f9e-a5d7-0e1b2c3d4f5a"`
>
> **data** `object` *required*
>
> Event-specific data payload containing the rejection details

> [tab] Data Object Fields
>
> **data.merchant\_id** `string` *required*
>
> Unique identifier of the rejected sub-merchant
>
> **Example**: `"1380229823"`
>
> **data.legal\_name** `string` *required*
>
> Legal business name of the sub-merchant as registered with authorities
>
> **Example**: `"TechStore Solutions Private Limited"`
>
> **data.trade\_name** `string` *required*
>
> The sub-merchant's brand name: the `brand_name` sent when it was created or last edited.
>
> **Example**: `"TechStore Online"`
>
> **data.timestamp** `string` *required*
>
> ISO 8601 timestamp when the application was rejected
>
> **Example**: `"2026-12-15T14:32:18.456789"`
>
> **data.reason** `string` *required*
>
> EximPe's reason for the rejection. Can be an empty string when no reason was recorded. The same text is returned as `reject_reason` by [Get Merchant](https://docs.eximpe.com/api-reference/v3/merchant/get.md).
>
> **Example**: `"The business operates in a category EximPe does not support."`
>
> **data.section\_reasons** `array` *required*
>
> One entry per part of the application EximPe flagged. Can be empty.
>
> * `section` — the part of the application, e.g. `"business_details"`. See [Sections](https://docs.eximpe.com/api-reference/v3/merchant/options.md#sections) for every value.
> * `reason` — what EximPe found in that part.
>
> **Example**: `[{"section": "business_details", "reason": "Category is outside the supported list."}]`

***


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.