- Should numbers be translated in vernacular KFS?
No, you don’t need to translate the numbers and you can keep using English and Roman numerics.
This is because people of India are more comfortable with English and Roman numerals now, thanks to mobile phones, frequent OTPs and social media.
In fact, a recent report by Google India actively recommends using English numerals instead of Indian numerals. It found that most users are familiar with English numerals.
You can read the report here
- Can we send the KFS eSign invite message in a vernacular language via Leegality?
Yes. You can send document execution messages (eSign link, signed document) in the following languages -
Via SMS - English, Hindi, Marathi, Gujarati, Tamil, Telugu, Kannada, Malayalam
Via WhatsApp - English
Via Email - Can provide* in 11 languages (English, Bengali, Kannada, Odia, Hindi, Punjabi, Malayalam, Gujarati, Tamil, Telugu, Marathi)
*Not tested. Subject to requirements.
- Can I hyperlink the KFS in the summary screen and collect ‘I agree’ consent stating they’ve read and agreed to the terms of the KFS?
We would not recommend this flow because:
A. Customers can claim they never saw the KFS, so they were not aware of the terms of the KFS before signing the loan agreement
B. You can’t prove the identity of the person who clicked the ‘I Agree’ button - so you can never prove the borrower’s identity.
The KFS should be displayed prominently - and the customer should have the ability to download it and acknowledge it later if they so wish.
.svg)
