MERCHANT CHANGES NEEDED

Event Overview

Event Type: MERCHANT_CHANGES_NEEDED
Category: Onboarding
Description: EximPe needs changes to a sub-merchant’s application before it can be approved This webhook is sent each time EximPe sends a sub-merchant’s application back for changes. It is delivered to the parent merchant’s webhook URL, and carries EximPe’s reason and the parts of the application to fix. The sub-merchant’s status is then CHANGES_REQUESTED. It is sent every time EximPe asks for changes, including when the sub-merchant is already CHANGES_REQUESTED and EximPe asks again. Each delivery carries the latest reasons. To act on it, fix the fields with Update Merchant. Once the application is complete again, that edit resubmits it for review automatically; there is no separate resubmit call.

Payload Schema

{
    "event_type": "MERCHANT_CHANGES_NEEDED",
    "event_time": "2026-12-15T14:32:18.456789",
    "version": "3.0.0",
    "sequence_number": "5f0c2b1e-9a43-4d7e-8b61-2c7d9e4f1a90",
    "data": {
        "merchant_id": "1380229823",
        "legal_name": "TechStore Solutions Private Limited",
        "trade_name": "TechStore Online",
        "timestamp": "2026-12-15T14:32:18.456789",
        "reason": "The registration number does not match the incorporation certificate.",
        "section_reasons": [
            {
                "section": "company_details",
                "reason": "Registration number does not match the certificate."
            },
            {
                "section": "settlement_account",
                "reason": "Bank account name must match the legal name."
            }
        ]
    }
}

Field Specifications

Root Level Fields
Data Object Fields

string

required

Always "MERCHANT_CHANGES_NEEDED" 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: "5f0c2b1e-9a43-4d7e-8b61-2c7d9e4f1a90"

object

required

Event-specific data payload containing the requested changes

string

required

Unique identifier of the 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 EximPe asked for the changesExample: "2026-12-15T14:32:18.456789"

string

required

EximPe’s overall reason for sending the application back. Can be an empty string when no reason was recorded. The same text is returned as changes_requested_reason by Get Merchant.Example: "The registration number does not match the incorporation certificate."

array

required

One entry per part of the application that needs changes. Can be empty.

section — the part of the application, e.g. "company_details". See Sections for every value.
reason — what needs to change in that part.

Example: [{"section": "company_details", "reason": "Registration number does not match the certificate."}]

Order

Payment

Merchant

Settlement

Refund

Subscriptions

Payment Links

Virtual Bank Accounts

LRS

B2B Services

Webhooks

MERCHANT CHANGES NEEDED

Event Overview

Payload Schema

Field Specifications

​Event Overview

​Payload Schema

​Field Specifications

Event Overview

Payload Schema

Field Specifications