Skip to main content

​
Event Overview

Event Type: REFUND_STATUS_UPDATE
Category: Payment
Description: Refund status has changed This webhook is triggered whenever a refund transitions to a new status (for example, while it is being processed) 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-EventREFUND_STATUS_UPDATE
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

{
    "data": {
        "refunds": [
            {
                "bank_arn": null,
                "comments": "Refund is in progress",
                "order_id": "OD5128740396",
                "refund_id": "RF8043512967",
                "payment_id": "PR6271908354",
                "refund_amount": 320,
                "refund_status": "PROCESSING",
                "refund_completed_at": null
            }
        ]
    },
    "version": "1.0.0",
    "event_time": "2026-05-27T14:30:01.359434",
    "event_type": "REFUND_STATUS_UPDATE",
    "sequence_number": "b3e91f47-20ad-4c85-9f31-6d0a87145e2b"
}

​
Field Specifications

​
event_type
string
required
Always "REFUND_STATUS_UPDATE" for this webhook event
​
event_time
string
required
Timestamp when the event occurred in ISO 8601 formatExample: "2026-05-27T14:30:01.359434"
​
version
string
required
Webhook payload version (currently “1.0.0”)
​
sequence_number
string
required
Unique identifier for the event instanceExample: "b3e91f47-20ad-4c85-9f31-6d0a87145e2b"
​
data
object
required
Event-specific data payload containing refund details