4.2 Payment Result Callback (Static QR)

Processing Flow:

Brief Description:

After the static QR code has been paid by the customer, the system will send a notification with the transaction information.
Note: Find the merchant's configuration channel based on service and merchant account routing

Callback Example (Success):

{
    "msgId": "1164806705893105666",
    "orderNo": "1164806712444612610",
    
    "trxState": "paid",
    "deviceInfo":"4444555",
    "trxAmount": "226.5",
    "message": "Transaction successful",
    "signature":"ce85ac3fc2002bcfb6ceda7ac636aa23"
}

Important note:

The callback is in JSON format. If your endpoint returns an invalid response format, you may not receive future callbacks. You must return the string "success" (without quotes) after processing.

Callback Parameters:

Parameter	Description	Format	Type
msgId	Merchant order number.	e.g., 1164806705893105	String
orderNo	Open API Order Number / System Reference ID.	e.g., 18235435435435435	String
trxState	Final status of the payment.	paid / unpaid / failed	String
deviceInfo	Terminal identification.	e.g., 3242342342	String
trxAmount	Transaction amount.	e.g., 26.50 USD	String
message	Description.	(String)	String
signature	Signature calculated using MD5 algorithm for data integrity and authentication.	MD5(payTradeNo + outTradeNo + totalAmount + first_16_chars_of_merchant_secret)	String

Construction Formula:
MD5(payTradeNo + outTradeNo + totalAmount + first_16_chars_of_merchant_secret)

Source String Example:
200560078466037350625920251229192417320146.22F50E217D0D7447DC

Resulting Signature:
ce85ac3fc2002bcfb6ceda7ac636aa23

Processing Flow:#

Brief Description:#

Callback Example (Success):#

Important note:#

Callback Parameters:#

Processing Flow:

Brief Description:

Callback Example (Success):

Important note:

Callback Parameters: