Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.go.gbgplc.com/llms.txt

Use this file to discover all available pages before exploring further.

The Facematch Verification module determines whether two face images belong to the same person. It compares a selfie captured during the onboarding journey against a reference face image. The reference is typically the portrait extracted from the subject’s identity document or read from the document’s Near Field Communication (NFC) chip. Liveness verification confirms that a real person is present. Facematch verification confirms that the person present is the same person shown on the document. This page contains documentation for the Facematch Verification module, including its capabilities and the scoring thresholds it uses.

Facematch Verification

The Facematch Verification module uses a comparison engine that returns a granular similarity score rather than a binary match result. This gives you more control over how strictly you enforce the match, since you can configure the acceptance threshold to suit your risk tolerance. The module compares the selfie image against the anchor image and produces a score from 0 to 100, where a higher score indicates greater similarity between the two faces. Default outcomes are configured around two thresholds (80 for success, 70 for review), but these can be adjusted in the Journey builder.

Capabilities

The module returns a single capability: a facematch score.

Facematch score

This capability returns an integer similarity score indicating how closely the selfie matches the reference face image.
DetailDescription
TypeInteger
Range0–100
Default0
A higher score indicates greater similarity between the two faces. The score reflects the algorithm’s confidence that the selfie and the document portrait belong to the same person, based on analysis of facial geometry, feature positioning, and biometric markers. Factors that can reduce the score without indicating fraud include:
  • Significant time elapsed between the document photo and the selfie (ageing).
  • Changes in appearance such as facial hair, glasses, hairstyle, poor lighting.
  • Camera quality during selfie capture, low resolution or damage to the document photograph.
  • Differences in head angle or facial expression between the two images.
A score of 0 indicates that the comparison couldn’t produce a result. This occurs if no face was detected in the selfie, if the anchor image was missing or unreadable, or if an error prevented the comparison. Evaluation rules should treat a score of 0 as an inconclusive result rather than a confirmed mismatch.

Default outcomes

The module uses score thresholds to classify the facematch result into one of three outcomes.
OutcomeConditionDescription
SuccessScore ≥ 80The system has high confidence that the selfie and the document portrait belong to the same person. The subject is confirmed as the document holder.
ReviewScore ≥ 70 and < 80The system’s confidence is moderate. The faces might belong to the same person, but the similarity score is not high enough for automatic acceptance. Common causes include poor lighting, a significant age gap between the document photo and the selfie, or partial face occlusion. This outcome typically routes to manual review, where a human operator visually compares the two images.
FailScore < 70The system has low confidence that the faces belong to the same person. The selfie and the document portrait are likely of different individuals. This outcome typically routes to rejection or escalation.
ERRORDefault (no conditions matched)The facematch check could not be completed due to a system-level issue.
The default score thresholds (80 for success, 70 for review) are starting points. Adjust them in the evaluation configuration to match your risk tolerance. Lowering the success threshold increases acceptance rates but allows weaker matches through. Raising it improves security but might route more genuine users to manual review, particularly for documents with older photographs.

Input payload

The following is a sample payload used to submit biometric images to the Facematch Verification module for processing.
JSON
{
  "resourceId": "<resourceId>",
  "context": {
    "subject": {
      "biometrics": [
        {
          "face1Image": "<base64-encoded string>",
          "face2Image": "<base64-encoded string>"
        }
      ]
    }
  }
}
The following table describes each field in the payload.
FieldRequiredDescription
face1ImageYesBase64-encoded selfie image captured from the end user.
face2ImageYesBase64-encoded anchor image used for comparison. Sourced from a document processed earlier in the journey or from an existing trusted reference image.
biometricsYesAccepts at least one item.

Sample response

The following is a sample response for a successful facematch from the Facematch Verification module.
JSON
{
  "response": {
    "advice": {
      "score": 82
    },
    "outcome": "Success"
  }
}