Skip to content

Pay-in Webhook Notification Callback

Description

Once a pay-in transaction has succeeded or failed, the platform asynchronously pushes the final order status via an HTTP POST request to the notifyUrl provided by the merchant during order creation.

IMPORTANT

  1. After the merchant system receives and successfully processes the notification, it must respond with the plain text string SUCCESS (without quotes or extra whitespace).
  2. If the platform receives any response other than SUCCESS (or if the request times out), a retry mechanism will trigger: up to 5 retries with a 20-minute interval between attempts.
  3. Verify the signature using the Platform Public Key and ignore case differences during signature checking.

Request Information

  • Endpoint: Merchant's configured notifyUrl
  • Method: POST
  • Content-Type: application/json; charset=utf-8

HTTP Headers

HeaderRequiredTypeDescription
merchantNoYesStringMerchant ID
signYesStringRSA signature of the payload generated using the platform's private key

Callback Body Parameters

Example Payload

json
{
  "timestamp": "1772880120000",
  "merchantOrderNo": "202603070001",
  "platOrderNo": "876324486452871168",
  "amount": "100.00",
  "fee": "2.00",
  "status": "3",
  "msg": "success",
  "remark": "Test Order"
}

Field Specifications

FieldRequiredTypeExampleDescription
timestampYesString1772880120000Notification dispatch timestamp
merchantOrderNoYesString202603070001Merchant order reference number
platOrderNoYesString876324486452871168Platform transaction reference
amountYesString100.00Transaction amount paid
feeYesString2.00Channel service fee
msgYesStringsuccessResult description
statusYesString3Order status:
0: Created
1: Expired
2: Payment Failed
3: Payment Succeeded
remarkNoStringTest OrderCustom remarks passed by merchant during order creation

Merchant Expected Response

The merchant server must acknowledge receipt by responding with HTTP 200 and the plain text:

text
SUCCESS

Bangladesh Payment Gateway API Specifications