10.1 Signature Utility Class (SignUtils)
When the platform calls back the merchant, the request headers carryTimestamp, Signature, Sign-Version (V1), and Timezone (UTC+8).
The signature is calculated on the data object (JSON string), excluding the top-level id and action fields.
- Parameters involved in signature:
appId,timestamp, and all fields in data; top-levelidandactionare not involved in signature. buildBodyMapis a public method that can be reused by merchants during signature verification.
10.2 Merchant Sensitive Data Encryption/Decryption Utility (MerchantEncryptUtil)
Use Cases
Algorithm Description
PIN plaintext must be 6 digits and cannot contain three or more identical or consecutive digits, otherwise returns 4016.Physical card activation plaintext CVV must be 3 pure digits; decryption failure returns 4015 / 4019.
