top of page
banner bkgd.png


Merchant Quick Start Guide

version 1.0 | publishing date: 15/02/2017 

1. Introduction

Octo3’s e-Commerce Payment Service provides an efficient, secure and easy-to-use payment integration solution to enable merchant systems with online payment capabilities. The document aims at providing merchants necessary information to jump-start the integration process, by interacting with the platform using the pre-defined codes and account information.

To understand extensively how the platform functions, please refer to the following documents.

  • e-Commerce Payment API Specification Document  

  • Asynchronous Notification Merchant Implementation Guide

  • Merchant Portal Guide

2. Submit Your First Transaction / Digital Order (DO)

The e-Commerce Payment Service API is a simple-to-use and secure payment service interface which allows the merchant to integrate real-time payment capability into its system. To immediately submit your first transaction (SALE_ONLY transaction), you can make use of a HTML form and submit a HTTPS POST request. You can quickly create one by copying the following code to a new text document:

2. Submit

Assign a unique ID to the transaction by replacing “this_is_the_1st_transaction” with a string in the merch_order_id field.

Revise the parameter values based on the MID account document if necessary. Click “Process payment” to proceed.

3. Complete the transaction

Upon submitting the correct parameters to the platform, you will be redirected to the payment page hosted by the service channel.

If you are using a different MID for making a transaction, please refer to the respective payment flow document and input the payment information as provided in the MID Account Document.

3. complete
PAyment Page.png

Select “China Merchant Bank” (招商银行) under the Debit Card (储蓄卡) tab. Click “Proceed Payment” (确认付款) to next step.

China PAyment Page.png

Accept the parameters to click “confirm payment” (確認支付) to confirm.

4. Receive the Response / Digital Receipt (DR)

Upon a successful transaction, you will be redirected to the address provided in the “redirect_url” field and receive a XML response. Below is the sample response of an accepted transactions.

4. Receive
Invalid Request

If the parameters are not correctly inputted, you may run into an “invalid request” page. To quickly identify the cause of an invalid request, you can add the following string to the “redirect_url” field while submitting the request.


Below is the sample error of an invalid request:

redirect URL.png

You can identify the cause of failure by looking at the txn_message and the txn_response_code. For complete list and the meaning of the response codes, please refer to the e-Commerce Payment API Specification Document.

5. Query your transaction on the merchant portal

You can log in the merchant portal and search for the transaction just made. Log in with the following information,


Merchant Code: uat_mc

Username: admin

Password: 89YCMQ43

Select the MID in the pull down menu:

5. Query

Go to "Search Transaction"

Search TXN.png
Click on the search button​
  • Typing in the merch_order_id value in the Merchant Transaction ID field

  • Selecting “all” as txn type

  • Refining the day range to the date when transaction is complete.

Search TXN 1.png
6. Stay updated with the transaction status​


The platform offers 2 ways for merchant systems to keep updated with the transaction status, namely the API function “query_txn” and the asynchronous notification.

6. Stay
API function “query_txn”

The API function “query_txn” provide HTTPS pull data service for merchants to request the latest transaction status. You can quickly query a transaction status by using the following html code.

Upon successful request, you will receive a transaction response in XML format. Below is the sample response of an accepted transaction:

Asynchronous notification

The asynchronous notification provides server push update to merchants’ services when a transaction status changes.  For detailed implementation guideline, please refer to Asynchronous Notification – Merchant Implementation Guide.

bottom of page