Web photo verify API
Performs a liveness detection on the uploaded samples to verify whether they are recorded from a live person. And then perform a one-to-one comparison with the ID photo submitted in order to verify whether the live images and ID photo belong to the same person.
PhotoVerify is a BWS service, which uses one passport image from an ID document, and compares that to two "live" images of a person, to find out whether the persons shown are the same. Periocular biometrics is used as it gives better results than face (and allows for close-view recordings). No classes are created, no templates or patterns are stored. It fulfills all requirements for an anonymous ID proofing service.
To perform a photo verification, three images have to be provided:
- two live recorded images, which are sent to the quality-check where, among other things, the face detection is done. If the images are suitable, a live-detection is executed. Only if live-detection succeeds, the procedure is continued.
- a photo, typically a passport image from an ID document. If the photo also contains a face, it is compared to the live images.
A decision about the similarity of the photo and the live images is made according to an accuracy level. The higher the accuracy level, the better the faces on the images must match. Higher accuracy levels are recommended, but lower accuracy levels can be used with low quality ID photos (e.g. scanned passport images), where a higher accuracy cannot be reached any more.
Five accuracy settings are defined from 1 to 5 with accuracy lower or equal to 1 being the worst (with a false acceptance rate of about 30%), and greater or equal to 5 being the best (with a false acceptance rate of about 0.1%). The default is 4, with a false acceptance rate of 2.5%.
This API call requires Basic Authentication, i. e. you have to provide an HTTP authorization header using the authorization method Basic and the base64 encoded string
App-ID:App-Secret (therefore the transport is secured using TLS/SSL). To receive the necessary BWS WebAPI access data (
App-Secret) you have to register your application on the BWS Management Portal first. This requires a valid BWS subscription.
optional integer containing the desired accuracy level:
or using the application/x-www-form-urlencoded media type:
If all three provided images could be processed successfully, this method returns the OK HTTP status code (200) with simply
false in the body content, indicating whether the live images match the ID photo or not with regard to the applied accuracy level.
In case something goes wrong, an error HTTP status code is returned together with some additional information if available.
Response HTTP Status Codes
The call returns one of the standard HTTP status codes:
|200 OK||The response body simply says true or false, indicating whether the live images match the ID photo or not.|
|400 Bad Request||Invalid samples have been uploaded or they could not be processed successfully, e.g. no face found or live detection failed, etc. The response body typically has a |
|401 Unauthorized||Basic Authentication is required.|
|500 Internal Server Error||A server side exception occurred. The content may contain a |