Format for returning message: according parameter to determine: if ‘_type’ it is not specified, then default format is xml, and if it is set as then “json”, the returning message will be in json format. Table 6.1 Requesting parameters for interface Parameter Can be Parameters Type Parameter Description Sample Name empty? sign Result for String Sign=MD5(timestamp + No signature Merchant Key When calculating the signature, please exclude the space and link breaks inside the bodyContent The Merchant Keys are allocated by SOUSHOU centrally _type Format for the String Requirement for the Yes json returning format of the returning message message: Json or is the default format when this parameter is not set. encrypt Encryption String Currently can support Yes 3DES algorithm DES encryption for the message content. The sequence of signing and encrypting algorithm is: signing then encryption. Encrypted messages must be encoded by BASE64. busiCode Merchant code String Merchant code No 01000001 Parameters of requesting message Table 6.2 Requesting parameter for interface Parameter Can be Parameter Type Parameter Description Sample name BUSI_ID Merchant ID String Merchant ID is allocated No 0010000001 centrally by SOUSHOU OPER_ID Operator ID String Operator ID No Operator01 DEV_ID Device String Device number No Cash Register
Format for returning message: according ‘_type’ parameter to determine: if it is not specified, then default format is xml, and if it is set as “json”, then the returning message will be in json format. Table 6.1 Requesting parameters for interface Parameters Parameter Name Type Parameter Description Can be empty? Sample sign Result for signature String Sign=MD5(timestamp + Merchant Key When calculating the signature, please exclude the space and link breaks inside the bodyContent The Merchant Keys are allocated by SOUSHOU centrally No _type Format for the returning message String Requirement for the format of the returning message: Json or is the default format when this parameter is not set. Yes json encrypt Encryption algorithm String Currently can support DES encryption for the message content. The sequence of signing and encrypting algorithm is: signing then encryption. Encrypted messages must be encoded by BASE64. Yes 3DES busiCode Merchant code String Merchant code No 01000001 Parameters of requesting message Table 6.2 Requesting parameter for interface Parameter Parameter name Type Parameter Description Can be Sample BUSI_ID Merchant ID String Merchant ID is allocated centrally by SOUSHOU No 0010000001 OPER_ID Operator ID String Operator ID No Operator01 DEV_ID Device String Device number No Cash Register
Open%20Interface%20Documentation%20of%20SOUSHOU_v2.3.1.docx