The KYC functionality is now working. To verify someone, a website creates a challenge, something like "
www.utopia.org/?kyc-request=1462517"
The user then scans his passport and generates a base64 encoded identity proof for this challenge. As said previously there a re 3 modes: anonymous, with written information and with facial image.
When the base64 encoded proof is sent to the /ubi/verify-kyc endpoint, the output would be like this one:
{
"success": "true",
"dscID": "81fd9c80a1c40f2fbde419ee928318013fe714ff",
"currencyID": "42",
"expiration": "1568278666",
"passportHash": "35715d1ae2c2b67e17815c3d53b12406833a0b294cc9bc40a37473111d32deb9",
"challenge": "www.utopia.org/?kyc-request=1462517",
"passportNumber": "A54DF5AA4",
"name": "DOE JOHN",
"isoCountryCode": "UTO",
"gender": "M",
"dateOfExpiry": "210519",
"dateOfBirth": "890529",
"mrz": "PUTODOE< "facialImage": "AAAAgdf0...."
}
in the above example the KYC proof is with a facial image.
An "anonymous" proof would look like this:
{
"success": "true",
"dscID": "81fd9c80a1c40f2fbde419ee928318013fe714ff",
"currencyID": "42",
"expiration": "1568278666",
"passportHash": "35715d1ae2c2b67e17815c3d53b12406833a0b294cc9bc40a37473111d32deb9",
"challenge": "www.utopia.org/?kyc-request=1462517"
}
