Have questions?
We got answers
Mistakes to avoid while selecting/orchestrating KYC methods
- If someone is using Aadhaar XML (even though we don’t recommend using it), it is necessary to do some health check to ensure whether the UIDAI website is live or down
- In the KYC Record upload workflow, make sure to extract & validate KYC details, not just ‘search & download’. If only search & download is done, bad/empty records can be downloaded.
- Not all Aadhaar numbers are linked with mobile numbers, so before taking a user through a journey, it would be helpful to check whether their mobile number is linked to their Aadhaar.
(Digilocker has an API call that can check whether the mobile number and Aadhaar number are linked only using the mobile number as input)
What are the 80-20s to get right when implementing aKYC process/ solution?
- Try to use a workflow orchestrator instead of building everything yourself
- Use passive liveness as a best practice. It has a high conversion rate, requires very little instructions and works well on all devices and bandwidth conditions
