Verification Check Results
HYPR Affirm shows the result of each identity verification check in the Activity Log, the Helpdesk and the scorecards. This page explains each result: what it checks, what its values mean and where it appears.
The results come from the Document and Biometric Verification step. Which of them appear depends on the checks and settings that step has turned on.
How Results Are Shown
Pass and Fail Labels
Each check either passes or flags something that needs attention. Each surface shows this with its own labels.
| Surface | A passing check shows as | A flagged check shows as |
|---|---|---|
| Activity Log and Helpdesk | Verified | Unverified |
| Approver scorecard and requester report | The pass value in the result's row, such as Yes or Valid, with a check mark | The fail value in the result's row, such as No or Expired, with a cross |
Some labels describe a problem rather than a pass. For Document Tampering, for example, a passing check shows as No on the scorecard, because no tampering was found.
When a check result isn't available:
- The Activity Log shows the result as Unverified. A missing Document Template Match, Document Status or band is left out instead
- The scorecard shows a warning icon in place of the check mark or cross. Document Template Match, Document Status and Security Feature Present are left out instead
If a check is still under manual review when Affirm stops waiting, the Activity Log and the scorecard show Awaiting manual review in place of the results. See Checks Held for Manual Review.
Bands
Spoofing Detection and Face Match Confidence show a Low, Medium or High band instead of a pass or fail value.
| Result | Low | Medium | High | Fails with the default rules |
|---|---|---|---|---|
| Spoofing Detection | Unlikely to be a spoof | Some signs of spoofing | Likely a spoof | High |
| Face Match Confidence | A weak match | A partial match | A close match | Low |
The bands run in opposite directions: a High band is the failing band for Spoofing Detection and the best band for Face Match Confidence.
Overall Result and the Individual Checks
Overall Result is a single result for the whole verification. With the default rules, the IDV Outcome decision comes from the individual results, not from Overall Result. The exception: when Overall Result is passing, a missing Document Template Match, Document Status or Security Feature Present result doesn't fail the step.
A Policy Evaluation Kit can change these rules. See Reading the IDV Outcome action.
Where Results Appear
Each table on this page names the surfaces that show a result, and the label each surface uses.
- Activity Log: The detail view of a verification groups the results by report, such as Document Report or Motion Report. The Helpdesk shows the same labels. See Activity Log
- Approver scorecard: The Document and biometric verification section that an approver reviews. The labels on this page are the defaults, which you can change in Affirm Studio. See Approver Experience
- Requester report: The same section, shown to the requester when Report Visibility for Requester is on. Watchlist and Identity Enhanced results appear to approvers only
- Risk signals: The fields that Risk Policy Builder rules read, under a shorter name. Every evaluation stores them in the verification's policy ledger
- Affirm API: The activity log records that the IDV Results API returns carry these results, including Overall Result
In the tables, Scorecards means both the approver scorecard and the requester report.
Audit Trail events record when the step starts and finishes, and when a check is held for manual review. They don't carry individual check results. See Identity Verification Events.
With Dual Document Verification, each document has its own set of results. The Activity Log labels them Document #1 and Document #2, and risk signals carry a Document 1 or Document 2 prefix.
Document Checks
The Activity Log lists these results under Document Report. They appear whenever the step authenticates a document, and the requester report shows them too. The first Document type row on the scorecard names the document the requester submitted; it isn't a check. Supported document types are listed in Supported Documents by Location.
| Result | What it checks | Values and meaning | Where it appears |
|---|---|---|---|
| First Name Match | Compares the first name read from the document with the first name on the requester's record | Yes: the names match No: the names differ | Activity Log Scorecards: First name match Risk signal: First Name Match |
| Last Name Match | Compares the last name read from the document with the last name on the requester's record | Yes: the names match No: the names differ | Activity Log Scorecards: Last name match Risk signal: Last Name Match |
| Document Template Match | Checks that the document looks and reads like a genuine document of its type and issuing country, and that data printed in more than one place on it agrees | Yes: the document matches its template and its data is consistent No: at least one part of the check was flagged | Activity Log, only when available Scorecards: Document template match, only when available Risk signal: Template Match |
| Document Status | Checks the expiry date read from the document | Valid: the document hasn't expired Expired: the expiry date has passed | Activity Log, only when available Scorecards: Document status, only when available Risk signal: Not Expired |
| Image Quality | Checks that the document image is good enough to read: not low resolution, and with no vital data obscured | High: the image is readable Low: the image is too poor to read reliably | Activity Log Scorecards: Image quality Risk signal: Image Quality |
| Supported Document | Checks that the document type is accepted | Supported: the document type is accepted Unsupported: the document type isn't accepted | Activity Log Scorecards: a second Document type row Risk signal: Doc Supported |
| Image Color | Checks that the document image is in color | Color: the image is in color Black & white: the image is black and white | Activity Log Scorecards: Image color Risk signal: Color Image |
| Document Authenticity | Checks that the image quality allows a conclusive decision on whether the document is genuine | Verified: the document could be assessed Unverified: the quality didn't allow a conclusive assessment | Activity Log Scorecards: Document authenticity Risk signal: Authentic |
| Document Image Tampering | Checks the portrait photo on the document for signs of tampering or alteration | No: no tampering found on the portrait Yes: the portrait shows signs of tampering | Activity Log Scorecards: Document image tampering Risk signal: No Image Tamper |
| Security Feature Present | Checks that the security features expected on this document type are present and correct | Yes: the expected features are present No: features are missing or wrong | Activity Log Scorecards: Security feature present, only when available Risk signal: Security Features |
| Original Document Present | Checks that the image is of the physical document, not a photo of a screen, a photo of a photo or a copy | Yes: the image shows the original document No: the image appears to be a reproduction | Activity Log Scorecards: Original document present Risk signal: Original Present |
| Document Tampering | Checks the document image for signs of digital editing | No: no digital tampering found Yes: the image appears digitally altered | Activity Log Scorecards: Document tampering Risk signal: No Tampering |
| Face Detected on Image | Checks that a face was found on the document | Yes: a face was found on the document No: no face was found | Activity Log Scorecards: Face detected on image Risk signal: Face on Image |
The Activity Log also summarizes the document results in two rows on the step itself. See Overall Result.
Face and Liveness Checks
These results compare the requester's live capture with the document. The Liveness Check setting produces them from a selfie, which the Activity Log lists under Photo Fully Auto Report. With With Motion Detection on, they come from a head-turn video instead, under Motion Report. Motion Detection is an optional capability; see Affirm Feature Availability.
| Result | What it checks | Values and meaning | Where it appears |
|---|---|---|---|
| Face Detected | Checks that a single face of sufficient quality was found in the document image and in the live capture | Yes: a usable face was found in both No: a usable face wasn't found | Activity Log Scorecards: Face detection Risk signal: Face Detected |
| Liveness Detected | Checks that the requester performed the head-turn pattern correctly during the video capture. Requires With Motion Detection | Yes: the head turn was completed correctly No: it wasn't | Activity Log, under Motion Report Scorecards: Liveness detected Risk signal: Liveness Detected |
| Image Source Integrity | Checks that the live capture came from a trustworthy source, such as a real camera rather than an emulator or an altered upload | High: the source is trusted Low: the source was flagged | Activity Log Scorecards: Image source integrity Risk signal: Image Integrity |
| Spoofing Detection | Rates how likely the capture is a spoof, such as a replayed or injected capture, rather than a live person | Low: unlikely to be a spoof Medium: some signs of spoofing High: likely a spoof. Fails with the default rules | Activity Log shows the band, and Unverified for High Scorecards: Spoofing detection, with a cross for High Risk signal: Spoof Detection |
| Face Match Confidence | Rates how closely the face in the live capture matches the portrait on the document | High: a close match Medium: a partial match Low: a weak match. Fails with the default rules | Activity Log shows the band, and Unverified for Low Scorecards: Face match confidence, with a cross for Low Risk signal: Face Match |
Watchlist Checks
These results come from the AML Checks and OFAC Checks options in the step. The Activity Log lists them under Watchlist Standard Report. They need the Watchlist and KYC Screening capability; see KYC Compliance Checks.
| Result | What it checks | Values and meaning | Where it appears |
|---|---|---|---|
| Sanctions Lists | Screens the requester against government and international organization sanctions lists. Requires AML Checks | Passing: no sanctions match Failing: a possible match | Activity Log Approver scorecard: AML checks Risk signal: No Sanctions |
| Legal and Regulatory Warnings | Screens the requester against law-enforcement and regulatory monitored lists. Requires OFAC Checks | Passing: no warnings found Failing: a warning was found | Activity Log Approver scorecard: OFAC checks Risk signal: No Legal Warnings |
With the default rules, a failing result on either check fails the step.
Identity Enhanced Checks
These results come from the Identity Verification With Document Issuer check, which compares the requester's details with external identity data sources. The Activity Log lists them under Identity Enhanced Report. HYPR enables this check per tenant; contact your HYPR representative if it isn't available.
| Result | What it checks | Values and meaning | Where it appears |
|---|---|---|---|
| Address History | Checks whether the requester's address matches the address held in the identity data sources | Yes: the address matched No: it didn't match | Activity Log Approver scorecard: Address verified Risk signal: Address Match |
| Date of Birth | Checks whether the requester's date of birth matches the identity data sources | Yes: the date of birth matched No: it didn't match | Activity Log Approver scorecard: Date of birth verified Risk signal: DOB Match |
| Found in Data Sources | Shows whether the identity data sources found the requester at all | Yes: the requester was found No: the requester wasn't found | Activity Log, as a flag on the step Risk signal |
| Known Identity (IDP/Directory) | Shows whether the requester's directory profile already held the date of birth and address the checks need | Yes: the details came from the directory No: the requester entered them | Activity Log, as a flag on the step Risk signal |
With the default rules, this check passes when Known Identity or Found in Data Sources is Yes. Address History and Date of Birth aren't part of the default rules. For more on the two flags, see Activity Log.
Overall Result
These results summarize the whole check rather than one aspect of it. The three step rows appear at the top of the expanded Document & Biometric Verification step in the Activity Log. With Dual Document Verification, the second document adds rows with a Secondary prefix, such as Secondary Name Check.
| Result | What it checks | Values and meaning | Where it appears |
|---|---|---|---|
| Overall Result | Summarizes the whole verification in one result | Passing: nothing was flagged Not passing: at least one check needs attention, or no overall result was available | Risk signal: Overall Result Affirm API Not shown in the Activity Log or scorecards |
| Document Authentication | Summarizes the document checks | Verified: every document check passed. Document Template Match, Document Status and Security Feature Present also pass when missing if Overall Result is passing Unverified: at least one didn't | Activity Log |
| Name Check | Summarizes First Name Match and Last Name Match | Verified: both names match Unverified: at least one differs | Activity Log |
| Biometric Liveness Check | Summarizes the face and liveness checks | Verified: Face Detected, Image Source Integrity and Liveness Detected pass, Spoofing Detection isn't High and Face Match Confidence isn't Low Unverified: any of these fails | Activity Log |
Related
- Activity Log: the detail view that shows these results for each verification
- Approver Experience: the scorecard an approver reviews
- Document and Biometric Verification: the step settings that turn these checks on
- Risk Policy Builder: rules that read these results as risk signals
- Verification Outcome Status Enum: the status of the verification as a whole