PhilSys Biometric Match
Overview
The Philippines' official electronic ID for accessing government services and verifying identity. Collects key personal data then performs a liveness selfie to match against the Philippine Statistics Authority’s national ID records covering 90 M+ citizens.
- ID:
philippines-philsys-match - Type: eID (database)
- Verification Type: Match
- Regions: Asia
- Countries: PH
- Adoption: 90,000,000
- URL: https://philsys.gov.ph/ephilid/
Integration with Trinsic
PhilSys Biometric verification is integrated into Trinsic's identity acceptance network allowing businesses to verify users against the government system of record in the Philippines.
- Permission required: Yes, this method requires registration before you can activate it for your users. Please contact Trinsic to begin this process.
- Cost: Contact the Trinsic team.
User Flow
PhilSys Biometric Match requires the user to input some data about themselves into a form, and then complete a liveness selfie to match their biometrics against the system of record.
Customers can bypass the form-fill step by passing in known identity data about the user when launching the integration. In this scenario the user would go directly into the liveness step. To see the video of bypassing the form fill, watch this video. The liveness step, which matches the biometric of the live user to the biometric stored within the system of record, is operated & hosted by PhilSys (the government agency that operates the service) and cannot be bypassed. Trinsic serves the liveness step through an iFrame, which means Trinsic's domain is shown. If your use case requires serving the liveness step through your own iFrame, please reach out to your Trinsic representative to inquire.
In either case, you must ensure all data entered matches exactly what appears on an individual's National ID or else the matching service will return a false result. To see the demo of a user inputting their data, watch this video.
How to Test
While using a test mode App, launch the widget or the provider directly.
- Enter the credentials (you can fill in random data) and submit.
- Perform a liveness check.
- At the end, you will be presented with test data for the verification session.
Direct API Requirements
Direct is not a requirement.You can integrate with this provider using the Widget or Hosted UI instead, with no additional integration requirements on your end.
What your integration must support in order to use this provider with the Direct Provider Sessions API.
- Supports Direct Provider Sessions: ✅
- Launch Method:
LaunchBrowser— Send the user's browser (via redirect, popup, or new tab) to the given URL. - Collection Method:
CaptureRedirect— The user is redirected back to your app with aresultsAccessKeyupon completion. - Requires Input: This provider requires input before verification can proceed.
- Trinsic-Hosted UI: A Trinsic-Hosted Fallback UI exists for this provider, which may be invoked to cover gaps in your integration's capabilities.
Outputs
Normalized AttributesThese attributes form part of our normalized model, a standardized set used across providers. Trinsic normalizes this for you and lets you know when a property is available for each provider.
| Field | Availability | Notes |
|---|---|---|
person.givenName | Always | - |
person.familyName | Always | - |
person.middleName | Sometimes | If provided |
person.suffix | Sometimes | If provided |
person.dateOfBirth | Always | - |
Frequently Asked Questions
Does this flow support attribute level matching?
No, the Philsys Biometric Match only supports an overall yes/no confirmation of the attributes and the Philsys liveness. If any of the attributes do not match what is on file, or if the selfie does not match, the flow will fail.
Updated 5 days ago