{"componentChunkName":"component---src-templates-md-template-js","path":"/docs/qr","result":{"data":{"markdownRemark":{"html":"

NETS QR Integration Guide

\n

Version 1.2

\n

Introduction

\n

NETS QR API allows you to collect payment on any smart devices like tablets and mobile phones to through real-time generation of QR codes.

\n

Examples of NETS QR Online adoption:

\n\n

Getting Started

\n

Integration with NETS QR is done through RESTful APIs.

\n

Requirements

\n

To start integrating, you need the following:

\n
    \n
  1. API Key
    \nYou can create an application under \"My Account/Application\"
    2. \n
  2. Secret
    \nThe secret can be viewed within the application once created under \"My Account/Application\"
    3. \n
  3. Institution Identification Code
    \nUse 20000000001 for test and live transactions
    4. \n
  4. \n

    TID (Terminal ID)

    \n
    \n

    Apply for test ID: Download form and submit to eNETSTS@nets.com.sg
    \nApply for production ID: Download form and submit to info@nets.com.sg

    \n
    \n
    5. \n
  5. \n

    MID (Merchant ID)

    \n
    \n

    Apply for test ID: Download form and submit to eNETSTS@nets.com.sg
    \nApply for production ID: Download form and submit to info@nets.com.sg

    \n
    \n
    6. \n
\n

Service Environments (API URL)

\n

NETS provides separate environments for test and live transactions. The gateway URL path is different for each.

\n\n

Sample Transaction Request

\n

Request header

\n
POST /uat/merchantservices/v1/transaction/request HTTP/1.1\nKeyId: 8bc63cde-2647-4a78-ac75-d5f534b56047\nSign: YEtCdIQpamqAA2Mr3jnOFZ2w/x21jmQi85GMSTH5YNc=\nContent-Type: application/json\n
\n

A sample request JSON payload as follows :

\n
{\n\"mti\": \"0200\",\n\"process_code\": \"990000\",\n\"amount\": \"000000000100\",\n\"stan\": \"001002\",\n\"transaction_time\": \"084356\", //In hhmmss\n\"transaction_date\": \"0206\", //In MMDD\n\"entry_mode\": \"000\",\n\"condition_code\": \"85\",\n\"institution_code\": \"20000000001\",\n\"retrieval_ref\": \"206026360706\",\n\"host_tid\": \"39067101\",\n\"host_mid\": \"11139067100\",\n\"getQRCode\": \"Y\",\n\"communication_data\": [{\n\"type\": \"https_proxy\",\n\"category\": \"URL\",\n\"destination\": \"https://netspay.uat.net:8801/secapi/notify/dynamic\",\n\"addon\": {\n\"external_API_keyID\": \"8bc63cde-2647-4a78-ac75-d5f534b56047\"\n}\n}],\n\"npx_data\": {\n\"E103\": \"39067101\",\n\"E201\": \"000000000100\",\n\"E202\": \"SGD\"\n},\n\"invoice_ref\": \"2018020602636070\"\n}\n
\n

Signature Generation

\n

A hashed signature will need to be generated for every request. The hash formula is a 4 operation process.

\n
\n
    \n
  1. signature = json + secretkey Concatenate payload and secret
    2. \n
  2. signature = sha265(signature) SHA-256 Hash
    3. \n
  3. signature = uppercase(signature) Convert to Uppercase
    4. \n
  4. signature = base64encode(signature) Base64 encode
    5. \n
\n
\n

With the given payload and secret below,

\n
{\"mti\": \"0200\",\"process_code\": \"990000\",\"amount\": \"000000000100\",\"stan\": \"001002\",\"transaction_time\": \"084356\", \"transaction_date\": \"0206\",\"entry_mode\": \"000\",\"condition_code\": \"85\",\"institution_code\": \"20000000001\",\"retrieval_ref\": \"206026360706\",\"host_tid\": \"39067101\",\"host_mid\": \"11139067100\",\"getQRCode\": \"Y\",\"communication_data\": [{\"type\": \"https_proxy\",\"category\": \"URL\",\"destination\": \"https://netspay.uat.net:8801/secapi/notify/dynamic\",\"addon\": {\"external_API_keyID\": \"8bc63cde-2647-4a78-ac75-d5f534b56047\"}}],\"npx_data\": {\"E103\": \"39067101\",\"E201\": \"000000000100\",\"E202\": \"SGD\"},\"invoice_ref\": 2018020602636070\"}\n
\n\n

The expected signature should be:

\n
YEtCdIQpamqAA2Mr3jnOFZ2w/x21jmQi85GMSTH5YNc=\n
\n

API Calls

\n

NETS QR Request

\n

The NETS QR API initiates a new QR payment transaction.

\n

\"QR

\n

The transaction flow goes as follows :

\n\n

?> You may query the gateway to confirm the transaction in addition to awaiting the NETS gateway response as well with the following /merchantservices/v1/transaction/query

\n

NETS QR Query

\n

The NETS QR query API allows you to check the status of the QR transaction and see if it's completed or failed in the event that the NETS gateway does not return any data. The details of the API can be found in the reference

\n

NETS QR Reversal

\n

In certain cases when the server cannot connect to the smart device, a transaction reversal may be initiated. This process is as shown below:

\n

\"Payment

\n

This is a 4 stage process:

\n
    \n
  1. (Step 1-5) As per normal payment sequence, i.e. transaction is approved.
    2. \n
  2. (Step 6) The QR/VT server sends a reversal to NETS host.
    3. \n
  3. (Step 7) NETS host send the reversal request to the issuing host.
    4. \n
  4. (Step 8) NETS host informs mobile server of the event.
    5. \n
","frontmatter":{"date":"December 17, 2018","path":"/docs/qr","title":"NETS QR","type":"api-guide","section":"qr"}}},"pageContext":{}},"staticQueryHashes":["3649515864"]}