Performs a one-to-one comparison of the given samples with the stored biometric templates in order to verify the individual is the person he or she claims to be.
[OperationContract]
[FaultContract(typeof(BioIDWebServiceFault)]
bool Verify(BiometricClassID classId, Sample[] samples, ClassificationFlags flags, out string messages);
Returns true when the given classId could have been verified successfully with the given samples;
false otherwise, or when errors occurred (see messages for details).
A biometric verification tests the given samples against already stored samples (biometric templates) of the given classId.
When this test shows that the new samples belong to the class, true is returned, false otherwise.
This method supports liveness detection (currently supported traits are face and periocular). To activate liveness detection, simply use the flag ClassificationFlags.LiveFaceDetection or ClassificationFlags.LivePeriocularDetection with the flags parameter. Note that in this case the verification will only succeed, when it can undoubtedly determine that the given data is live data. In case that the liveness detection succeeds, the degree of the head rotation between two subsequent images is reported with the returned messages XML-string.
Additionally, verification supports the ClassificationFlags.AutoEnrollment flag that allows an automatic adaption of the template of a user by sending (asynchrounously) the submitted samples to the enroll operation in case that the verification succeeds.
Internally this operation performs a QualityCheck (in BioID ExtractTokenData mode) for all submitted samples before they are forwarded to the liveness detection - in case a live-detection flag is set - and finally the verification is performed. Therefore you might get results from these operations as well together with the verification results.
This API has a fault contract of type BioIDWebServiceFault which is used for fatal errors like invalid arguments or missing service, etc. Messages, even error messages, generated by the verification procedure are reported via the messages output value, which contains an XML string according to the BWSMessages schema namespace.
The messages output XML string might contain operation specific errors as follows:
The messages output XML string might also contain errors for the individual samples. Many of the errors can result from the initial quality-check that is performed before anything else is done. Please refer to the QualityCheck method for a list of sample errors that might have been generated by the quality-check.
Additionally the following errors can occur. With any of theses errors the sample is marked as unsuitable and is not considered in the verification process: