Revocation signature is different from other interfaces. ‘sign’ sign=MD5(timestamp+ Merchant Key+ incoming parameter):timestamp Incoming chargeCode={chargeCode}&busiCode={busiCode} Do revocation while parameter opType is equals do ‘ACO’,and revocation real-time while parameter opType is null or not equals ‘ACO’ Format for returning to to determine the ‘_type’ format, default is XML if no is set, and if it is set as then the ‘_type’ “json”, message format is json. Parameters of the returning message Table 11.2 The returning parameter for revoking interface Parameter Parameter Type Parameter description Sample name RESULT Response Object The sub-node including: 1 code code, please refer to appendix 5 for detailed info. message Sample returning message JSON format { "CANCELTRADE_RESP": { "RESULT": { "CODE": "SUCCESS", "INFO": "Revocation is successful" } } }
Revocation signature ‘sign’ is different from other interfaces. sign=MD5(timestamp+ Merchant Key+ incoming parameter):timestamp Incoming chargeCode={chargeCode}&busiCode={busiCode} Do revocation while parameter opType is equals ‘ACO’,and do revocation real-time while parameter opType is null or not equals ‘ACO’ Format for returning to ‘_type’ to determine the format, default is XML if no ‘_type’ is set, and if it is set as “json”, then the message format is json. Parameters of the returning message Table 11.2 The returning parameter for revoking interface Parameter Parameter name Type Parameter description Sample RESULT Response code Object The sub-node including: code, please refer to appendix 5 for detailed info. message 1 Sample returning message JSON format { "CANCELTRADE_RESP": { "RESULT": { "CODE": "SUCCESS", "INFO": "Revocation is successful" } } }
Open%20Interface%20Documentation%20of%20SOUSHOU_v2.3.1.docx