Event Overview
Event Type:PAYMENT_DETAILS_MISSINGCategory: Payment
Description: Payment was recorded but one or more order fields required for payment verification are missing. This webhook notifies you which fields that are missing for payment verification so you can supply them via the Partner API (order update or upload-verification-details) or dashboard. It is used for any payment with missing verification details, including VBA transfer and regular payment success flows.
When the webhook is sent
The webhook is sent only when all of the following are true:- Merchant has webhook URL – Your merchant account (or parent, for sub-merchants) has an active API credential with a non-empty webhook URL.
- At least one detail is missing – The payment’s order is missing one or more verification fields (see details_missing below). If all six fields are present on the order, the webhook is not sent.
Delivery Details
| Attribute | Value |
|---|---|
| HTTP method | POST |
| URL | The webhook URL configured on your merchant account’s API credentials |
| Content-Type | application/json |
| Timeout | 10 seconds |
| Retries | Up to 5 delivery attempts (backoff: 1 min, 5 min, 15 min, 60 min) |
Headers
| Header | Description |
|---|---|
Content-Type | application/json |
User-Agent | Eximpe-Webhook/1.0 |
X-Webhook-Event | PAYMENT_DETAILS_MISSING |
X-Webhook-Timestamp | Unix timestamp (string) at the time of the request |
X-Webhook-Signature | HMAC-SHA256 signature of the request body (JSON string with keys sorted, no extra whitespace), using your API key as the secret. Hex-encoded. |
Compute
HMAC-SHA256(api_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
Field Specifications
- Root Level Fields
- Data Object Fields
Always
"PAYMENT_DETAILS_MISSING" for this webhook eventISO 8601 datetime when the webhook event was createdExample:
"2025-02-12T10:30:00.123456Z"Envelope version (e.g. “2.0.0”)
Unique identifier for this webhook event (UUID), useful for idempotencyExample:
"550e8400-e29b-41d4-a716-446655440000"Event payload: order_uid, payment_id, message, details_missing
details_missing field names
Each element indetails_missing is a field name that may be missing on the order. Supply the missing fields by updating the order (Partner API or dashboard) or by calling the upload-verification-details endpoint for that payment. The following field names may appear:
| Field name | Description |
|---|---|
buyer_name | Name of the buyer/importer. |
product_description | Description of the product/goods. |
buyer_address | Buyer’s address. |
invoice_number | Invoice number. |
buyer_postal_code | Buyer’s postal/ZIP code. |
hs_code | HS code (or hs_code_description on the order). |
What to Do When You Receive This Webhook
- Respond with HTTP 2xx (e.g.
200 OK) as soon as you have accepted the payload, so the platform marks the delivery as successful and does not retry. - Verify the signature using your API key and the raw request body (HMAC-SHA256, hex) to ensure authenticity.
- Use
order_uidandpayment_idto fetch full order/payment details from the Partner API if needed (e.g. amount, status). - Supply missing verification details by updating the order with the missing fields (via the Partner API or dashboard) or by calling the upload-verification-details endpoint for that payment. The
details_missingarray lists the field names that are missing (e.g.buyer_name,product_description,invoice_number,buyer_address,buyer_postal_code,hs_code).