How KRA Microservice Works

KRA Microservice can be used to send/submit customers’ complete KYC data to the KRA of their choice among CVL, CAMS, and KARVY. KRA Microservices can be easily integrated by Clients as an API utility.

The customer journey workflow can be defined and designed by Clients to onboard them. The complete data set required for KYC verification is to be collected by clients and then pushed to respective KRA using KRA microservice API.

We also provide the functionality of a multi-KRA system where clients can set up multiple KRAs(max 3) based on priority(First, Second, and Third).

The functionality works as follows, whenever there is a request to push a record to KRA it will first attempt to push the record on primary KRA as per the configuration, if it fails to push to primary KRA then it will attempt to push the record on the secondary KRA. When the record fails to push on the secondary KRA then it will attempt to push it on to the third KRA. In case the application is successfully inserted into any one of the KRA, then the process ends.

To use KRA microservices the entity(client) must register with at least any one of the KRA among CVL, CAMS or KARVY and get the UAT and production credentials from KRA.

Protocol: https://

Pre-Production Hostname: https://backops-investor-onboarding-preproduction.signzy.tech/kra-handler/

Production Hostname:  https://backops-investor-onboarding.signzy.tech/kra-handler/

In the APIs, you have a username and password to the APIs. You need to have an access token for making any further API calls, which you can receive by logging in manually or programmatically using these credentials.

Each call to the APIs should include an 'Authorization' header or 'access_token' query parameter for authentication.

Step 1: Customer Login (Client Login)

Step 2: Register KRA Creds

Step 3: Push Onboarding to KRA

Step 4: Get Push Onboarding Response