Last updated
Last updated
Create a Endpoint
Get your user's Selfie & ID Card images
Submit the Job to Smile ID
Authenticate the user
Interpret your results
The SmartSelfie™ Authentication entails comparing a SmartSelfie™ against the Selfie on file of a registered user. To register a user, the job request payload is exactly the same as a SmartSelfie™ Authentication except for two differences (both changes are to be made in the section of this page):
Since you are authenticating the user, you need an existing user_id
(details of Key in of a user previously successfully enrolled on the Smile ID system)
Set the job_type
to "2" (details of Key in section of this page)
To successfully run Enhanced KYC + SmartSelfie™ jobs you need to submit the user's selfie.Please see SmartSelfie capture as , it is important to recognise that the tag supplied and or returned from this is what will need to be used to submit the Job
jobType
should be set to 2 and is required
callBackUrl (Optional)
can be null but if not it should be a url which the job data will be posted to depending on the status the job is in
partnerParams (Optional)
This is the object create in the step above related to partner params
idInfo (Required)
This is the object create in the step above related to user id information
geoInfo
(Optional) This is any information that may be necessary to associate the job with any geolocation
jobStatusPollingTimeoutMillis => (optional) pass 0 if not needed. This will be the time to wait for job status polling , note if set to a smaller number this will return a complete false result from job status and results will be delivered to the callback
isProduction (required)
should be set to true if you intent to run in production and false if you intend to run in sandbox, it is important to note you cannot run real ID Numbers check on sandbox, for test data please see
The result hashmap will be an object which will contain results returned from the api this contains strongly typed method to get the response as individual items or as json object or as a string, for more information on how to interpret results you can read more about result codes and responses in the section of the docs.