Encrytion Process

For data security , Geoswift's interface adopts two encryption methods ,two signature methodsand one sorting method: CFCA public key certificate encryption, AES encryption, SHA1 signature, CFCA private key certificate signature and key name initial alphabet sorting. The demos in threelanguages offer a variety of methods.

1.Sort by key name initial

The main purpose is to sort the data JSON from a to z by initial of key name,then joint the keyvalue(except for the null value), the corresponding key values should be separated by #. Sample：

Before sorting:

PS:’#’ is needed at the end of the string,not the beginning. After sorting：

SHA1 signature：

Used for preliminary summary of data. Sample：

Before signature：

After signature：

3.CFCA CFCA private key signature：

PS: The result of this step is hmac. The signed value should be passed to the hmac item in the original JSON.

The merchant signs the SHA1 result with the exported CFCA private key certificate.The advantage of this signature is that it cannot be cracked.After requesting the interface, Geoswift uses the public key uploaded by the merchant in the Geoswift merchant background for signature verification to prevent information tampering. Example：

After encryption:

After encryption：

4.Automatically generate 16 digits AES key

After this step, get the AES key that used to encrypt the original JSON data which containsthe hmac parameter

The merchant generates a string of the random number with 16 digits length for AES encryption
Sample：wsF0iQI3myswBmH8

5.AES encryption：

The encryption can be decrypted with the same key.The merchant encrypts the original JSONdata which contains the hmac parameter with the self generated 16-bit random number key.Geoswift would decrypt with the same key when received the data.

Sample：

Before encryption：

After encryption：

6.CFCA public key encryption:

After this step, you will get the request header encryptKey data of the request interface. Put the encrypted value into the request header of the request interface, and the key nameisencryptKey.

This encryption is asymmetric encryption. Merchant could conduct the CFCApublic keycertificate encryption through the public key in the demo provided by Geoswift(not the public keyexported). The encrypted data is the AES key generated by merchant, to prevent the leaking of AESkey.

Before encryption：

wsF0iQI3myswBmH8

After encryption：

O3ch2CMfQaVeP8b6WbziCffGVGHF2BSsjaOQm2EvO+3Q1X8y2CSobquLNcT/g/FdsvRnmPwfscR3lbFBYvH9M9NdGjKjLNHkGc2ekagABPGWDwMzcnrLj vkNL3xgHSt4+mmZDDs8OUlpN5WCDVnMBcq2NEb4IY0We7I4g80xIFj1+XwPhzFZL6MMny5fq1/GVbAfh/iNV1XxpOvGsi0v8bRxEwu/auqTM5K6p7VrS ZgcE7rdwD1I11PgN1sHUaPQn1X/2oJ2qELWdNi9K7aAC/7SfZhGXzU5+Z22ShxYzN27l1MIIVKBCbR7/tOMZe2VfQn8YFQgT05TB5dntaJeGw==

7.Request the interface:

When requesting, the merchant needs to confirm that the request address is correct andtherelevant encryption process is accurate. The request method is POST. When requesting, pleaseconfirm that it is encoded by UTF-8. The following is the relevant request content.

Headers: