---

KYC Documents :

In KYC Document Profile the request is send over HTTPS to the /applicationServices/api/ApplicationManager/uploadKycDocuments resource using POST method. The request must contain all the document field list on which we have to upload KYC documents.

In our API Specifications you can find a full list of parameters that can be sent in the request. Also the number of parameters varies depending on the acquiring bank selected. This can be seen in the sample request given below.

---

Sample Request

---

Sample Response

---

Hashing Rule

supports MD5 Cryptographic Hash for the authenticity of payment request send to the server.

KYC document upload API requires below details for authentication and authorization to be passed along with request.

• memberId <Merchant ID as shared by >
• random Id <Any random generated ID>
• partner's secureKey <Partner key shared by >

How to generate Checksum ?

Checksum has to be calculated with following combination and need to be send along with the authentication parameters in each server-to-server request:
<memberId>|<secureKey>|<random>

---

Sample Code

---