Quick Start
Environment
tip
Lianlian thai payment provides two environments, one is a sandbox, and the other is online formal environment. The sandbox is provided for merchants to debug and test, formal environment will be qualified after complete debugging in sandbox env.
Payment Gateway
- production: https://api.lianlianpay.co.th/gateway
- sandbox: https://sandbox-th.lianlianpay-inc.com/gateway
Merchant Portal
- production: https://merchant.lianlianpay.co.th/user/login
- sandbox: https://sandbox-th-merchant.lianlianpay-inc.com/user/login
Specification
tip
All messages between lianlian and merchant are communicated through POST/GET of HTTP protocol. The Content-Type of POST request is application/json, and encoding is UTF-8.
Request Header
| Field | Type | Length | Required | Description |
|---|---|---|---|---|
| sign_type | string | 3 | true | digital signature type, fixed value: RSA |
| sign | string | 128 | true | digital signature |
| Content-Type | string | 32 | true | fixed value: application/json |
General Response Body
| Field | Type | Length | Required | Description |
|---|---|---|---|---|
| code | int | 6 | true | 6 digits, see Response Code |
| message | string | 128 | true | response message |
| data | - | - | false | data structure, no value if code is not 200000 |
| trace_id | string | 16 | true | trace id, just like '2451cac2ef079401' |
Security
tip
The interface signature generation algorithm is SHA1withRSA
info
👉 Intructions
- The above figure shows the principle of signing and checking. The described scenario is the process of the merchant server initiating repeated open interface requests
- According to the api signature assembly rules and parameter signature assembly rules, the parameters are signed with the merchant's private key to generate a digital signature
- The merchant saves the private key itself, and the public key is saved to Lianlian through the merchant station (merchant public key maintenance) function
- Lianlian open interface access, the signature and parameters need to be transmitted at the same time, Lianlian received the request will use the merchant saved to Lianlian public key and received plaintext parameters for signature verification
- After the verification is passed, the business logic will be executed, and the result will be returned after the execution of the business logic. The result consists of two parts, one is the business result, and the other is the signature parameter in the return head
- The signature parameter returned to head is constructed from the service return result and signed using the private key of the company
- After the merchant receives the open return result, it uses the plaintext return parameters and the link public key (obtained by the link public key of the merchant station) to compare and check the returned signature