Message Structure
Request and response message are both use following structure
No. | Parameter | Format | Reference | Description | Memo |
---|---|---|---|---|---|
1 | action | String | inquiry | Transaction Type | The specific interfaces with detail description |
2 | deviceNo | String | POS01 | Cashier Terminal No. | To identify the Cashier Terminal used in this transaction |
3 | shopNo | String | CN123456 | Shop No. | To identify the merchant / shop in this transaction |
4 | brand | String | 663 | Brand No. | To identify the Brand used in this transaction, allocated by e-Buy |
5 | body | String | BASE64 | Message Detail | The specific interfaces with detail description |
6 | mwVersion | String | 20161010 | Middleware Version | The Middleware is compatible to process with different backend system |
7 | ptlVersion | String | 20161010 | Protocal Version | The protocol is compatible to process with different backend system |
8 | posVersion | String | 20161010 | e-Buy POS Version | The e-Buy POS is compatible to process with different backend system |
9 | timestamp | String | 1483372334 | Unix Format | Unit : second,中间件需要在收到返回时同步该时间 |
10 | sign | String | 7E65B60DCFA42B04 | Signature | See detail : Signature Algorithm |
example
{
"action" : "inquiry",
"deviceNo" : "POS01",
"shopNo" : "CN123456",
"brand" : "663",
"body" : "ewogICAgICAgICAidHJhY2VObyI6ICI5OTAwMDAwOTEwMDAxMDEwMTczMjEyMyIsCiAgICAgICAgICJvcmlnaW5hbFRyYWNlTm8iOiAiOTkwMDAwMDkxMDAwMTAxMDE3MzIxMjQiCiAgICAgfQ==",
"mwVersion" : "20161010",
"ptlVersion" : "20161010",
"posVersion" : "20161010",
"timestamp" : "1483372334",
"sign" : "7E65B60DCFA42B04"
}
No Comments