Skip to main content

Message Structure

Request and response message are both use following structure

No.ParameterFormatReferenceDescriptionMemo
1actionStringinquiryTransaction TypeThe specific interfaces with detail description
2deviceNoStringPOS01Cashier Terminal No.To identify the Cashier Terminal used in this transaction
3shopNoStringCN123456Shop No.To identify the merchant / shop in this transaction
4brandString663Brand No.To identify the Brand used in this transaction, allocated by e-Buy
5bodyStringBASE64Message DetailThe specific interfaces with detail description
6mwVersionString20161010Middleware VersionThe Middleware is compatible to process with different backend system
7ptlVersionString20161010Protocal VersionThe protocol is compatible to process with different backend system
8posVersionString20161010e-Buy POS VersionThe e-Buy POS is compatible to process with different backend system
9timestampString1483372334Unix FormatUnit : second,中间件需要在收到返回时同步该时间
10signString7E65B60DCFA42B04SignatureSee detail : Signature Algorithm

example

 {
     "action" : "inquiry",
     "deviceNo" : "POS01",
     "shopNo" : "CN123456",
     "brand" : "663",
     "body" : "ewogICAgICAgICAidHJhY2VObyI6ICI5OTAwMDAwOTEwMDAxMDEwMTczMjEyMyIsCiAgICAgICAgICJvcmlnaW5hbFRyYWNlTm8iOiAiOTkwMDAwMDkxMDAwMTAxMDE3MzIxMjQiCiAgICAgfQ==",
     "mwVersion" : "20161010",
     "ptlVersion" : "20161010",
     "posVersion" : "20161010",
     "timestamp" : "1483372334",
     "sign" : "7E65B60DCFA42B04"
 }