Skip to main content

​
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.

​
Delivery Details

AttributeValue
HTTP methodPOST
URLThe webhook URL configured on your merchant account’s API credentials
Content-Typeapplication/json
Timeout10 seconds
RetriesUp to 5 delivery attempts (backoff: 1 min, 5 min, 15 min, 60 min)

​
Headers

HeaderDescription
Content-Typeapplication/json
User-AgentEximpe-Webhook/1.0
X-Webhook-EventMERCHANT_APPROVED
X-Webhook-TimestampUnix timestamp (string) at the time of the request
X-Webhook-SignatureHMAC-SHA256 signature of the request body (JSON string with keys sorted, no extra whitespace), using your API key as the secret. Hex-encoded.
Signature verification (recommended):
Compute HMAC-SHA256(encryption_key, raw_body) where raw_body is the exact UTF-8 request body as received. Compare the hex result with the X-Webhook-Signature header to ensure the webhook is from the platform and unchanged.

​
Payload Schema

{
    "event_type": "MERCHANT_APPROVED",
    "event_time": "2024-12-15 14:32:18",
    "version": "2.0.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

​
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 formatExample: "2024-12-15 14:32:18"
​
version
string
required
Webhook payload version (currently “1.0”)
​
sequence_number
string
required
Unique identifier for the event instanceExample: "a3791670-7c5d-4a86-aa7a-fe35e58a9dbb"
​
data
object
required
Event-specific data payload containing merchant approval details