MERCHANT REJECTED

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. To onboard the business again, create a new sub-merchant with Create Merchant.

Payload Schema

{
    "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

Root Level Fields
Data Object Fields

string

required

Always "MERCHANT_REJECTED" for this webhook event

string

required

UTC, no timezone suffix, e.g. "2026-12-15T14:32:18.456789". Parse tolerantly — fractional seconds can be absent.

string

required

API version of your account, e.g. "3.0.0"

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"

object

required

Event-specific data payload containing the rejection details

string

required

Unique identifier of the rejected sub-merchantExample: "1380229823"

string

required

Legal business name of the sub-merchant as registered with authoritiesExample: "TechStore Solutions Private Limited"

string

required

The sub-merchant’s brand name: the brand_name sent when it was created or last edited.Example: "TechStore Online"

string

required

ISO 8601 timestamp when the application was rejectedExample: "2026-12-15T14:32:18.456789"

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.Example: "The business operates in a category EximPe does not support."

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 for every value.
reason — what EximPe found in that part.

Example: [{"section": "business_details", "reason": "Category is outside the supported list."}]

Order

Payment

Merchant

Settlement

Refund

Subscriptions

Payment Links

Virtual Bank Accounts

LRS

B2B Services

Webhooks

Event Overview

Payload Schema

Field Specifications

​Event Overview

​Payload Schema

​Field Specifications

Event Overview

Payload Schema

Field Specifications