QR-Enabled Citizen Card
A secure citizen card with QR verification and biometric enrollment, engineered for province-wide rollout.

What changed, and what came of it
The province needed a way to identify residents reliably at the point of service. We delivered a citizen card program: enrollment and biometric capture, card production with a QR credential, and a verification service that front-line staff can use from a counter terminal or a handheld device. It is used by provincial offices delivering services to residents.
Before
Identification was fragmented and paper-based. Each office kept its own list, residents presented whatever document they had, and staff had no reliable way to confirm that the person in front of them was the person on the record. That slowed every transaction and made duplicate and fraudulent claims difficult to detect.
What we built
We built a single enrollment and verification platform. Residents are enrolled once, with biometric capture, and issued a card carrying a QR credential. Any authorized office can scan the card and confirm the holder against the provincial record in a single step, without needing a copy of the underlying database.
Residents enrolled and issued cards through the program. We publish the order of magnitude rather than a precise figure because the register continues to grow.
The availability target the platform was engineered and contracted to meet.
The verification path is designed to return a result in under a second at the counter, so it does not slow the transaction it is supporting.
Each outcome carries the label that describes what kind of claim it is. We never present a target as a measured result — see the Ledger and our claims policy.
What the system does
- Resident enrollmentCapture of resident details and biometrics, with de-duplication against existing records.
- QR credentialA scannable credential on the card that resolves to the resident record without exposing personal data in the code itself.
- Verification serviceCounter and handheld verification returning a confirm/deny result and the minimum data the office needs.
- Card productionBatch card printing with the QR credential, ready for distribution through barangay and municipal offices.
- Role-based accessEach office sees only the resident data its function requires; administrative functions are separated from counter functions.
- Audit trailEvery verification and every record change is logged against a named account.
How it fits together
A layer-level view. We do not publish hostnames, addresses, credentials, firewall rules or topology detail for systems in production.
How it is protected, and how it went live
Controls in the delivered system
High-level controls only. Detailed security design is shared under NDA with the client organization, not published.
How it was rolled out
- Pilot enrollmentA single office enrolled first, so enrollment throughput, biometric capture quality and card production were proven at small scale.
- Verification rolloutCounter verification introduced office by office, with staff training at each site.
- Card issuanceBatch production and distribution through municipal and barangay offices.
- SupportPost-implementation support, with enrollment and verification issues triaged against the audit log.
Frequently asked questions
Yes. The reusable part is the register and the verification service, not the card stock — the card is the cheapest component to change. What sets the schedule is local: enrolment capacity, card production, counter staffing, and the ordinance or resolution authorising the programme.
Biometrics are used at enrolment to stop the same resident being registered twice. Whether templates are retained afterwards is a separate decision with its own obligations under RA 10173, and it should be made deliberately rather than inherited from a card vendor's default configuration.
Because a card that carries the resident's data stays readable forever once printed, including after it is lost. Resolving a signed identifier against the register at the moment of the check means a replaced or revoked card fails immediately, and the personal data never leaves the register.
Access is role-based and every read is recorded in an audit trail, so the question 'who looked at this record, and when' has an answer. That audit trail is what an investigation or a National Privacy Commission enquiry actually examines, and it has to exist before it is needed.
Planning a similar project?
Tell us the organization, the process and the constraint you are working against. We can help shape the architecture, the implementation approach and the next step.