MERCHANT APPROVED

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

---

Event Overview

Event Type: MERCHANT_APPROVED
Category: Onboarding
Description: Merchant account has been approved and activated

This webhook is triggered when a merchant account is approved and can start collecting payments through EximPe.

---

Payload Schema

Example Payload

{
    "event_type": "MERCHANT_APPROVED",
    "event_time": "2024-12-15 14:32:18",
    "version": "1.0",
    "sequence_number": "a3791670-7c5d-4a86-aa7a-fe35e58a9dbb",
    "data": {
        "approved_at": "2024-12-15T14:32:18.456789Z",
        "merchant_id": "1380229823",
        "legal_name": "TechStore Solutions Private Limited",
        "trade_name": "TechStore Online"
    }
}

---

Field Specifications

Root Level Fields

event_type · string · required

Always "MERCHANT_APPROVED" for this webhook event

event_time · string · required

Timestamp when the event occurred in YYYY-MM-DD HH:MM:SS format

Example: "2024-12-15 14:32:18"

version · string · required

Webhook payload version (currently “1.0”)

sequence_number · string · required

Unique identifier for the event instance

Example: "a3791670-7c5d-4a86-aa7a-fe35e58a9dbb"

data · object · required

Event-specific data payload containing merchant approval details

Data Object Fields

data.approved_at · string · required

ISO 8601 timestamp when the merchant was approved

Example: "2024-12-15T14:32:18.456789Z"

data.merchant_id · string · required

Unique identifier for the approved merchant

Example: "1380229823"

data.legal_name · string · required

Legal business name of the merchant as registered with authorities

Example: "TechStore Solutions Private Limited"

data.trade_name · string · required

Trading or brand name of the merchant used for customer-facing operations

Example: "TechStore Online"

---