Event Overview
Event Type:MERCHANT_CHANGES_NEEDEDCategory: 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.
Delivery Details
Headers
Verifying. The body is serialised once and those exact bytes are both sent and signed, so hashing the raw request body as received is correct — do not re-serialise the parsed JSON first.
Both signature headers are sent. Verify V2 (recommended) or V1 — see Verifying webhooks.
Payload Schema
Field Specifications
- Root Level Fields
- Data Object Fields
UTC, no timezone suffix, e.g.
"2026-12-15T14:32:18.456789". Parse tolerantly — fractional seconds can be absent.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"