API Documentation

We Are Your Trusted And Excellent Payment Solution

PAYMENT GATEWAY API GUIDE

Last Update 8th May 2026

WELCOME TO OUR API

Thank you for choosing Us!
We are excited to present our API documentation for seamless integration.
The documentation have 10 sections, with separated API endpoints for deposits and payouts.
You are NOT required to integrate all sections, only choose the relevant sections upon your needs.
You can navigate through each sections via the sidebar on the left.
If you have any questions beyond this documentation, please reach out to our Customer Support chat group.

HOME

Quick access to top of the page.

DEPOSIT

Quick access to Deposit Section.

DEPOSIT - CRYPTO

Quick access to Deposit Crypto Section.

DEPOSIT STATUS CHECK (REDIRECT)

Quick access to Deposit Status Check (Redirect) Section.

DEPOSIT STATUS CHECK (B2B)

Quick access to Deposit Status Check (B2B) Section.

PAYOUT - AUTOMATED (REDIRECT)

Quick access to Payout Automated (Redirect) Section.

PAYOUT - AUTOMATED (B2B)

Quick access to Payout Automated (B2B) Section.

PAYOUT STATUS CHECK - AUTOMATED (B2B)

Quick access to Payout Status Check Automated (B2B) Section.

APPENDIXES

Quick access to Appendixes Section.

DEPOSIT

HOW IT WORKS

Merchant posts deposit data to Payment Gateway using HTTP Post. Refer to DATA TO BE POSTED TO PAYMENT GATEWAY below.
Payment Gateway processes payment and redirects back to Merchant using HTTP Get with the Deposit Redirect URL provided by Merchant. Refer to HTTP GET REDIRECTED BY PAYMENT GATEWAY below.
Payment Gateway makes a HTTP Post with JSON only for success deposits to Deposit Postback JSON URL that provided by Merchant. Not like HTTP Get where users can see the HTTP Get URL from the browser, the HTTP Post is a backend process. The JSON contains detailed deposit data. Refer to HTTP POST (WITH JSON) BY PAYMENT GATEWAY below.
Merchant may uses arguments in the HTTP Get to process the deposit, such as show status to users and update deposit status but for success transaction merchant must use data from HTTP Post with Json to update the deposit status.

URL TO BE POSTED TO PAYMENT GATEWAY

Demo/Test Site: https://api-demo.mxpay.asia/WebForm/Deposit.aspx

Live Site: https://api./WebForm/Deposit.aspx

DATA TO BE POSTED TO PAYMENT GATEWAY

Element Name	Type	Max Length	Required	Description
MerchantCode	String	-	Yes	Merchant code that given by Payment Gateway upon application. Case-sensitive.
TransNum	String	50	Yes	Transaction number that provided from merchant own platform system. Note: Value must be unique.
Currency	String	5	Yes	Deposit currency code. See APPENDIX CURRRENCY.
Amount	Numeric	-	Yes	Deposit amount. Note: For example, 100 and 2000.50 but for Currency EUSDT, TUSDT and BTC are allowed up to 6 decimal places such as 20.123456.
PaymentDesc	String	300	Optional	Deposit description. Empty is allowed.
FirstName	String	50	Yes	Customer first name, customer bank account name, customer ID, or equivalent Note: Value must be unique, and then for IDR Currency, compulsory to insert customer's registered bank account name that used for deposit DO NOT insert customer ID.
LastName	String	50	Optional	Customer last name, customer ID or equivalent Empty is allowed. Note: Value must be unique.
EmailAddress	String	100	Optional	Customer email. Empty is allowed.
PhoneNum	String	50	Optional	Customer phone number. Empty is allowed.
Address	String	300	Optional	Customer address. Empty is allowed.
City	String	50	Optional	Customer city. Empty is allowed.
State	String	50	Optional	Customer state. Empty is allowed.
Country	String	3	Yes	Customer country. See APPENDIX COUNTRY.
Postcode	String	50	Optional	Customer postcode. Empty is allowed.
MerchantRemark	String	300	Optional	Merchant deposit remarks. Empty is allowed.
Signature	String	-	Yes	Encrypted Signature. See HOW TO BUILD SIGNATURE below.
RedirectUrl	String	-	Optional	This url value is for own reference. Empty is allowed. Note: This parameter is optional and NOT for your redirection purpose. You can choose to pass any value and that same value will returned in HTTP Get postback data for your reference.
TransProvider	String	-	Optional	Adding this parameter, Payment Gateway will skip default payment selection page and redirect to the chosen bank provider page: Note: This is NOT applicable to test in DEMO environment. 2 = Malaysia - Maybank 3 = Malaysia – CIMB Bank 4 = Malaysia – BSN 5 = Malaysia – Public Bank 6 = Malaysia – RHB Bank 7 = Malaysia – Alliance Bank 11 = Malaysia – Hong Leong Bank 15 = Malaysia – Bank Islam 19 = Malaysia – Affin Bank 101 = Malaysia – Touch N Go 102 = Malaysia – GrabPay 103 = Malaysia - ShopeePay 104 = Malaysia - Boost 105 = Malaysia – DuitNow 451 = India - UPI 550 = Vietnam – Momopay 551 = Vietnam – ZaloPay 552 = Vietnan – ViettelPay 553 = Vietnam – Bank Transfer (Manual) 554 = Vietnam – Bank Transfer (QR) 601 = Brunei – Baiduri Bank 801 = Crypto - EUSDT 802 = Crypto - TUSDT 803 = Crypto - BTC 901 = Singapore - DBS 902 = Singapore – OCBC 903 = Singapore - UOB 1001 = All Credit Cards 2101 = Digi 2102 = Maxis 2103 = Celcom 2104 = UMobile 2105 = Touch N Go PIN 4001 = Thailand - PromptPay 9051 = Bangladesh - Bkash 9052 = Bangladesh - Nagad 9053 = Bangladesh - Upay 9054 = Bangladesh - Rocket

HOW TO POST DATA BY HTTP POST IN HTML FORM

Example in HTML

Merchant need to use HTML Form to post data to payment gateway.

                                                    
                                                          <form action="https://api./WebForm/Deposit.aspx" method="POST"><br>
                                                                <input name="MerchantCode" value="M1234567"><br>
                                                                <input name="TransNum" value="T1234"><br>
                                                                <input name="Currency" value="MYR"><br>
                                                                <input name="Amount" value="10.00"><br>
                                                                <input name="PaymentDesc" value=""><br>
                                                                <input name="FirstName" value="PE002"><br>
                                                                <input name="LastName" value=""><br>
                                                                <input name="EmailAddress" value=""><br>
                                                                <input name="PhoneNum" value=""><br>
                                                                <input name="Address" value=""><br>
                                                                <input name="City" value=""><br>
                                                                <input name="State" value=""><br>
                                                                <input name="Country" value="MYS"><br>
                                                                <input name="Postcode" value=""><br>
                                                                <input name="MerchantRemark" value=""><br>
                                                                <input name="Signature" value="f01f72b40dc10c09e88a2df242bfb172fbc77d53acb788c2eb78160b3ebc250c"><br>
                                                                <input name="submit" type="submit">
                                                            <form>

HOW TO BUILD SIGNATURE

Signature is an encrypted SHA256 string of concatenation of MerchantCode + SecretKey + TransNum + Currency + Amount.

For example,
MerchantCode: M1234567
SecretKey: bb841904-4eea-44e5-8ca3-0af1e304ff4f
TransNum: T1234
Currency: MYR
Amount: 10.00

String to be encrypted: M1234567bb841904-4eea-44e5-8ca3-0af1e304ff4fT1234MYR10.00
Signature: f01f72b40dc10c09e88a2df242bfb172fbc77d53acb788c2eb78160b3ebc250c

Click below links to see the example ENCRYPTION ALGORITHM TO GENERATE SHA256 VALUE.

ENCRYPTION ALGORITHM TO GENERATE SHA256 VALUE

Example in C#
Example in PHP

Below is the example of encryption algorithm in C# to generate the SHA256 value:

                                                        
                                                            protected void Page_Load(object sender, EventArgs e)
                                                            {
                                                                // concatenation 
                                                                var concateString = string MerchantCode + string SecretKey + string TransNum + string Currency + int Amount;
                                                                var hash = StringToSha256Hash(concateString);

                                                                //display the output via javascript alert box
                                                                Response.WriteLine($"<script>alert('{hash}');<script>");

                                                                //display the output via console
                                                                Console.WriteLine(hash);
                                                            }

                                                            public static string StringToSha256Hash(string OrgValue)
                                                            {
                                                                // Create a SHA256
                                                                using (SHA256 sha256Hash = SHA256.Create())
                                                                {
                                                                    // ComputeHash - returns byte array
                                                                    byte[] bytes = sha256Hash.ComputeHash(Encoding.UTF8.GetBytes(OrgValue));

                                                                    // Convert byte array to a string
                                                                    StringBuilder builder = new StringBuilder();
                                                                    for (int i = 0; i < bytes.Length; i++)
                                                                    {
                                                                        builder.Append(bytes[i].ToString("x2"));
                                                                    }
                                                                    return builder.ToString();
                                                                }
                                                            }

Below is the example of encryption algorithm in PHP to generate the SHA256 value:

                                                        
                                                            <?php 
                                                            $concate = $MerchantCode . $SecretKey . $TransNum. $Currency. $Amount;
                                                            $hash = hash('sha256', $concate, true);
                                                            $hex = bin2hex($hash);
                                                            echo $hex;
                                                            ?>

DATA TO BE RETURNED BY PAYMENT GATEWAY

URL Argument Name	Description
DepositId	Unique deposit reference number that returned by Payment Gateway. Only return for success deposits.
Result	10001 = Success 10002 = Failed 10004 = Pending (Only for transactions of UPI, PromptPay and Crypto)
MerchantCode	Merchant code that given by Payment Gateway upon application. Case-sensitive. Only return for success deposits.
TransNum	Transaction number that provided from merchant own platform system. Value must be unique.
FromBank	Customer bank. Only return for success deposits.
ToBank	Receiving bank. Only return for success deposits.
BankAccountNum	Receiving bank account number. Only return for success deposits.
Currency	Deposit currency code. Only return for success deposits.
Amount	Deposit amount. Only return for success deposits.
MerchantFeePercentage	Merchant fee in percentage. Only return for success deposits.
MerchantFee	Merchant fee in numeric. Only return for success deposits.
PaymentDesc	Deposit description. Only return for success deposits.
FirstName	Customer first name, customer bank account name, customer ID, or equivalent. Value must be unique. Only return for success deposits.
LastName	Customer last name, customer ID or equivalent. Value must be unique. Only return for success deposits.
EmailAddress	Customer email. Only return for success deposits.
PhoneNum	Customer phone number. Only return for success deposits.
Address	Customer address. Only return for success deposits.
City	Customer city. Only return for success deposits.
State	Customer state. Only return for success deposits.
Country	Customer country. Only return for success deposits.
Postcode	Customer postcode. Only return for success deposits.
MerchantRemark	Merchant deposit remarks. Only return for success deposits.
CheckString	Unique encryption string that returned by Payment Gateway. See HOW TO BUILD CHECKSTRING below.
CheckString2	Unique encryption string that returned by Payment Gateway. See HOW TO BUILD CHECKSTRING2 below. Only return for success deposits.
RedirectUrl	Url value for own reference.

HOW TO BUILD CHECKSTRING

CheckString is an encrypted SHA256 string of concatenation of MerchantCode + SecretKey + TransNum

For example,
MerchantCode: M1234567
SecretKey: bb841904-4eea-44e5-8ca3-0af1e304ff4f
TransNum: T1234

String to be encrypted: M1234567bb841904-4eea-44e5-8ca3-0af1e304ff4fT1234
CheckString: 1ab99207abc9de6f9ef66b5f9603e951ac99f990249a103987e742a499edf870

Click below links to see the example ENCRYPTION ALGORITHM TO GENERATE SHA256 VALUE.

HOW TO BUILD CHECKSTRING2

CheckString2 is an encrypted SHA256 string of concatenation of Reversed (MerchantCode + TransNum) + SecretKey.

For example,
MerchantCode: M1234567
SecretKey: bb841904-4eea-44e5-8ca3-0af1e304ff4f
TransNum: T1234

String to be encrypted: 7654321M4321Tbb841904-4eea-44e5-8ca3-0af1e304ff4f
CheckString2: b1b5212bc966f02915d65cd5078332d8b51ace94fa39372418be76eff6ea7703

*IMPORTANT*:
1. Merchant MUST use returned CheckString2 to check data accuracy on its end.
2. Merchant MUST validate the returned Amount with your Amount before update to player’s account
3. Merchant MUST only accept the HTTP Post (With JSON) from our IP addresses.

Click below links to see the example ENCRYPTION ALGORITHM TO GENERATE SHA256 VALUE.

HTTP GET REDIRECTED BY PAYMENT GATEWAY

The Payment Gateway makes a HTTP Get to Merchant for all status of deposits with the following data:

1. Result
2. TransNum
3. Amount - Only return for success deposits
4. DepositId - Only return for success deposits
5. FromBank - Only return for success deposits
6. ToBank - Only return for success deposits
7. BankAccNum - Only return for success deposits
8. RedirectUrl
9. CheckString
10. CheckString2 - Only return for success deposits

Below is the example of Http Get on failed deposit:

                                                        
                                                            https://www.example.com/Deposit_Response.aspx?Result=10002&TransNum=T1234&RedirectUrl=https%3a%2f%2fwww.abcdef.com&CheckString=1ab99207abc9de6f9ef66b5f9603e951ac99f990249a103987e742a499edf870

Below is the example of Http Get on pending deposit:

                                                        
                                                            https://www.example.com/Deposit_Response.aspx?Result=10004&TransNum=T1234&RedirectUrl=https%3a%2f%2fwww.abcdef.com&CheckString=1ab99207abc9de6f9ef66b5f9603e951ac99f990249a103987e742a499edf870

Below is the example of Http Get on success deposit:

                                                        
                                                            https://www.example.com/Deposit_Response.aspx?Result=10001&TransNum=T1234&Currency=MYR&Amount=10.00&DepositId=8811967&FromBank=Maybank%20Bank&ToBank=CIMB%20Bank&BankAccNum=123456789&RedirectUrl=https%3a%2f%2fwww.abcdef.com&CheckString=1ab99207abc9de6f9ef66b5f9603e951ac99f990249a103987e742a499edf870&CheckString2=b1b5212bc966f02915d65cd5078332d8b51ace94fa39372418be76eff6ea7703

HTTP POST (WITH JSON) SEND BY PAYMENT GATEWAY

The Payment Gateway makes a HTTP Post (with JSON) to Merchant ONLY for success deposits with the following data:

1. DepositId
2. Result
3. MerchantCode
4. TransNum
5. FromBank
6. ToBank
7. BankAccountNum
8. Currency
9. Amount
10. MerchantFeePercentage
11. MerchantFee
12. PaymentDesc
13. FirstName
14. LastName
15. EmailAddress
16. PhoneNum
17. Address
18. City
19. State
20. Country
21. Postcode
22. MerchantRemark
23. CheckString
24. CheckString2
25. RedirectUrl

Below is the sample of success deposit in JSON send by payment gateway:

                                                        
                                                            {"DepositId":"8811967","Result":"10001","MerchantCode":"M1234567","TransNum":"T1234",
                                                            "FromBank":"Maybank","ToBank":"CIMB","BankAccountNum":"123456789","Currency":"MYR","Amount":"10.00",
                                                            "MerchantFeePercentage":0.02,"MerchantFee":0.2,"PaymentDesc":"","FirstName":"PE002","LastName":"",
                                                            "EmailAddress":"","PhoneNum":"","Address":"","City":"","State":"","Country":"","Postcode":"",
                                                            "MerchantRemark":"","CheckString":"1ab99207abc9de6f9ef66b5f9603e951ac99f990249a103987e742a499edf870",
                                                            "CheckString2":"b1b5212bc966f02915d65cd5078332d8b51ace94fa39372418be76eff6ea7703"}

Reads JSON using HTTP Request Stream. Below is the syntax to capture the JSON in C#:

                                                        
                                                            //get JSON
                                                            string result = "";
                                                            using (var reader = new System.IO.StreamReader(Request.InputStream))
                                                            {
                                                                result = reader.ReadToEnd();
                                                            }

                                                            //write JSON to file
                                                            using (System.IO.StreamWriter file = new System.IO.StreamWriter(@"C:\Temp\DepositResult.txt"))
                                                            {
                                                                file.WriteLine(result);
                                                            }

Reads JSON using HTTP Request Stream. Below is the syntax to capture the JSON in PHP:

                                                        
                                                            json_decode(file_get_contents('php://input'), true)

DEPOSIT - CRYPTO

HOW IT WORKS

This API section is only made for Cryptocurrency deposit submission without payment page selection. Please refer back to DEPOSIT section if you wish to use crypto payment with payment page.
Merchant posts deposit data to Payment Gateway using HTTP Post. Refer to DATA TO BE POSTED TO PAYMENT GATEWAY below.
Payment Gateway processes payment and return a HTTP Post with JSON to URL that provided by Merchant. The JSON contains detailed deposit data. Refer to HTTP POST (WITH JSON) BY PAYMENT GATEWAY below.
Merchant may uses the JSON data for next course of action, such as retrieving the wallet address, show status to users and update deposit status.

URL TO BE POSTED TO PAYMENT GATEWAY

Demo/Test Site: -

Live Site: https://job1.mxpay.asia/PublicApi/Deposit_Crypto

DATA TO BE POSTED TO PAYMENT GATEWAY

Element Name	Type	Max Length	Required	Description
MerchantCode	String	-	Yes	Merchant code that given by Payment Gateway upon application. Case-sensitive.
TransNum	String	50	Yes	Transaction number that provided from merchant own platform system. Note: Value must be unique.
Currency	String	5	Yes	Deposit currency code. Note: Value insert EUSDT or TUSDT only.
Amount	Numeric	-	Yes	Deposit amount. Note: Allowed up to 6 decimal places such as 20.123456.
PaymentDesc	String	300	Optional	Deposit description. Empty is allowed.
FirstName	String	50	Yes	Customer first name, customer bank account name, customer ID, or equivalent Note: Value must be unique, and then for IDR Currency, compulsory to insert customer's registered bank account name that used for deposit DO NOT insert customer ID.
LastName	String	50	Optional	Customer last name, customer ID or equivalent Empty is allowed. Note: Value must be unique.
EmailAddress	String	100	Optional	Customer email. Empty is allowed.
PhoneNum	String	50	Optional	Customer phone number. Empty is allowed.
Address	String	300	Optional	Customer address. Empty is allowed.
City	String	50	Optional	Customer city. Empty is allowed.
State	String	50	Optional	Customer state. Empty is allowed.
Country	String	3	Yes	Customer country. See APPENDIX COUNTRY.
Postcode	String	50	Optional	Customer postcode. Empty is allowed.
MerchantRemark	String	300	Optional	Merchant deposit remarks. Empty is allowed.
Signature	String	-	Yes	Encrypted Signature. See HOW TO BUILD SIGNATURE below.

HOW TO POST DATA BY HTTP POST IN HTML FORM

Example in HTML

Merchant need to use HTML Form to post data to payment gateway.

                                                    
                                                          <form action="https://job1.mxpay.asia/PublicApi/Deposit_Crypto" method="POST"><br>
                                                                <input name="MerchantCode" value="M1234567"><br>
                                                                <input name="TransNum" value="T1234"><br>
                                                                <input name="Currency" value="TUSDT"><br>
                                                                <input name="Amount" value="78.123456"><br>
                                                                <input name="PaymentDesc" value=""><br>
                                                                <input name="FirstName" value="PE002"><br>
                                                                <input name="LastName" value=""><br>
                                                                <input name="EmailAddress" value=""><br>
                                                                <input name="PhoneNum" value=""><br>
                                                                <input name="Address" value=""><br>
                                                                <input name="City" value=""><br>
                                                                <input name="State" value=""><br>
                                                                <input name="Country" value="MYS"><br>
                                                                <input name="Postcode" value=""><br>
                                                                <input name="MerchantRemark" value=""><br>
                                                                <input name="Signature" value="f01f72b40dc10c09e88a2df242bfb172fbc77d53acb788c2eb78160b3ebc250c"><br>
                                                                <input name="submit" type="submit">
                                                            <form>

HOW TO BUILD SIGNATURE

Signature is an encrypted SHA256 string of concatenation of MerchantCode + SecretKey + TransNum + Currency + Amount.

For example,
MerchantCode: M1234567
SecretKey: bb841904-4eea-44e5-8ca3-0af1e304ff4f
TransNum: T1234
Currency: TUSDT
Amount: 78.123456

String to be encrypted: M1234567bb841904-4eea-44e5-8ca3-0af1e304ff4fT1234TUSDT78.123456
Signature: 96b7ff60235af579f9f6367217ce2006e4f9b20581849e84db9beb285dbbde9d

Click below links to see the example ENCRYPTION ALGORITHM TO GENERATE SHA256 VALUE.

DATA TO BE RETURNED BY PAYMENT GATEWAY

URL Argument Name	Description
DepositId	Unique deposit reference number that returned by Payment Gateway. Only return for success deposits.
Result	10001 = Success 10002 = Failed 10004 = Pending (Only for transactions of UPI, PromptPay and Crypto)
MerchantTransNum	Transaction number that provided from merchant own platform system. Value must be unique.
Currency	Deposit currency code. Only return for success deposits.
Amount	Deposit amount. Only return for success deposits.
QrImagePath	Path of the QR image. Only return for success deposits.
WalletAddress	Deposit wallet address for crypto. Only return for success deposits.
CheckString	Unique encryption string that returned by Payment Gateway. See HOW TO BUILD CHECKSTRING below.

HOW TO BUILD CHECKSTRING

CheckString is an encrypted SHA256 string of concatenation of DepositId + MerchantCode + SecretKey + TransNum + Currency + Amount

For example,
DepositId: 8811967
MerchantCode: M1234567
SecretKey: bb841904-4eea-44e5-8ca3-0af1e304ff4f
TransNum: T1234
Currency: TUSDT
Amount: 78.123456

String to be encrypted: 8811967M1234567bb841904-4eea-44e5-8ca3-0af1e304ff4fT1234TUSDT78.123456
CheckString: 05bb486cce39080468d98e0227e9b7a5d0181ca5d74ca4237ee8e021a7f981b0

Click below links to see the example ENCRYPTION ALGORITHM TO GENERATE SHA256 VALUE.

HTTP POST (WITH JSON) SEND BY PAYMENT GATEWAY

The Payment Gateway makes a HTTP Post (with JSON) to Merchant ONLY for success deposits with the following data:

1. DepositId
2. Result
3. MerchantTransNum
4. Currency
5. Amount
6. QrImagePath
7. WalletAddress
8. CheckString

Below is the example of Http Post (with JSON) on failed deposit:

                                                    
                                                            {"Result":"10002","Message":""}

Below is the example of Http Post (with JSON) on pending deposit:

                                                    
                                                            {"Result":"10004","Message":""}

Below is the example of Http Post (with JSON) on success deposit:

                                                    
                                                            {"Result":"10001","DepositId":"8811967","MerchantTransNum":"T1234","Currency":"TUSDT","Amount":"78.123456",
                                                            "QrImagePath":"https://payessence.vcoin-pay.com/qrcode?u=0xDDDdC7Ce5A803E1Fff03aD2cF512d21104730BbA",
                                                            "WalletAddress":"0xDDDdC7Ce5A803E1Fff03aD2cF512d21104730BbA",
                                                            "CheckString":"b0cd40bf57c0a7b8553029df7e51dae0a3ebd8eed55451f6106e0f5b8113750c"}

DEPOSIT STATUS CHECK (REDIRECT METHOD)

HOW IT WORKS

Merchant posts check data to Payment Gateway using HTTP Post. Refer to DATA TO BE POSTED TO PAYMENT GATEWAY below.
Payment Gateway checks the status of the deposit and redirects back to Merchant using HTTP Get with the Deposit Status Check URL provided by Merchant. Refer to HTTP GET REDIRECTED BY PAYMENT GATEWAY below.

URL TO BE POSTED TO PAYMENT GATEWAY

Demo/Test Site: https://job1-demo.mxpay.asia/WebForm/Deposit_StatusCheck.aspx

Live Site: https://job1.mxpay.asia/WebForm/Deposit_StatusCheck.aspx

DATA TO BE POSTED TO PAYMENT GATEWAY

Element Name	Type	Max Length	Required	Description
MerchantCode	String	-	Yes	Merchant code that given by Payment Gateway upon application. Case-sensitive.
MerchantTransNum	String	50	Yes	Transaction number that provided from merchant own platform system. Note: Value must be unique.
CheckString	String	-	Yes	Encrypted CheckString. See HOW TO BUILD CHECKSTRING below.

HOW TO POST DATA BY HTTP POST IN HTML FORM

Example in HTML

Merchant need to use HTML Form to post data to payment gateway.

                                                        
                                                            <form action="https://job1.mxpay.asia/WebForm/Deposit_StatusCheck.aspx" method="POST"><br>
                                                                <input name="MerchantCode" value="M1234567"><br>
                                                                <input name="MerchantTransNum" value="T1234"><br>
                                                                <input name="CheckString" value="1ab99207abc9de6f9ef66b5f9603e951ac99f990249a103987e742a499edf870"><br>
                                                                <input name="submit" type="submit">
                                                            <form>

HOW TO BUILD CHECKSTRING

CheckString is an encrypted SHA256 string of concatenation of MerchantCode + SecretKey + MerchantTransNum

For example,
MerchantCode: M1234567
SecretKey: bb841904-4eea-44e5-8ca3-0af1e304ff4f
MerchantTransNum: T1234

String to be encrypted: M1234567bb841904-4eea-44e5-8ca3-0af1e304ff4fT1234
CheckString: 1ab99207abc9de6f9ef66b5f9603e951ac99f990249a103987e742a499edf870

Click below links to see the example ENCRYPTION ALGORITHM TO GENERATE SHA256 VALUE.

DATA TO BE RETURNED BY PAYMENT GATEWAY

URL Argument Name	Description
MerchantCode	Merchant code that given by Payment Gateway upon application. Case-sensitive.
MerchantTransNum	Transaction number that provided from merchant own platform system. Value must be unique
CheckString	See HOW TO BUILD CHECKSTRING above.
Result	1201 = Merchant Transaction No. is not defined. 1202 = Invalid Merchant Transaction No. 1203 = Merchant Transaction No. not found. 1204 = More than one Merchant Transaction No. found. 1301 = Check String is not defined. 1302 = Invalid Check String. 2001 = Deposit Status is Registered. User has been redirect to Payment Gateway and yet making any payment. 2002 = Deposit Status is Processing. 2101 = Deposit Status is Success. 2102 = Deposit Status is Failed. 2201 = Deposit Status is Deposit Appeal on failed deposit. 2202 = Deposit Status is Appealed and Success. 2203 = Deposit Status is Appealed and Failed.

HTTP GET REDIRECTED BY PAYMENT GATEWAY

The Payment Gateway makes a HTTP Get to Merchant for deposit status check with the following data:

1. MerchantCode
2. MerchantTransNum
3. CheckString
4. Result

Below is the example of Http Get on failed deposit status check:

                                                        
                                                            https://www.example.com/WebForm/Deposit_StatusCheck_Response.aspx?MerchantCode=M1234567&MerchantTransNum=T1234&CheckString=1ab99207abc9de6f9ef66b5f9603e951ac99f990249a103987e742a499edf870&Result=2102

Below is the example of Http Get on pending deposit status check:

                                                        
                                                            https://www.example.com/WebForm/Deposit_StatusCheck_Response.aspx?MerchantCode=M1234567&MerchantTransNum=T1234&CheckString=1ab99207abc9de6f9ef66b5f9603e951ac99f990249a103987e742a499edf870&Result=2002

Below is the example of Http Get on success deposit status check:

                                                        
                                                            https://www.example.com/WebForm/Deposit_StatusCheck_Response.aspx?MerchantCode=M1234567&MerchantTransNum=T1234&CheckString=1ab99207abc9de6f9ef66b5f9603e951ac99f990249a103987e742a499edf870&Result=2101

DEPOSIT STATUS CHECK (BACK-TO-BACK METHOD)

HOW IT WORKS

Merchant posts check data to Payment Gateway using HTTP Post. Refer to DATA TO BE POSTED TO PAYMENT GATEWAY below.
Payment Gateway checks the status of the deposit and return JSON to Merchant.

URL TO BE POSTED TO PAYMENT GATEWAY

Demo/Test Site: https://job1-demo.mxpay.asia/WebForm/Deposit_StatusCheck_Json.aspx

Live Site: https://job1.mxpay.asia/WebForm/Deposit_StatusCheck_Json.aspx

DATA TO BE POSTED TO PAYMENT GATEWAY

Element Name	Type	Max Length	Required	Description
MerchantCode	String	-	Yes	Merchant code that given by Payment Gateway upon application. Case-sensitive.
MerchantTransNum	String	50	Yes	Transaction number that provided from merchant own platform system. Note: Value must be unique.
CheckString	String	-	Yes	Encrypted CheckString. See HOW TO BUILD CHECKSTRING below.

HOW TO POST DATA BY HTTP POST IN HTML FORM

Example in HTML

Merchant need to use HTML Form to post data to payment gateway.

                                                        
                                                            <form action="https://job1.mxpay.asia/WebForm/Deposit_StatusCheck_Json.aspx" method="POST"><br>
                                                                <input name="MerchantCode" value="M1234567"><br>
                                                                <input name="MerchantTransNum" value="T1234"><br>
                                                                <input name="CheckString" value="1ab99207abc9de6f9ef66b5f9603e951ac99f990249a103987e742a499edf870"><br>
                                                                <input name="submit" type="submit">
                                                            <form>

HOW TO BUILD CHECKSTRING

CheckString is an encrypted SHA256 string of concatenation of MerchantCode + SecretKey + MerchantTransNum

For example,
MerchantCode: M1234567
SecretKey: bb841904-4eea-44e5-8ca3-0af1e304ff4f
MerchantTransNum: T1234

String to be encrypted: M1234567bb841904-4eea-44e5-8ca3-0af1e304ff4fT1234
CheckString: 1ab99207abc9de6f9ef66b5f9603e951ac99f990249a103987e742a499edf870

Click below links to see the example ENCRYPTION ALGORITHM TO GENERATE SHA256 VALUE.

DATA TO BE RETURNED BY PAYMENT GATEWAY

URL Argument Name	Description
DepositId	Unique deposit reference number that returned by Payment Gateway. Only return for success deposits.
Result	1201 = Merchant Transaction No. is not defined. 1202 = Invalid Merchant Transaction No. 1203 = Merchant Transaction No. not found. 1204 = More than one Merchant Transaction No. found. 1301 = Check String is not defined. 1302 = Invalid Check String. 2001 = Deposit Status is Registered. User has been redirect to Payment Gateway and yet making any payment. 2002 = Deposit Status is Processing. 2101 = Deposit Status is Success. 2102 = Deposit Status is Failed. 2201 = Deposit Status is Deposit Appeal on failed deposit. 2202 = Deposit Status is Appealed and Success. 2203 = Deposit Status is Appealed and Failed.
MerchantCode	Merchant code that given by Payment Gateway upon application. Case-sensitive. Only return for success deposits.
TransNum	Transaction number that provided from merchant own platform system. Value must be unique. Only return for success deposits.
FromBank	Customer Bank. Only return for success deposits.
ToBank	Receiving Bank. Only return for success deposits.
BankAccountNum	Receiving bank account number. Only return for success deposits.
Currency	Deposit currency code. Only return for success deposits.
Amount	Deposit amount. Only return for success deposits.
MerchantFeePercentage	Merchant fee in percentage. Only return for success deposits.
MerchantFee	Merchant fee in numeric. Only return for success deposits.
PaymentDesc	Deposit description. Only return for success deposits.
FirstName	Customer first name, customer bank account name, customer ID, or equivalent. Value must be unique. Only return for success deposits.
LastName	Customer last name, customer ID or equivalent Value must be unique Only return for success deposits.
EmailAddress	Customer email. Only return for success deposits.
PhoneNum	Customer phone number. Only return for success deposits.
Address	Customer address. Only return for success deposits.
City	Customer city. Only return for success deposits.
State	Customer state. Only return for success deposits.
Country	Customer country. Only return for success deposits.
Postcode	Customer postcode. Only return for success deposits.
MerchantRemark	Merchant deposit remarks. Only return for success deposits.
Message	Notifications or error message that return from acquirers or banks provider.
CheckString	Unique encryption string that returned by Payment Gateway. See HOW TO BUILD CHECKSTRING above. Only return for success deposits.

HTTP POST (WITH JSON) SEND BY PAYMENT GATEWAY

The Payment Gateway makes a HTTP Post (with JSON) to Merchant for deposit status check with the following data:

Below is the example of Http Post (with JSON) on failed deposit status check:

                                                        
                                                            {"Result":"2102","Message":""}

Below is the example of Http Post (with JSON) on pending deposit status check:

                                                        
                                                            {"Result":"2002","Message":""}

Below is the example of Http Post (with JSON) on success deposit status check:

                                                        
                                                            {"DepositId":"8811967","Result":"2101","MerchantCode":"M1234567","TransNum":"T1234",
                                                             "FromBank":"Dummy Bank","ToBank":"Dummy Bank", "BankAccountNum": "123456789", "Currency":"MYR",
                                                             "Amount":"10.00", "MerchantFeePercentage":0.02, "MerchantFee":0.2,"PaymentDesc":"","FirstName":"PE002",
                                                             "LastName":"","EmailAddress":"user@gmail.com","PhoneNum":"","Address":"","City":"","State":"", "Country":"",
                                                             "Postcode":"", "MerchantRemark":"", "Message":"","CheckString": "1ab99207abc9de6f9ef66b5f9603e951ac99f990249a103987e742a499edf870"}

PAYOUT - AUTOMATED (REDIRECT METHOD)

HOW IT WORKS

Merchant posts payout data to Payment Gateway using HTTP Post. Refer to DATA TO BE POSTED TO PAYMENT GATEWAY below.
Payment Gateway registers, processes and redirects back to Merchant using HTTP Get (with JSON) to the Payout URL provided by Merchant. Refer to HTTP GET REDIRECTED BY PAYMENT GATEWAY and HTTP GET (WITH JSON) SEND BY PAYMENT GATEWAY below.
Payment Gateway processes the pending payout and make a HTTP Get (with JSON) to Merchant with result Approved or Rejected. Refer to HTTP GET REDIRECTED BY PAYMENT GATEWAY and HTTP GET (WITH JSON) SEND BY PAYMENT GATEWAY below.

URL TO BE POSTED TO PAYMENT GATEWAY

Demo/Test Site: https://job1-demo.mxpay.asia/WebForm/Deposit_P2pPayout2.aspx

Live Site: https://job1.mxpay.asia/WebForm/Deposit_P2pPayout2.aspx

DATA TO BE POSTED TO PAYMENT GATEWAY

Element Name	Type	Max Length	Required	Description
MerchantCode	String	-	Yes	Merchant code that given by Payment Gateway upon application. Case-sensitive.
MerchantTransNum	String	50	Yes	Transaction number that provided from merchant own platform system. Note: Value must be unique.
CurrencyTypeId	Numeric	1	Yes	1 = MYR 8 = VND 1001 = EUSDT 1002 = TUSDT
ToBankId	String	2	Yes	1 = Malaysia - Maybank 2 = Malaysia – CIMB Bank 3 = Malaysia – RHB Bank 4 = Malaysia - Public Bank 5 = Malaysia - Hong Leong Bank 6 = Malaysia - Alliance Bank 7 = Malaysia - Bank Islam 8 = Malaysia - Affin Bank 9 = Malaysia - AmBank 10 = Malaysia – BSN 11 = Malaysia – Touch N Go eWallet 12 = Malaysia – GX Bank 13 = Malaysia – Bank Rakyat 14 = Malaysia – Ryt Bank 15 = Malaysia – United Overseas Bank 16 = Malaysia – OCBC Bank 17 = Malaysia – Bank Muamalat 18 = Malaysia – Standard Chartered Bank 20 = Malaysia – Boost Bank 21 = Malaysia – Boost Ewallet 22 = Malaysia – BigPay 23 = Malaysia – Bank Pertanian (AgroBank) 24 = Malaysia – CitiBank Berhad 25 = Malaysia – Al-Rajhi Bank 26 = Malaysia – HSBC Bank 27 = Malaysia – MUFG Bank 101 = Vietnam - Asia Commercial Bank 102 = Vietnam - BIDV 103 = Vietnam - Military Commercial Bank 104 = Vietnam - Dong A Bank 105 = Vietnam - EXIMBANK 106 = Vietnam - Saigon Hanoi Commercial Joint Stock Bank 107 = Vietnam - HD Bank 108 = Vietnam - Sacombank 109 = Vietnam - AGRIBANK 110 = Vietnam - TECHCOMBANK 111 = Vietnam - VietinBank 112 = Vietnam - Vietcombank Note: For Crypto Currency, please set to “0”.
ToBankAccountName	String	100	Yes	Customer bank account name. Note: For Crypto Currency, please leave EMPTY.
ToBankAccountNum	String	50	Yes	Customer bank account number. Note: Customer wallet address (for Crypto Currency), Customer duitnow/mobile phone number (for TNG eWallet).
Amount	Numeric	-	Yes	Payout amount. Note: For example, 100 and 2000.50 but for Currency EUSDT, TUSDT and BTC are allowed up to 6 decimal places such as 20.123456.
BankIdentifierCode	String	50	Optional	IFSC code for INR only. Note: May skip if not using INR Currency.
Signature	String	-	Yes	Encrypted Signature. See HOW TO BUILD SIGNATURE below.

HOW TO POST DATA BY HTTP POST IN HTML FORM

Example in HTML

Merchant need to use HTML Form to post data to payment gateway.

                                                        
                                                            <form action="https://job1.mxpay.asia/WebForm/Deposit_P2pPayout2.aspx" method="POST"><br>
                                                                <input name="MerchantCode" value="M1234567"><br>
                                                                <input name="MerchantTransNum" value="T1234"><br>
                                                                <input name="CurrencyTypeId" value="1"><br>
                                                                <input name="ToBankId" value="1"><br>
                                                                <input name="ToBankAccountName" value="PE002"><br>
                                                                <input name="ToBankAccountNum" value="123456789"><br>
                                                                <input name="Amount" value="10.00"><br>
                                                                <input name="BankIdentifierCode" value=""><br>
                                                                <input name="Signature" value="98696ab7dc6e0da2215bc4421b6724c8aa6e3bd33a264542b9393b404457344f"><br>
                                                                <input name="submit" type="submit">
                                                            <form>

HOW TO BUILD SIGNATURE

Signature is an encrypted SHA256 string of concatenation of MerchantCode + SecretKey + MerchantTransNum + ToBankId + ToBankAccountNum + CurrencyTypeId + Amount.

For example,
MerchantCode: M1234567
SecretKey: bb841904-4eea-44e5-8ca3-0af1e304ff4f
MerchantTransNum: T1234
ToBankId: 1
ToBankAccountNum: 123456789
CurrencyTypeId: 1
Amount: 10.00

String to be encrypted: M1234567bb841904-4eea-44e5-8ca3-0af1e304ff4fT12341123456789110.00
Signature: 98696ab7dc6e0da2215bc4421b6724c8aa6e3bd33a264542b9393b404457344f

Click below links to see the example ENCRYPTION ALGORITHM TO GENERATE SHA256 VALUE.

DATA TO BE RETURNED BY PAYMENT GATEWAY

URL Argument Name	Description
PayoutId	Unique payout reference number that returned by Payment Gateway.
Result	35001 = Payout is Pending. 35002 = Payout is Success. 35003 = Payout is Rejected. 35004 = Payout is Processing. 1101 = Merchant Code Not Defined. 1102 = Merchant Code Invalid. 1201 = Merchant Payout No. is not defined. 1202 = Invalid Merchant Payout No. 1203 = More than one Merchant Transaction No. found. 1301 = Currency Code is not defined. 1302 = Invalid Currency Code. 1401 = Amount is not defined. 1402 = Invalid Amount. 1403 = Amount’s Requirement Not Met. 1501 = Bank Name is not defined. 1502 = Invalid Bank Name or exceed length. 1503 = Bank Name not matched – Refer to Appendix Bank. 1601 = Account Name is not defined. 1602 = Invalid Account Name. 1701 = Account Number is not defined. 1702 = Invalid Account Number. 1801 = Signature is not defined. 1802 = Invalid Signature. 1901 = Redirect URL not set. 2001 = System Error. 2101 = Bank Identifier Code is not defined. 2102 = Invalid Bank Identifier Code or exceed length. 2301 = To Bank Id is not defined. 2302 = To Bank Id is invalid. 2401 = To Bank Account Name is not defined. 2402 = To Bank Account Name is invalid. 2501 = To Bank Account No. is not defined. 2502 = To Bank Account No. is invalid. 2601 = System is invalid. 2602 = System is offline. 2701 = Merchant’s Payout Account is inactive. 2801 = Merchant IP Address Invalid (Whitelisting is needed).
MerchantCode	Merchant code that given by Payment Gateway upon application. Case-sensitive.
MerchantTransNum	Transaction number that provided from merchant own platform system. Value must be unique.
CurrencyTypeId	Payout currency type id.
ToBankId	Customer bank id selection.
ToBankAccountNum	Customer bank account number.
Amount	Payout amount.
Remarks	Merchant payout remarks.
CheckString2	Unique encryption string that returned by Payment Gateway. See HOW TO BUILD CHECKSTRING2 below.

HOW TO BUILD CHECKSTRING2

CheckString2 is an encrypted SHA256 string of concatenation of concatenation of MerchantCode + SecretKey + MerchantTransNum + PayoutId + ToBankId + ToBankAccountNum + CurrencyTypeId + Amount.

For example,
MerchantCode: M1234567
SecretKey: bb841904-4eea-44e5-8ca3-0af1e304ff4f
MerchantTransNum: T1234
PayoutId: 8811967
ToBankId: Malaysia_Maybank
ToBankAccountNum: 123456789
CurrencyTypeId: 1
Amount: 10.00

String to be encrypted: M1234567bb841904-4eea-44e5-8ca3-0af1e304ff4fT12348811967Malaysia_Maybank123456789110.00
CheckString2: f08508b98bca3d118f5c17b3899e76820a84f43f099d8592fef93d235879c56a

Click below links to see the example ENCRYPTION ALGORITHM TO GENERATE SHA256 VALUE.

HTTP GET REDIRECTED BY PAYMENT GATEWAY

The Payment Gateway makes a HTTP Get to Merchant for all status of payout with the following data:

1. MerchantCode
2. TransNum
3. PayoutId
4. ToBankId
5. ToBankAccountNum
6. CurrencyTypeId
7. Amount
8. Remarks
9. CheckString2
10. Result

Below is the example of Http Get on failed payout:

                                                        
                                                            https://www.example.com/Deposit_P2pPayout_Response.aspx?MerchantCode=M1234567&MerchantTransNum=T1234&PayoutId=8811967&ToBankId=Malaysia_Maybank&ToBankAccountNum=123456789&CurrencyTypeId=1&Amount=10.00&Remarks=&CheckString2=f08508b98bca3d118f5c17b3899e76820a84f43f099d8592fef93d235879c56a&Result=35003

Below is the example of Http Get on pending payout:

                                                        
                                                            https://www.example.com/Deposit_P2pPayout_Response.aspx?MerchantCode=M1234567&MerchantTransNum=T1234&PayoutId=8811967&ToBankId=Malaysia_Maybank&ToBankAccountNum=123456789&CurrencyTypeId=1&Amount=10.00&Remarks=&CheckString2=f08508b98bca3d118f5c17b3899e76820a84f43f099d8592fef93d235879c56a&Result=35001

Below is the example of Http Get on success payout:

                                                        
                                                            https://www.example.com/Deposit_P2pPayout_Response.aspx?MerchantCode=M1234567&MerchantTransNum=T1234&PayoutId=8811967&ToBankId=Malaysia_Maybank&ToBankAccountNum=123456789&CurrencyTypeId=1&Amount=10.00&Remarks=&CheckString2=f08508b98bca3d118f5c17b3899e76820a84f43f099d8592fef93d235879c56a&Result=35002

HTTP GET (WITH JSON) SEND BY PAYMENT GATEWAY

The Payment Gateway makes a HTTP Get (with JSON) to Merchant for all status of payout with the following data:

1. PayoutId
2. Result
3. MerchantCode
4. TransNum
5. CurrencyTypeId
6. ToBankId
7. ToBankAccountNum
8. Amount
9. Remarks
10. CheckString2

Below is the example of Http Get (with JSON) on failed payout:

                                                        
                                                            {"PayoutId":"8811967","Result":"35003","MerchantCode":"M1234567","TransNum":"T1234",
                                                            "CurrencyTypeId":1,"ToBankId":"Malaysia_Maybank","ToBankAccountNum":"123456789","Amount":"10.00",
                                                            "Remarks":"","CheckString2":"f08508b98bca3d118f5c17b3899e76820a84f43f099d8592fef93d235879c56a"}

Below is the example of Http Get (with JSON) on pending payout:

                                                        
                                                            {"PayoutId":"8811967","Result":"35001","MerchantCode":"M1234567","TransNum":"T1234",
                                                            "CurrencyTypeId":1,"ToBankId":"Malaysia_Maybank","ToBankAccountNum":"123456789","Amount":"10.00",
                                                            "Remarks":"","CheckString2":"f08508b98bca3d118f5c17b3899e76820a84f43f099d8592fef93d235879c56a"}

Below is the example of Http Get (with JSON) on success payout:

                                                        
                                                            {"PayoutId":"8811967","Result":"35002","MerchantCode":"M1234567","TransNum":"T1234",
                                                            "CurrencyTypeId":1,"ToBankId":"Malaysia_Maybank","ToBankAccountNum":"123456789","Amount":"10.00",
                                                            "Remarks":"","CheckString2":"f08508b98bca3d118f5c17b3899e76820a84f43f099d8592fef93d235879c56a"}

PAYOUT - AUTOMATED (BACK-TO-BACK METHOD)

HOW IT WORKS

Merchant posts payout data to Payment Gateway using HTTP Post. Refer to DATA TO BE POSTED TO PAYMENT GATEWAY below.
Payment Gateway registers, processes and post back to Merchant with JSON. Refer to HTTP Post (with JSON) SEND BY PAYMENT GATEWAY below.
Payment Gateway processes the pending payout and make a HTTP Post (with JSON) to Merchant with result Approved or Rejected. Refer to HTTP POST (WITH JSON) SEND BY PAYMENT GATEWAY

URL TO BE POSTED TO PAYMENT GATEWAY

Demo/Test Site: https://job1-demo.mxpay.asia/WebForm/Deposit_P2pPayout2_B2b.aspx

Live Site: https://job1.mxpay.asia/WebForm/Deposit_P2pPayout2_B2b.aspx

DATA TO BE POSTED TO PAYMENT GATEWAY

Element Name	Type	Max Length	Required	Description
MerchantCode	String	-	Yes	Merchant code that given by Payment Gateway upon application. Case-sensitive.
MerchantTransNum	String	50	Yes	Transaction number that provided from merchant own platform system. Note: Value must be unique.
CurrencyTypeId	Numeric	1	Yes	1 = MYR 8 = VND 1001 = EUSDT 1002 = TUSDT
ToBankId	String	2	Yes	1 = Malaysia - Maybank 2 = Malaysia – CIMB Bank 3 = Malaysia – RHB Bank 4 = Malaysia - Public Bank 5 = Malaysia - Hong Leong Bank 6 = Malaysia - Alliance Bank 7 = Malaysia - Bank Islam 8 = Malaysia - Affin Bank 9 = Malaysia - AmBank 10 = Malaysia – BSN 11 = Malaysia – Touch N Go eWallet 12 = Malaysia – GX Bank 13 = Malaysia – Bank Rakyat 14 = Malaysia – Ryt Bank 15 = Malaysia – United Overseas Bank 16 = Malaysia – OCBC Bank 17 = Malaysia – Bank Muamalat 18 = Malaysia – Standard Chartered Bank 20 = Malaysia – Boost Bank 21 = Malaysia – Boost Ewallet 22 = Malaysia – BigPay 23 = Malaysia – Bank Pertanian (AgroBank) 24 = Malaysia – CitiBank Berhad 25 = Malaysia – Al-Rajhi Bank 26 = Malaysia – HSBC Bank 27 = Malaysia – MUFG Bank 101 = Vietnam - Asia Commercial Bank 102 = Vietnam - BIDV 103 = Vietnam - Military Commercial Bank 104 = Vietnam - Dong A Bank 105 = Vietnam - EXIMBANK 106 = Vietnam - Saigon Hanoi Commercial Joint Stock Bank 107 = Vietnam - HD Bank 108 = Vietnam - Sacombank 109 = Vietnam - AGRIBANK 110 = Vietnam - TECHCOMBANK 111 = Vietnam - VietinBank 112 = Vietnam - Vietcombank Note: For Crypto Currency, please set to “0”.
ToBankAccountName	String	100	Yes	Account Name Note: For Crypto Currency, please leave EMPTY.
ToBankAccountNum	String	50	Yes	Customer bank account number. Note: Customer wallet address (for Crypto Currency), Customer duitnow/mobile phone number (for TNG eWallet).
Amount	Numeric	-	Yes	Payout amount. Note: Note: For example, 100 and 2000.50 but for Currency EUSDT, TUSDT and BTC are allowed up to 6 decimal places such as 20.123456.
BankIdentifierCode	String	50	No	IFSC code for INR only. Note: May skip if not using INR Currency.
Signature	String	-	Yes	Encrypted Signature. See HOW TO BUILD SIGNATURE below.

HOW TO POST DATA BY HTTP POST IN HTML FORM

Example in HTML

Merchant need to use HTML Form to post data to payment gateway.

                                                        
                                                            <form action="https://job1.mxpay.asia/WebForm/Deposit_P2pPayout2_B2b.aspx" method="POST"><br>
                                                                <input name="MerchantCode" value="M1234567"><br>
                                                                <input name="MerchantTransNum" value="T1234"><br>
                                                                <input name="CurrencyTypeId" value="1"><br>
                                                                <input name="ToBankId" value="1"><br>
                                                                <input name="ToBankAccountName" value="PE002"><br>
                                                                <input name="ToBankAccountNum" value="123456789"><br>
                                                                <input name="Amount" value="10.00"><br>
                                                                <input name="BankIdentifierCode" value=""><br>
                                                                <input name="Signature" value="98696ab7dc6e0da2215bc4421b6724c8aa6e3bd33a264542b9393b404457344f"><br>
                                                                <input name="submit" type="submit">
                                                            <form>

HOW TO BUILD SIGNATURE

Signature is an encrypted SHA256 string of concatenation of MerchantCode + SecretKey + MerchantTransNum + ToBankId + ToBankAccountNum + CurrencyTypeId + Amount.

For example,
MerchantCode: M1234567
SecretKey: bb841904-4eea-44e5-8ca3-0af1e304ff4f
MerchantTransNum: T1234
ToBankId: 1
ToBankAccountNum: 123456789
CurrencyTypeId: 1
Amount: 10.00

String to be encrypted: M1234567bb841904-4eea-44e5-8ca3-0af1e304ff4fT12341123456789110.00
Signature: 98696ab7dc6e0da2215bc4421b6724c8aa6e3bd33a264542b9393b404457344f

Click below links to see the example ENCRYPTION ALGORITHM TO GENERATE SHA256 VALUE.

DATA TO BE RETURNED BY PAYMENT GATEWAY

URL Argument Name	Description
PayoutId	Unique payout reference number that returned by Payment Gateway.
Result	35001 = Payout is Pending. 35002 = Payout is Success. 35003 = Payout is Rejected. 35004 = Payout is Processing. 1101 = Merchant Code Not Defined. 1102 = Merchant Code Invalid. 1201 = Merchant Payout No. is not defined. 1202 = Invalid Merchant Payout No. 1203 = More than one Merchant Transaction No. found. 1301 = Currency Code is not defined. 1302 = Invalid Currency Code. 1401 = Amount is not defined. 1402 = Invalid Amount. 1403 = Amount’s Requirement Not Met. 1501 = Bank Name is not defined. 1502 = Invalid Bank Name or exceed length. 1503 = Bank Name not matched – Refer to Appendix Bank. 1601 = Account Name is not defined. 1602 = Invalid Account Name. 1701 = Account Number is not defined. 1702 = Invalid Account Number. 1801 = Signature is not defined. 1802 = Invalid Signature. 1901 = Redirect URL not set. 2001 = System Error. 2101 = Bank Identifier Code is not defined. 2102 = Invalid Bank Identifier Code or exceed length. 2301 = To Bank Id is not defined. 2302 = To Bank Id is invalid. 2401 = To Bank Account Name is not defined. 2402 = To Bank Account Name is invalid. 2501 = To Bank Account No. is not defined. 2502 = To Bank Account No. is invalid. 2601 = System is invalid. 2602 = System is offline. 2701 = Merchant’s Payout Account is inactive. 2801 = Merchant IP Address Invalid (Whitelisting is needed).
MerchantCode	Merchant code that given by Payment Gateway upon application. Case-sensitive.
TransNum	Transaction number that provided from merchant own platform system. Value must be unique.
CurrencyTypeId	Payout currency type id.
ToBankId	Customer bank id selection.
ToBankAccountNum	Customer bank account number.
Amount	Payout amount.
Remarks	Merchant payout remarks.
CheckString2	Unique encryption string that returned by Payment Gateway. See HOW TO BUILD CHECKSTRING2 below.

HOW TO BUILD CHECKSTRING2

CheckString2 is an encrypted SHA256 string of concatenation of concatenation of MerchantCode + SecretKey + MerchantTransNum + PayoutId + ToBankId + ToBankAccountNum + CurrencyTypeId + Amount.

String to be encrypted: M1234567bb841904-4eea-44e5-8ca3-0af1e304ff4fT12348811967Malaysia_Maybank123456789110.00
CheckString2: f08508b98bca3d118f5c17b3899e76820a84f43f099d8592fef93d235879c56a

Click below links to see the example ENCRYPTION ALGORITHM TO GENERATE SHA256 VALUE.

HTTP POST (WITH JSON) SEND BY PAYMENT GATEWAY

The Payment Gateway makes a HTTP Post (with JSON) to Merchant for all status of payout with the following data:

1. PayoutId
2. Result
3. MerchantCode
4. TransNum
5. CurrencyTypeId
6. ToBankId
7. ToBankAccountNum
8. Amount
9. Remarks
10. CheckString2

Below is the example of Http Post (with JSON) on failed payout:

                                                        
                                                            {"PayoutId":"8811967","Result":"35003","MerchantCode":"M1234567","TransNum":"T1234",
                                                            "CurrencyTypeId":1,"ToBankId":"Malaysia_Maybank","ToBankAccountNum":"123456789","Amount":"10.00",
                                                            "Remarks":"","CheckString2":"f08508b98bca3d118f5c17b3899e76820a84f43f099d8592fef93d235879c56a"}

Below is the example of Http Post (with JSON) on pending payout:

                                                        
                                                            {"PayoutId":"8811967","Result":"35001","MerchantCode":"M1234567","TransNum":"T1234",
                                                            "CurrencyTypeId":1,"ToBankId":"Malaysia_Maybank","ToBankAccountNum":"123456789","Amount":"10.00",
                                                            "Remarks":"","CheckString2":"f08508b98bca3d118f5c17b3899e76820a84f43f099d8592fef93d235879c56a"}

Below is the example of Http Post (with JSON) on success payout:

                                                        
                                                            {"PayoutId":"8811967","Result":"35002","MerchantCode":"M1234567","TransNum":"T1234",
                                                            "CurrencyTypeId":1,"ToBankId":"Malaysia_Maybank","ToBankAccountNum":"123456789","Amount":"10.00",
                                                            "Remarks":"","CheckString2":"f08508b98bca3d118f5c17b3899e76820a84f43f099d8592fef93d235879c56a"}

PAYOUT STATUS CHECK - AUTOMATED (BACK-TO-BACK METHOD)

HOW IT WORKS

Merchant posts payout data to Payment Gateway using HTTP Post. Refer to DATA TO BE POSTED TO PAYMENT GATEWAY below.
Payment Gateway return Payout status check result in JSON. Refer to HTTP POST (WITH JSON) SEND BY PAYMENT GATEWAY below.

URL TO BE POSTED TO PAYMENT GATEWAY

Demo/Test Site: https://job1-demo.mxpay.asia/WebForm/Deposit_P2pPayout2_Check_B2b.aspx

Live Site: https://job1.mxpay.asia/WebForm/Deposit_P2pPayout2_Check_B2b.aspx

DATA TO BE POSTED TO PAYMENT GATEWAY

Element Name	Type	Max Length	Required	Description
PayoutId	String	-	Yes	Unique payout reference number that returned by Payment Gateway.
MerchantCode	String	-	Yes	Merchant code that given by Payment Gateway upon application. Case-sensitive.
MerchantTransNum	String	50	Yes	Transaction number that provided from merchant own platform system. Noted: Value must be unique
Signature	String	-	Yes	Encrypted Signature. See HOW TO BUILD SIGNATURE below.

HOW TO POST DATA BY HTTP POST IN HTML FORM

Example in HTML

Merchant need to use HTML Form to post data to payment gateway.

                                                        
                                                            <form action="https://job1.mxpay.asia/WebForm/Deposit_P2pPayout2_Check_B2b.aspx" method="POST"><br>
                                                                <input name="PayoutId" value="8811967"><br>
                                                                <input name="MerchantCode" value="M1234567"><br>
                                                                <input name="MerchantTransNum" value="T1234"><br>
                                                                <input name="Signature" value="1ab99207abc9de6f9ef66b5f9603e951ac99f990249a103987e742a499edf870"><br>
                                                                <input name="submit" type="submit">
                                                            <form>

HOW TO BUILD SIGNATURE

Signature is an encrypted SHA256 string of concatenation of MerchantCode + SecretKey + MerchantTransNum.

For example,
MerchantCode: M1234567
SecretKey: bb841904-4eea-44e5-8ca3-0af1e304ff4f
MerchantTransNum: T1234

String to be encrypted: M1234567bb841904-4eea-44e5-8ca3-0af1e304ff4fT1234
Signature: 1ab99207abc9de6f9ef66b5f9603e951ac99f990249a103987e742a499edf870

Click below links to see the example ENCRYPTION ALGORITHM TO GENERATE SHA256 VALUE.

DATA TO BE RETURNED BY PAYMENT GATEWAY

URL Argument Name	Description
PayoutId	Unique payout reference number that returned by Payment Gateway.
Result	35001 = Payout is Pending. 35002 = Payout is Success. 35003 = Payout is Rejected. 35004 = Payout is Processing. 1101 = Merchant Code Not Defined. 1102 = Merchant Code Invalid. 1201 = Merchant Payout No. is not defined. 1202 = Invalid Merchant Payout No. 1203 = More than one Merchant Transaction No. found. 1301 = Currency Code is not defined. 1302 = Invalid Currency Code. 1401 = Amount is not defined. 1402 = Invalid Amount. 1403 = Amount’s Requirement Not Met. 1501 = Bank Name is not defined. 1502 = Invalid Bank Name or exceed length. 1503 = Bank Name not matched – Refer to Appendix Bank. 1601 = Account Name is not defined. 1602 = Invalid Account Name. 1701 = Account Number is not defined. 1702 = Invalid Account Number. 1801 = Signature is not defined. 1802 = Invalid Signature. 1901 = Redirect URL not set. 2001 = System Error. 2101 = Bank Identifier Code is not defined. 2102 = Invalid Bank Identifier Code or exceed length. 2301 = To Bank Id is not defined. 2302 = To Bank Id is invalid. 2401 = To Bank Account Name is not defined. 2402 = To Bank Account Name is invalid. 2501 = To Bank Account No. is not defined. 2502 = To Bank Account No. is invalid. 2601 = System is invalid. 2602 = System is offline. 2701 = Merchant’s Payout Account is inactive. 2801 = Merchant IP Address Invalid (Whitelisting is needed).
MerchantCode	Merchant code that given by Payment Gateway upon application. Case-sensitive.
TransNum	Transaction number that provided from merchant own platform system. Value must be unique.
CurrencyTypeId	Payout currency type id.
ToBankId	Customer bank id selection.
ToBankAccountNum	Customer bank account number.
Amount	Payout amount.
Remarks	Merchant payout remarks.
CheckString2	Unique encryption string that returned by Payment Gateway. See HOW TO BUILD CHECKSTRING2 below.

HOW TO BUILD CHECKSTRING2

CheckString2 is an encrypted SHA256 string of concatenation of concatenation of MerchantCode + SecretKey + MerchantTransNum + PayoutId + ToBankId + ToBankAccountNum + CurrencyTypeId + Amount.

String to be encrypted: M1234567bb841904-4eea-44e5-8ca3-0af1e304ff4fT12348811967Malaysia_Maybank123456789110.00
CheckString2: f08508b98bca3d118f5c17b3899e76820a84f43f099d8592fef93d235879c56a

Click below links to see the example ENCRYPTION ALGORITHM TO GENERATE SHA256 VALUE.

HTTP POST (WITH JSON) SEND BY PAYMENT GATEWAY

The Payment Gateway makes a HTTP Post (with JSON) to Merchant for all status of payout with the following data:

1. PayoutId
2. Result
3. MerchantCode
4. TransNum
5. CurrencyTypeId
6. ToBankId
7. ToBankAccountNum
8. Amount
9. Remarks
10. CheckString2

Below is the example of Http Post (with JSON) on failed payout status check:

                                                        
                                                            {"PayoutId":"8811967","Result":"35003","MerchantCode":"M1234567","TransNum":"T1234",
                                                            "CurrencyTypeId":1,"ToBankId":"Malaysia_Maybank","ToBankAccountNum":"123456789","Amount":"10.00",
                                                            "Remarks":"","CheckString2":"f08508b98bca3d118f5c17b3899e76820a84f43f099d8592fef93d235879c56a"}

Below is the example of Http Post (with JSON) on pending payout status check:

                                                        
                                                            {"PayoutId":"8811967","Result":"35001","MerchantCode":"M1234567","TransNum":"T1234",
                                                            "CurrencyTypeId":1,"ToBankId":"Malaysia_Maybank","ToBankAccountNum":"123456789","Amount":"10.00",
                                                            "Remarks":"","CheckString2":"f08508b98bca3d118f5c17b3899e76820a84f43f099d8592fef93d235879c56a"}

Below is the example of Http Post (with JSON) on success payout status check:

                                                        
                                                            {"PayoutId":"8811967","Result":"35002","MerchantCode":"M1234567","TransNum":"T1234",
                                                            "CurrencyTypeId":1,"ToBankId":"Malaysia_Maybank","ToBankAccountNum":"123456789","Amount":"10.00",
                                                            "Remarks":"","CheckString2":"f08508b98bca3d118f5c17b3899e76820a84f43f099d8592fef93d235879c56a"}

APPENDIX

APPENDIX CURRENCY

Currency Code	Currency
USD	United States Dollar
MMK	Burmese kyat
EUR	Euro
SGD	Singapore Dollar
CNY	Yuen RMB
THB	Thai Baht
INR	Indian Rupee
VND	Vietnamese Dongs
BND	Brunei Dollar
MYR	Malaysian Ringgit
BDT	Bangladeshi Taka
IDR	Indonesia Rupiah
EUSDT	Ethereum Blockchain
TUSDT	Tron Blockchain
BTC	Bitcoin

APPENDIX BANK

Country	Bank Name
Malaysia	Maybank
Malaysia	CIMB Bank
Malaysia	Public Bank
Malaysia	RHB Bank
Malaysia	Hong Leong Bank
Malaysia	AmBank
Malaysia	UOB Malaysia Bank
Malaysia	Bank Rakyat
Malaysia	OCBC Bank Malaysia
Malaysia	HSBC Bank Malaysia
Malaysia	Affin Bank
Malaysia	Bank Islam Malaysia
Malaysia	Standard Chartered Bank Malaysia
Malaysia	CitiBank Malaysia
Malaysia	Bank Simpanan Nasional
Malaysia	Bank Muamalat Malaysia Berhad
Malaysia	Alliance Bank
Malaysia	Ryt Bank
Malaysia	GX Bank
India	Allahabad Bank
India	Bandhan Bank
India	HDFC Bank
India	IDBI Bank
India	IDFC Bank
India	Indian Bank
India	IndusInd Bank
India	Kotak Mahindra Bank
India	Lakshmi Vilas Bank
India	Ujjivan Small Finance Bank
India	ICICI Bank
India	State Bank of India
India	Union Bank of India
India	Bank of India
India	Canara Bank
India	Axis Bank
India	Punjab National Bank
India	Bank Of Baroda
India	PAYTM Payments Bank LTD
India	India Post Payment Bank
India	Jammu and Kashmir Bank Limited
India	Andhra Bank
India	Federal Bank LTD
India	South Indian Bank
Thailand	Kasikorn Bank
Thailand	Bank of Ayudhya
Thailand	TMB Bank
Thailand	Bangkok Bank
Thailand	Siam Commercial Bank
Thailand	Government Savings Bank
Thailand	Krung Thai Bank
Thailand	Thanachart Bank
Thailand	Bank for Agriculture and Agricultural Cooperatives
Thailand	United Overseas Bank (Thai)
Thailand	Standard Chartered Bank (Thai)
Thailand	CIMB Thai Bank
Thailand	TISCO Bank
Thailand	Kiatnakin Bank
Vietnam	Asia Commercial Bank
Vietnam	DongA Bank
Vietnam	SacomBank
Vietnam	TechcomBank
Vietnam	VietcomBank
Vietnam	BANK for INVESTMENT AND DEVELOPMENT of VIETNAM
Vietnam	EXIMBANK
Vietnam	Vietnam International Commercial Joint Stock Bank
Vietnam	AGRIBANK
Vietnam	Saigon Hanoi Commercial Joint Stock Bank
Vietnam	Ho Chi Minh City Development Joint Stock Commercial Bank
Vietnam	National Citizen Commercial Joint Stock Bank
Vietnam	Vietnam Maritime Commercial Joint Stock Bank
Vietnam	Tien Phong Commercial Joint Stock Bank
Vietnam	Ocean Commercial One Member Limited Liability Bank
Brunei	Baiduri Bank

APPENDIX COUNTRY

Country Code	Country
AFG	AFGHANISTAN
ALB	ALBANIA
DZA	ALGERIA
ASM	AMERICAN SAMOA
AND	ANDORRA
AGO	ANGOLA
AIA	ANGUILLA
ATA	ANTARCTICA
ATG	ANTIGUA AND BARBUDA
ARG	ARGENTINA
EUSDT	Ethereum Blockchain
ARM	ARMENIA
ABW	ARUBA
AUS	AUSTRALIA
AUT	AUSTRIA
AZE	AZERBAIJAN
BHS	BAHAMAS
BHR	BAHRAIN
BGD	BANGLADESH
BRB	BARBADOS
BLR	BELARUS
BEL	BELGIUM
BLZ	BELIZE
BEN	BENIN
BMU	BERMUDA
BOL	BOLIVIA
BIH	BOSNIA AND HERZEGOVINA
BWA	BOTSWANA
BRA	BRAZIL
IOT	BRITISH INDIAN OCEAN TERRITORY
VGB	BRITISH VIRGIN ISLANDS
BRN	BRUNEI DARUSSALAM
BGR	BULGARIA
BFA	BURKINA FASO
BDI	BURUNDI
KHM	CAMBODIA
CMR	CAMEROON
CAN	CANADA
CPV	CAPE VERDE
CYM	CAYMAN ISLANDS
CAF	CENTRAL AFRICAN REPUBLIC
TCD	CHAD
CHL	CHILE
CHN	CHINA
CXR	CHRISTMAS ISLAND
CCK	COCOS ISLANDS
COL	COLOMBIA
COM	COMOROS
COK	COOK ISLANDS
CRI	COSTA RICA
CIV	COTE D'IVOIRE
HRV	CROATIA
CUB	CUBA
CUW	CURACAO
CYP	CYPRUS
CZE	CZECH REPUBLIC
COD	DEMOCRATIC REPUBLIC OF THE CONGO
DNK	DENMARK
DJI	DJIBOUTI
DMA	DOMINICA
DOM	DOMINICAN REPUBLIC
TLS	EAST TIMOR
ECU	ECUADOR
EGY	EGYPT
SLV	EL SALVADOR
GNQ	EQUATORIAL GUINEA
ERI	ERITREA
EST	ESTONIA
ETH	ETHIOPIA
FLK	FALKLAND ISLANDS (MALVINAS)
FRO	FAROE ISLANDS
FJI	FIJI
FIN	FINLAND
FRA	FRANCE
GUF	FRENCH GUIANA
PYF	FRENCH POLYNESIA
GAB	GABON
GMB	GAMBIA
GEO	GEORGIA
DEU	GERMANY
GHA	GHANA
GIB	GIBRALTAR
GRC	GREECE
GRL	GREENLAND
GRD	GRENADA
GLP	GUADELOUPE
GUM	GUAM
GTM	GUATEMALA
GGY	GUERNSEY
GIN	GUINEA
GNB	GUINEA-BISSAU
GUY	GUYANA
HTI	HAITI
VAT	HOLY SEE
HND	HONDURAS
HKG	HONG KONG
HUN	HUNGARY
ISL	ICELAND
IND	INDIA
IDN	INDONESIA
IRN	IRAN
IRQ	IRAQ
IRL	IRELAND
IMN	ISLE OF MAN
ISR	ISRAEL
ITA	ITALY
JAM	JAMAICA
JPN	JAPAN
JEY	JERSEY
JOR	JORDAN
KAZ	KAZAKHSTAN
KEN	KENYA
KIR	KIRIBATI
PRK	KOREA, DEMOCRATIC PEOPLE'S REPUBLIC OF
KOR	KOREA, REPUBLIC OF
XKX	KOSOVO
KWT	KUWAIT
KGZ	KYRGYZSTAN
LAO	LAOS
LVA	LATVIA
LBN	LEBANON
LSO	LESOTHO
LBR	LIBERIA
LBY	LIBYAN ARAB JAMAHIRIYA
LIE	LIECHTENSTEIN
LTU	LITHUANIA
LUX	LUXEMBOURG
MAC	MACAO SPECIAL ADMINISTRATIVE REGION OF CHINA
MKD	MACEDONIA
MDG	MADAGASCAR
MWI	MALAWI
MYS	MALAYSIA
MDV	MALDIVES
MLI	MALI
MLT	MALTA
MHL	MARSHALL ISLANDS
MTQ	MARTINIQUE
MRT	MAURITANIA
MUS	MAURITIUS
MYT	MAYOTTE
MEX	MEXICO
FSM	MICRONESIA
MDA	MOLDOVA
MCO	MONACO
MNG	MONGOLIA
MNE	MONTENEGRO
MSR	MONTSERRAT
MAR	MOROCCO
MOZ	MOZAMBIQUE
MMR	MYANMAR
NAM	NAMIBIA
NRU	NAURU
NPL	NEPAL
NLD	NETHERLANDS
ANT	NETHERLANDS ANTILLES
NCL	NEW CALEDONIA
NZL	NEW ZEALAND
NIC	NICARAGUA
NER	NIGER
NGA	NIGERIA
NIU	NIUE
NFK	NORFOLK ISLAND
MNP	NORTHERN MARIANA ISLANDS
NOR	NORWAY
OMN	OMAN
PAK	PAKISTAN
PLW	PALAU
PAN	PANAMA
PNG	PAPUA NEW GUINEA
PRY	PARAGUAY
PER	PERU
PHL	PHILIPPINES
PCN	PITCAIRN
POL	POLAND
PRT	PORTUGAL
PRI	PUERTO RICO
QAT	QATAR
SRB	REPUBLIC OF SERBIA
COG	REPUBLIC OF THE CONGO
REU	REUNION
ROU	ROMANIA
RUS	RUSSIA FEDERATION
RWA	RWANDA
BLM	SAINT BARTHELEMY
SHN	SAINT HELENA
KNA	SAINT KITTS AND NEVIS
LCA	SAINT LUCIA
MAF	SAINT MARTIN
SPM	SAINT PIERRE AND MIQUELON
VCT	SAINT VINCENT AND THE GRENADINES
WSM	SAMOA
SMR	SAN MARINO
STP	SAO TOME AND PRINCIPE
SAU	SAUDI ARABIA
SEN	SENEGAL
SYC	SEYCHELLES
SLE	SIERRA LEONE
SGP	SINGAPORE
SXM	SINT MAARTEN
SVK	SLOVAKIA
SVN	SLOVENIA
SLB	SOLOMON ISLANDS
SOM	SOMALIA
ZAF	SOUTH AFRICA
SSD	SOUTH SUDAN
ESP	SPAIN
LKA	SRI LANKA
PSE	STATE OF PALESTINE
SDN	SUDAN
SUR	SURINAME
SJM	SVALBARD AND JAN MAYEN
SWZ	SWAZILAND
SWE	SWEDEN
CHE	SWITZERLAND
SYR	SYRIAN ARAB REPUBLIC
TWN	TAIWAN
TJK	TAJIKISTAN
TZA	TANZANIA
THA	THAILAND
TGO	TOGO
TKL	TOKELAU
TON	TONGA
TTO	TRINIDAD AND TOBAGO
TUN	TUNISIA
TUR	TURKEY
TKM	TURKMENISTAN
TCA	TURKS AND CAICOS ISLANDS
TUV	TUVALU
UGA	UGANDA
UKR	UKRAINE
ARE	UNITED ARAB EMIRATES
GBR	UNITED KINGDOM
USA	UNITED STATES OF AMERICA
URY	URUGUAY
UZB	UZBEKISTAN
VUT	VANUATU
VEN	VENEZUELA
VNM	VIETNAM
VIR	VIRGIN ISLANDS, UNITED STATES
WLF	WALLIS AND FUTUNA ISLANDS
ESH	WESTERN SAHARA
YEM	YEMEN
YUG	YUGOSLAVIA
ZMB	ZAMBIA
ZWE	ZIMBABWE

APPENDIX IP ADDRESS

Note: Merchant MUST only accept the HTTP Post (With JSON) from our IP addresses.

103.237.169.108
20.205.226.212
15.235.226.229
139.99.120.220
103.237.169.202
15.235.220.200
139.99.8.238
15.235.226.72
15.235.222.82
15.235.225.85
139.99.123.66
139.99.62.209
15.235.218.126

VERSION LOG

Date and sequence of Documentation version released.

7 July 2024

•

NewDark theme

NewQuick access icons

ImprovementRedesign API docs layout

UpdateTransProvider duitnow consolidation

1 August 2024

•

NewAdded Bangladeshi Taka

FixedLeftside bar navigation not responding

ImprovementRemove unused endpoints

ImprovementDark theme contrast adjustment

UpdateAppendix Currency updated

UpdateTransProvider updated

9 December 2024

•

NewAdded new IP address

UpdateUnused IP address removed

NewAdded new TransProvider THB PromptPay

3 March 2025

•

NewAdded new IP address

UpdateUnused IP address removed

NewAdded new PayPin TransProvider

16 May 2025

•

NewAdded New IP address

2 October 2025

•

improvementReadjust font size

NewAdded new sections for sidebar and home icon

NewManual Payout API

NewManual Payout Status Check API

17 November 2025

•

NewAdded new TransProvider for INR

20 December 2025

•

NewAdded new TransProvider for Crypto

NewAdded new BankId for payout

31 December 2025

•

NewDeposit Crypto API

NewAdded new sections for sidebar and home icon

2 January 2026

•

UpdateRemoved an unused IP address

4 January 2026

•

NewNew payout BankId added

ImprovementShorten tab text length for visual appeal

15 January 2026

•

FixedDeposit - Crypto diagram adjustment

UpdateDeposit - Crypto purpose content

FixedTransProvider remark note

24 January 2026

•

FixedIP address typo

27 January 2026

•

FixedInsert payout manual result code 1901

3 February 2026

•

NewNew ToBankId for payout - automated

8 May 2026

•

UpdatePayout - Manual API removed

You've reached the end of pages.