MMK interface
- Details
- Category: MMK interface
Deposit interface — Myanmar MMK
Use the merchant ID and merchant API key issued by EOOPAY. Each product must be enabled for your merchant account before use. Submit the product number assigned to you.
Amounts are in Myanmar kyat (MMK), with at most two decimal places.
Amount per deposit: MMK 2,000–1,000,000.
Product numbers
| pay_bankcode | Product name | Payment method |
|---|---|---|
| 991 | MMK-PAY-KBZPAY | KBZPAY |
| 992 | MMK-PAY-WAVEPAY | WAVEPAY |
| 993 | MMK-PAY-KBZPAY-02 | KBZPAY 02 |
| 994 | MMK-PAY-WAVEPAY-02 | WAVEPAY 02 |
| 995 | MMK-PAY-KBZPAY-03 | KBZPAY 03 |
| 996 | MMK-PAY-WAVEPAY-03 | WAVEPAY 03 |
Existing enabled product numbers and request formats remain unchanged. The table lists additional products; existing merchants do not need to replace their original product numbers.
POST https://{request-address}/Pay_AddOrder.htmlContent-Type: application/x-www-form-urlencoded
Request parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
| pay_memberid | Yes | string | EOOPAY merchant ID |
| pay_orderid | Yes | string | Unique merchant order number |
| pay_amount | Yes | string | Amount in MMK |
| pay_applydate | Yes | string | yyyy-MM-dd HH:mm:ss |
| pay_bankcode | Yes | string | Enabled deposit product number from the table above |
| pay_notifyurl | Yes | string | Merchant URL for asynchronous payment results |
| pay_callbackurl | Yes | string | Merchant browser return URL |
| pay_userid | Yes | string | End-user identifier in the merchant system |
| type | No | string | Set to json; excluded from the signature |
| pay_md5sign | Yes | string | Calculate using existing EOOPAY signing rules; excluded from its own signature |
The eight pay_ business fields above are included in the deposit signature; type and pay_md5sign are excluded. Browser redirects are for display only. Confirm payment using a verified asynchronous notification or order query.
Request example
This is a parameter template, not a live order. Replace the merchant ID, account details, order number and callback URLs, then calculate the signature with your merchant key. Send the actual request as form data.
{
"pay_memberid": "YOUR_MERCHANT_ID",
"pay_orderid": "MMKDEPOSIT_UNIQUE_ORDER",
"pay_amount": "2000.00",
"pay_applydate": "2026-10-20 12:00:00",
"pay_bankcode": "992",
"pay_notifyurl": "https://merchant.example/payment/notify",
"pay_callbackurl": "https://merchant.example/payment/return",
"pay_userid": "YOUR_USER_ID",
"type": "json",
"pay_md5sign": "RECALCULATE_WITH_YOUR_MERCHANT_KEY"
}Response parameters and example
| Parameter | Required | Type | Description |
|---|---|---|---|
| code | Yes | string | 1 indicates order creation succeeded; otherwise inspect the returned message |
| msg | Yes | string | Result message |
| money | Yes | string | Order amount in MMK |
| order_sn | Yes | string | EOOPAY platform order number |
| payUrl | Yes | string | Open this URL to access the cashier |
{
"code": "1",
"msg": "Success",
"money": "2000.00",
"order_sn": "PLATFORM_ORDER_NUMBER",
"payUrl": "https://{request-address}/Pay_Pay_pay.html?orderid=PLATFORM_ORDER_NUMBER"
}The KBZPAY / WAVEPAY products in the table use the cashier and asynchronous notifications and do not require a separate SID submission. For existing products that still require SID updates, continue using the original SID instructions.
Signing, queries and callbacks
Encryption · Deposit inquiry · Withdrawal inquiry · Deposit callback · Withdrawal callback
Existing product reference (unchanged)
https://{url}/Pay_AddOrder.html
Request parameters
|
parameter name |
required |
yes or no signature |
explanation |
|
pay_memberid |
YES |
YES |
The "merchant number" provided by the payment system to the cooperative merchant |
|
pay_orderid |
YES |
YES |
Merchant’s unique order number |
|
pay_applydate |
YES |
YES |
Payment time，yyyy-MM-dd HH:mm:ss |
|
pay_bankcode |
YES |
YES |
Channel Management->>Channel Rate Acquisition |
|
pay_notifyurl |
YES |
YES |
Server return address. (POST return data) |
|
pay_callbackurl |
YES |
YES |
Page jump return address (POST return data) |
|
pay_userid |
YES |
YES |
Transaction user ID; if it is inconvenient or unavailable to provide, please provide other alternative data, such as: player mobile phone number。 |
|
pay_amount |
YES |
YES |
Product amount in current currency |
|
pay_md5sign |
YES |
NO |
Please see MD5 signature field format |
|
type |
NO |
NO |
If type=json is passed, json will be returned,If you use a bank card, you must access updateSID; if other values are passed, html will be returned. |
Response parameters (will be returned only if type=json is passed)
|
parameter name |
required |
type |
explanation |
|
status |
YES |
string |
Status code 1=success error=failure |
|
msg |
YES |
string |
Error message： Success or faild |
|
pay_amount |
YES |
string |
order amount |
|
pay_orderid |
YES |
string |
Payment order number of the payment system |
|
payUrl |
YES |
string |
Payment link |
|
bank_code |
YES |
string |
Bank card number for recharge |
|
return_params |
NO |
string |
Transparent transmission parameters |
Request Example
{
"pay_memberid": "10006",
"pay_orderid": 1722801459,
"pay_amount": "1000.00",
"pay_applydate": "2024-08-05 03:57:39",
"pay_bankcode": 948,
"pay_notifyurl": "https:\/www.baidu.com",
"pay_callbackurl": "https:\/\/ya.ru\/",
"pay_userid": 15452,
"pay_md5sign": "664C48949ED085D950E3681C3FBEC9AE",
"type": "json"
}
Response Example
|
{ |
- Details
- Category: MMK interface
Withdrawal interface — Myanmar MMK
Use the merchant ID and merchant API key issued by EOOPAY. Each product must be enabled for your merchant account before use. Submit the product number assigned to you.
Amounts are in Myanmar kyat (MMK), with at most two decimal places.
Amount per withdrawal: MMK 50–1,000,000.
Product numbers
| payment_code | Product name | Payment method |
|---|---|---|
| 11031 | MMK-PAYOUT-WAVEPAY | WAVEPAY |
| 11032 | MMK-PAYOUT-KBZPAY | KBZPAY |
Existing enabled product numbers and request formats remain unchanged. The table lists additional products; existing merchants do not need to replace their original product numbers.
POST https://{request-address}/Payment_AddOrderContent-Type: application/x-www-form-urlencoded
Request parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
| mchid | Yes | string | EOOPAY merchant ID |
| applydate | Yes | string | yyyy-MM-dd HH:mm:ss |
| out_trade_no | Yes | string | Unique merchant order number; do not submit duplicate orders |
| payment_code | Yes | string | Enabled withdrawal product number from the table above |
| money | Yes | string | Amount in MMK, e.g. 2000.00 |
| bankname | Yes | string | Match the selected product: wave / kbz |
| accountnumber | Yes | string | Valid recipient account number; send as a string to preserve leading zeros |
| accountname | Yes | string | Recipient account holder name |
| userid | Yes | string | End-user identifier in the merchant system |
| notifyurl | Yes | string | Merchant URL for asynchronous result notifications |
| pay_md5sign | Yes | string | Calculate using the existing EOOPAY merchant signing rules |
Request example
This is a parameter template, not a live order. Replace the merchant ID, account details, order number and callback URLs, then calculate the signature with your merchant key. Send the actual request as form data.
{
"mchid": "YOUR_MERCHANT_ID",
"applydate": "2026-10-20 12:00:00",
"out_trade_no": "MMKPAYOUT_UNIQUE_ORDER",
"payment_code": "11031",
"money": "2000.00",
"bankname": "wave",
"accountnumber": "YOUR_RECIPIENT_ACCOUNT",
"accountname": "YOUR_RECIPIENT_NAME",
"userid": "YOUR_USER_ID",
"notifyurl": "https://merchant.example/payment/notify",
"pay_md5sign": "RECALCULATE_WITH_YOUR_MERCHANT_KEY"
}Response parameters and example
| Parameter | Required | Type | Description |
|---|---|---|---|
| success | Yes | boolean | true means the request was accepted, not that the withdrawal completed |
| errCode | Yes | string | 0 indicates request acceptance; inspect errMsg for errors |
| errMsg | Yes | string | Acceptance or error message; obtain final status from a callback or query |
{
"success": true,
"errCode": "0",
"errMsg": "Accepted; awaiting payment result"
}If the request times out or the final result is unavailable, query the original order before any retry to avoid duplicate withdrawals. Match the original merchant order number and do not treat acceptance as settlement.
Signing, queries and callbacks
Encryption · Deposit inquiry · Withdrawal inquiry · Deposit callback · Withdrawal callback
Existing product reference (unchanged)
https://{request address}/Payment_AddOrder
Request parameters
|
parameter name |
required |
type |
explanation |
|
mchid |
YES |
string |
The "merchant number" provided by the payment system to the cooperative merchant |
|
applydate |
YES |
string |
Initiate payment time，(yyyy-MM-dd HH:mm:ss) |
|
out_trade_no |
YES |
string |
Merchant’s unique order number |
|
payment_code |
YES |
string |
To pay for the product code, contact customer service to obtain it. |
|
money |
YES |
string |
Payment amount (unit: YES, current currency, 2 decimal places, 100.00) |
|
bankname |
YES |
string |
kbz or wave |
|
accountnumber |
YES |
string |
Bank card number or account number corresponding to the payment account |
|
accountname |
YES |
string |
Beneficiary Name |
|
userid |
YES |
string |
Transaction user ID; if it is inconvenient or unobtainable, please provide other alternative data, such as the player's mobile phone number. |
|
notifyurl |
YES |
string |
Payment callback address |
|
pay_md5sign |
YES |
string |
signature |
response parameters
|
parameter name |
required |
type |
explanation |
|
success |
YES |
string |
True for success, false for failure |
|
errCode |
YES |
string |
0 |
|
errMsg |
YES |
string |
Payment status message |
Request example
|
{ |
Return example
|
{ "success": true, "errCode": "0", "errMsg": "Success" } |
