Lotuspay Merchant Integration Documentation

1. Payment order placement

Submission Method: POST
Submission URL: http://150.5.128.21/apid/newbankPay/crtOrder.do

Request Parameters:

Parameter name	Type	Required	Illustrate / Description
appId	string	Yes	Merchant Account ID viewable in platform backend dashboard.
appOrderNo	string	Yes	Merchant own unique system transaction tracking number.
orderCounty	string	Yes	Order amount (accurate to two decimal places, e.g., 100.00).
payId	string	Yes	Payment channel code (101 = bKash, 102 = Nagad, 103 = Rocket).
payName	string	No	Payer identification name data variable.
notifyURL	string	Yes	Asynchronous server HTTP callback notification address string.
jumpURL	string	No	Redirect address after client successfully completes payment.
sign	string	Yes	Lexicographically sorted uppercase MD5 authentication signature token.

Request Example JSON:

{
  "appId": "7881744704",
  "appOrderNo": "PAY202607191001",
  "orderCounty": "500.00",
  "payId": "101",
  "notifyURL": "http://yourdomain.com/callback.php",
  "sign": "E9785F22B0F5BC26461E235F22F0041B"
}

Response Parameters:

Parameter name	Type	Illustrate / Description
code	int	Status code. 200 indicates operation execution success.
msg	string	Description message returned by API engine node.
data.orderNo	string	Platform dynamic serial transaction unique tracking ID.
data.appOrderNo	string	Merchant custom tracking identification number.
data.payUrl	string	Dynamic target cashier destination payment interface URL.

Success Response JSON:

{
  "code": 200,
  "msg": "success",
  "data": {
    "orderNo": "PAY20260719225501",
    "appOrderNo": "PAY202607191001",
    "orderCounty": "500.00",
    "payUrl": "http://150.5.128.21/pay/index.php?trade_no=PAY20260719225501&payId=101"
  }
}

2. Payment callback interface

Submission Method: POST

Callback Data Parameters:

Parameter name	Type	Participate in sign	Illustrate / Description
appOrderNo	string	Yes	Merchant unique tracking reference number.
orderNo	string	Yes	Platform unified serial transaction node identification.
appId	string	Yes	Merchant account identification index token.
orderCounty	string	Yes	Gross transaction order asset volume value submitted.
payAmt	string	Yes	Actual net asset balance added after handling fee cuts.
orderFee	string	No	Platform system transaction processing charge deducted.
orderStatus	string	Yes	00 = Payment Successful, 01 = Processing, 99 = Failed.
sign	string	No	MD5 validation signature value computed by target server.

Callback Payload Example JSON:

{
  "appOrderNo": "PAY202607191001",
  "orderNo": "PAY20260719225501",
  "appId": "7881744704",
  "orderCounty": "1000.00",
  "payAmt": "980.00",
  "orderFee": "20.00",
  "orderStatus": "00",
  "sign": "F82C27D37AD96E5681D960EA16882394"
}

Notice: The notification service will hit your server. If successful, you must return a fixed uppercase "SUCCESS" string.

3. Payment order query

Submission Method: GET / POST
Submission URL: http://150.5.128.21/apid/newbankPay/selOrder.do

Request Parameters:

Parameter name	Type	Required	Illustrate / Description
appId	string	Yes	Merchant identifier number.
appOrderNo	string	Yes	Merchant tracking transaction reference ID.
sign	string	Yes	32-bit uppercase MD5 signature validation token.

Response Parameters:

Parameter name	Type	Illustrate / Description
code	int	200 indicates operational execution success.
msg	string	Description state response information label.
data.orderNo	string	Platform internal tracking transaction number string.
data.appOrderNo	string	Merchant reference custom transaction string index.
data.orderStatus	string	00 = Success Paid, 01 = Pending, 99 = Failed.
data.orderCounty	string	Gross original transaction asset amount value.
data.payAmt	string	Net asset values post-processing configuration logic.

Success Response JSON:

{
  "code": 200,
  "msg": "success",
  "data": {
    "orderNo": "PAY20260719225501",
    "appOrderNo": "PAY202607191001",
    "orderStatus": "00",
    "orderCounty": "1000.00",
    "payAmt": "980.00"
  }
}

4. Pay and place order

Submission Method: POST
Submission URL: http://150.5.128.21/apid/newbankPay/crtAgencyOrder.do

Request Parameters:

Parameter name	Type	Required	Illustrate / Description
appId	string	Yes	Merchant ID account token key credential.
appOrderNo	string	Yes	Merchant custom payout withdrawal reference ID.
orderCounty	string	Yes	Amount to transfer / withdraw to target endpoint receiver.
payId	string	Yes	Payout route identification variable code (401 = Payout Node).
accNo	string	Yes	Receiver bKash/Nagad system mobile phone wallet node account number.
accName	string	Yes	Receiver verification name identity record matching parameter.
bankCode	string	No	Bank routing system identifier variable if applicable.
bankName	string	No	Operator destination string config parameter reference (e.g. bKash).
notifyURL	string	Yes	Asynchronous server callback communication URL target location.
extParams	string	No	Extended metadata custom parameters object map.
sign	string	Yes	32-bit uppercase generated signature hash value validation string.

Request Example JSON:

{
  "appId": "7881744704",
  "appOrderNo": "WIT202607190099",
  "orderCounty": "1500.00",
  "payId": "401",
  "accNo": "01712345678",
  "accName": "Zhang San",
  "bankName": "Industrial and Commercial Bank of China",
  "notifyURL": "http://yourdomain.com/payout_notify.php",
  "sign": "5185FA0394B040BFCE43D56ACA61ABE7"
}

Response Parameters:

Parameter name	Type	Illustrate / Description
code	int	Status confirmation indicator variable logic.
msg	string	Operational error or successful description feedback parameter string.
data.orderNo	string	Unified platform generated processing unique trade serial code.
data.appOrderNo	string	Merchant reference verification index parameter tracker.
data.status	string	01 = Processing, 00 = Settled, 99 = Rejected.

Success Response JSON:

{
  "code": 200,
  "msg": "success",
  "data": {
    "orderNo": "AGENCY202607199988",
    "appOrderNo": "WIT202607190099",
    "status": "01"
  }
}

5. Payout order inquiry

Submission Method: GET / POST
Submission URL: http://150.5.128.21/apid/newbankPay/selAgencyOrder.do

Request Parameters:

Parameter name	Type	Required	Illustrate / Description
appId	string	Yes	Merchant account identification number tracker parameter index.
appOrderNo	string	Yes	Payout transaction identification tracker custom tracking ID.
sign	string	Yes	32 uppercase MD5 generated checking hash encryption token key string.

Success Response JSON:

{
  "code": 200,
  "msg": "success",
  "data": {
    "orderNo": "AGENCY202607199988",
    "appOrderNo": "WIT202607190099",
    "orderStatus": "00",
    "orderCounty": "1500.00",
    "orderFee": "30.00",
    "payAnt": "1530.00"
  }
}

6. Check merchant balance

Submission Method: GET
Submission URL: http://150.5.128.21/apid/newbankPay/selUser.do

Request Parameters:

Parameter name	Type	Required	Illustrate / Description
appId	string	Yes	Merchant database identifier tracking index credential token string.
sign	string	Yes	Lexicographically assembled 32-digit uppercase verification code string hash.

Success Response JSON:

{
  "code": 200,
  "msg": "success",
  "data": {
    "appId": "7881744704",
    "balance": "54200.50",
    "freeze": "0.00",
    "currency": "BDT"
  }
}

7. MD5 Signature Rules

MD5 Hashing Step Engine:
1. Arrange all request parameter parameter keys in alphabetical dictionary order (A to Z).
2. Remove empty string parameter variables and the sign parameter key itself.
3. Form a combined query string line like: appId=xxx&appOrderNo=xxx&orderCounty=xxx.
4. Append the active secret integration key string at the tail end position: ...&key=YOUR_SECRET_KEY.
5. Enclose the string inside an MD5 hash calculation tool and transform the final payload value output directly into Uppercase letters.

String Generation String Example:

appId=7881744704&appOrderNo=PAY202607191001&orderCounty=500.00&payId=101&key=093e59809ecb45c3a01b4513606c9165