Philippines National ID

Overview

The Philippines National ID refers to both the plastic card, and the National ID in Paper Form (previously called ePhillID), both of which have a QR code that can be scanned and validated against the Philsys database to ensure validity.

ID: philippines-physical-national-id-qr
Type: eID (card)
Verification Type: Enrichment
Regions: Asia
Countries: PH
Adoption: 89,000,000
URL: https://philsys.gov.ph/ephilid/

Integration with Trinsic

ePhilID 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

When verifying the ePhilID, a user must scan the QR code on their National ID Card, or on their National ID in PAper Form (ePhillID). Trinsic then validates the attributes against the government source of truth and returns the attributes listed above along with a confirmation that the identity is still valid.

How to Test

While using a test mode App, launch the widget or the provider directly.

Enter the credentials and submit.
- qr code: (see below)
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: None — No user-facing action is required to start the flow.
Collection Method: PollResult — Results arrive asynchronously; poll with the resultsAccessKey returned at session creation.
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 Attributes
These 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`	Always	-
`person.suffix`	Sometimes	If available
`person.dateOfBirth`	Always	-
`person.sex`	Always	-
`document.type`	Always	-
`document.issueDate`	Always	-
`document.issuingCountry`	Always	-
`attachments.documentPortrait`	Sometimes	If using ePhilID

Frequently Asked Questions

When we share the QR code with Trinsic, what is validated against the government system of record?

The QR code is shared with Philsys and returns the attributes along with confirmation that the signature from the issuing authority is valid and if the ID checks is active or revoked.

Which documents contain a verifiable QR code?

The Philippines National ID Card, the Philippines National ID in Paper Form, and the Digital National ID all contain a QR code that can be verified by Philsys. For an overview of the various forms of National ID with QR codes, view this page: https://philsys.gov.ph/the-national-id/.

How does the Philsys Biometric Match compare to verifying the QR code on an ID document?

The Philsys Biometric Match requires some attributes about the user and then prompts the user to do a Philsys-provided liveness flow, to confirm that the attributes match the user performing the liveness verification.

Why is place of birth not extracted from the QR code?

It is extracted from the QR code, but not yet exposed in provider specific output yet.