What we'll review:
SwiftID Requirements
SwiftID Setup
SwiftHire Workflow
Processing Results
Final Report Results
***Important Update: Please note the SwiftID product will no longer be available after December 31, 2023***
Summary
SwiftID allows customers to decrease the risk of identity fraud by giving them the ability to combine identity verification into the background check process. Seamlessly collect and instantly validate photo IDs, driver licenses, and passports. In short, SwiftID is a fast, automated mobile tool to verify identity. With SwiftID, you can:
- Verify correct name/dob is on the background
- Verify the person applying for the background is the same person pictured on the ID
- Validate in seconds
- Detect fake & duplicate IDs
This tool works similarly to the past address history trace and can be used in conjunction with it to help decrease background check fraud.
*NOTE* SwiftID is an Identity Verification Tool only and it is not part of the FCRA process. If a candidate's identity cannot be confirmed through the verification process, additional identification documents may be requested.
SwiftID requirements
SwiftID is compatible with SwiftHire Mobile and can be completed on mobile or desktop. This product is not intended for use with HR or Admin module orders.
How it works:
There will be a new search type to support each product:
- SwiftID Check (ID Verification)-Verifies photo IDs, driver licenses, and passports
- SwiftID Selfie Match (ID Verification with Selfie Match)-Verifies photo IDs, driver licenses, passports and uses AI Technology to match it against a Selfie Photo taken in real-time
Candidates will be prompted to upload an ID or ID and selfie combination in the existing SHM workflow. The ID Information can used to populate the SHM application (Name, DOB and Address).
Compatible ID Types
- AAMVA-compliant driver license or identification card. This includes all state or provincial issued driver licenses and identification cards in the United States and Canada. AAMVA-compliant identity documents will include a PDF417 2D barcode on the back of the ID.
- ICAO-compliant machine-readable travel documents. This includes all passports worldwide as well as many national ID cards. These travel documents will include a machine-readable component on either the front (passports and national ID cards) or the back of the document (national ID cards).
If there are any flags, the information is routed to your QA for review! The CRA or HR can revert to verifying those items using traditional means of identity verification (CBSV, W-2 or other forms). Please note that applicants should not be denied employment based on these findings.
deverus invoices the CRA for this product, based on when it is in a completed report.
SwiftID setup
SwiftID can be ready for clients in four steps:
Step 1: Rename the custom searches (optional)
Upon product release, two new search types will be available in your system. You can rename them by going to System Settings -> Search Names
SwiftID is the ID upload only.
SwiftID Selfie Match includes the ID upload but with the added requirement of a selfie to be supplied.
Step 2: Enable the Integrated SwiftID researchers
There is an integrated researcher for each SwiftID report type.
Go to Researcher -> Researcher Network and click 'GO' for each type.
Click the slider icon to enable the Integrated SwiftID Verification researcher.
Click 'Edit Settings' to set the search cost.
If there are clients that do not wish to use the automated service, you can create 'Client Type' or individual 'Client' exceptions by selecting the 'Add Client Exception(s)' option.
*NOTE* Please note that the Researcher Fee does not get applied.
Step 3: Enable the search type at the Client Type level
Before adding either product to a package, the report type must be enabled for the Client to order it.
Go to Sales -> Client Types -> select the Client Type you desire to order, then click -> Search Options.
*NOTE* Please note that the Client type 'Search Option' only allows one SwiftID product to be selected at a time.
Step 4: Add a SwiftID product to a package
The last step is to add the desired SwiftID product to a package. Just as with the Client Type 'Search Option' setting, a package can only contain one of either report type.
When one SwiftID product is selected for a package, the other SwiftID product will be made unavailable.
*NOTE* A quantity of one of either SwiftID product can be added to a package. The SwiftHire subject will go through the process only once during a SwiftHire session.
SwiftHire Workflow
SwiftID will add a new step to the SwiftHire Mobile process. It will take place after the subject has completed their consent documents but before the normal screening search type information is requested:
*NOTE* The SwiftID Check and SwiftID Selfie Match workflows are nearly the same. The only added difference is that the SwiftID Selfie Match will also require the subject to add an actual 'selfie.'
SwiftID Check
When the subject arrives on the SwiftID page of their SwiftHire session, they will encounter a screen as shown in the example below:
Here, the subject can select which form of identification they will provide. After selecting the Identification type, the upload screen will appear. On desktop, this step will look like this
Users completing their SwiftHire via a desktop computer will have the option to provide their mobile phone number. When provided with a mobile phone number, the SwiftID service will allow the subject to use their mobile phone camera to take images of their Identification and add it to their in-progress SwiftHire session.
For users that do not have a mobile device, they may choose the 'I don't have a phone' option. When this option is selected, the subject may select an image from their computer. The example is shown below:
Once the front and back images are uploaded, the SwiftID service will provide a final confirmation screen only if the barcode or machine-readable components are not read.
The final edited name will populate in SHM. Barcode and Machine-readable names will not be edited.
SwiftID Check with Selfie Match
In addition to the steps shown above, the subject will be required to submit a selfie. This can be completed with their mobile device or by uploading an image from their desktop computer. First, the subject must allow the device to grant access to it's camera.
Next, consent must be confirmed by the subject to allow the service to verify their identity. (These are stored for 30 days)
Once the subject agrees that the details provided are correct, the subject will proceed with the rest of the SwiftHire session.
Auto Population in SHM
Because the ID upload process comes before the applicant has a chance to enter their own screening information, the SwiftID product has the ability to Auto Populate some of the information directly from what is detected on the applicant ID.
-
If the address has been self-entered in the SHM process ID address will not populate
-
If the address has been provided by the ATS and pre-populated, ID address will not populate
-
If the name has been provided by an ATS, the ID name will still be populated and locked
-
If an applicant manual enters a name in SwiftID because a Barcode reader was not able to read the name, it will populate that name
The candidate will have an opportunity to enter or edit their name if the information is not barcode or optical character read (triggering the manual flag and source). The name and DOB in all instances will populate in SHM and be locked for editing. The purpose is to reduce identity fraud on the background check. The address will populate and be editable.
*NOTE* First, Middle, and Last names can all trigger different sources. Names that were populated from barcode or OCR are not editable by the subject.
Processing Results through Quality Assurance
The final status of a SwiftID search will be 'Complete' or 'Unable to Complete.' For searches that are verified by the SwiftID researcher without QA, the search will be completed automatically. Searches that are not verified by the recognition service will receive 'unable to complete' and will always go to QA. SwiftID search types that get sent to QA will show administrators the following information:
How the ID is Read: Sources and Manual Entry
The ID barcode will be scanned to populate the correct user's data. In the instance an older ID type cannot be read by barcode, the product will scan the ID and compare it against DMV state templates for fraudulent flags. The Optical Character items presented on the ID will be read and extracted. If an ID cannot be read by a barcode, these automatically get set to QA for a quick review along. This product will label how each element (ID number, name, DOB, name) is collected from the SHM session. In the example above, the information was collect via barcode and optical character recognition. Please see each method below:
-
Manual: sourced from data entered manually by the user when prompted to confirm or enter their basic details. A verification with manual data entry will always have the id_manual_entry flag.
-
Machine Readable: sourced from a machine-readable zone typically found on passports or other national ID cards.
-
Optical Character Recognition: sourced from human-readable components typically found on the front of identity documents through optical character recognition.
-
Barcode: sourced from a PDF417 barcode typically found on the back of the AAMVA-compliant US or Canadian ID or DL.
This information is viewable in QA only and not displayed on the final report. If the ID is not readable, the applicant will get the opportunity to manually enter their data. This will trigger the "Manual" flag and send the searches to QA for review.
SwiftID QA Flags
SwiftID has powerful built-in Quality Assurance logic that will automatically send the search to QA for any of the following reasons:
The information scanned for the front is significantly different from the information drawn from the back.
Expired ID
Manual Entry
The data about the photo ID returned was provided manually by the user and has not been verified by SwiftID.
Sample ID detected
The provided ID was a sample ID that is inauthentic for that user.
Fake ID detected
The user provided an ID that is likely to be inauthentic.
Unreadable Text
Insufficient text was detected in the front image.
No Face Detected
No face was detected in the front image of the ID.
Too Many Faces Detected
The image provided included more faces than expected for the ID type.
Partial Reading
Only part of the machine readable zone was successfully read from the scanned image.
Front Suspicious
The user provided front image(s) were flagged as suspicious and warrant further review.
Back Text Unreadable
Insufficient text was detected in the back image.
A partial 2D barcode was detected in the back image.
A full 2D barcode was detected in the back image but could not be decoded.
The user provided back image(s) were flagged as suspicious and warrant further review.
An unspecified error occurred when attempting to read the back image of the ID.
A full 2D barcode was detected and decoded but the data was in an unsupported format.
No face was detected in the selfie image.
Too many faces
The user was unable to take a valid selfie looking at the camera.
The user provided selfie images that were unlikely to be genuine.
An unspecified error occurred when attempting to process the selfie.
No face was detected in the liveness image.
The liveness image was rejected for having too many faces.
Liveness challenge failed
The user provided liveness images that were unlikely to be genuine.
The similarity score between the selfie and the photo from the ID was too low.
The similarity score between the selfie and the photo from the ID is inconclusive.
face_comparison_unavailable
A similarity score between the front and selfie could not be determined.
The similarity score between the selfie and the liveness photo was too low.
The user did not provide consent to digitally compare the faces across images where applicable.
Final Report Results
The information gathered from the actual SwiftID product is not viewable on the final report, as they are not considered to be a part of the standard FCRA Background check. Similar to the SSNT trace results not being able to be displayed on the report, the information is used to reduce fraud by allowing the CRA to run the correct name/DOB combination and ensure the same person to the ID is the applicant. The final report result will either be "Complete" or "Unable to Complete", along with a comments section.
*NOTE* The FRONT and BACK ( and Selfie, if applicable ) images will NOT be visible on the completed report but the images do show the SwiftID Check Documents section in the HR Module.
If confirmation of identity cannot be attained using this product, the CRA should consult with legal counsel on an alternate verification process (W2, CBSV, Utility bill, etc).
SwiftID SHM Flow
https://drive.google.com/file/d/1PhpAJSx75dceSreyI13RMpcPVchbTQWa/view?usp=sharing
Comments
0 comments
Please sign in to leave a comment.