Notification

The system pushes order updates to the merchant's configured callback URL whenever the status changes.

POSTMerchant callback URL

Return HTTP 200 with a plain-text OK body after receiving the callback so the system stops retrying.

Callback Strategy

• The system sends a notification when the order status changes.
• The merchant must return HTTP 200 with a plain-text OK response body (uppercase, no quotes, no extra JSON wrapper).
• If the merchant restricts incoming IPs, please inform us in advance.

Signature Verification

• The signature field in the callback is the notification signature and follows the same signing rule as API requests.
• Sort all non-empty fields in the callback JSON body except signature in a-z order, concatenate them as key=value pairs joined with &, append the merchant secret key, then calculate SHA256 and convert the result to lowercase hexadecimal.
• Compare the calculated result with signature, and verify that timestamp is within the valid time window. Return a non-OK response if signature verification or business processing fails.

Retry Strategy

If a valid acknowledgment is not received (HTTP 200 with response body OK), the system will automatically retry:

• Maximum Retries: 8 times within 24 hours
• Retry Intervals: 2s → 5s → 10s → 30s → 1h → 3h → 3h → 3h

Request Method

• POST
• JSON

Request Parameters

platformOrderNostringRequired

Unique platform order number

merchantOrderNostringRequired

Merchant order number

orderAmountstringRequired

Actual payment amount

orderStatusstringRequired

Order status: SUCCESS, PENDING, FAILED, EXPIRED, CANCELLED, REFUNDED

messagestringRequired

Status description message

completedAtstringOptional

Transaction completion time (YYYY-MM-DD HH:mm:ss), returned on successful transactions

timestampstringRequired

Millisecond timestamp

signaturestringRequired

Callback signature

payMethodstringOptional

Payment method, such as EASYPAISA, JAZZCASH, QR, or BANK