City-Wide Digitalization & Citizen Services
A city website, mobile app and NFC-enabled citizen cards giving residents access to payments, permits and public information.

What changed, and what came of it
A city-wide program rather than a single system: the public website, a mobile app and an NFC citizen card, joined so that a resident has one identity across city services and can transact from a phone instead of a queue.
Before
The city wanted to modernize how residents interact with government, but the requirement was not simply to put forms online. Access had to work for residents who transact in person as well as those who use a phone, transactions had to be secure, and identification had to be consistent across services rather than re-established at every counter.
What we built
We delivered three connected pieces: a city website for public information and service entry points, a mobile app for residents, and NFC-enabled citizen cards for identification at counters. Together they support bill payments, permit applications and access to public information, with secure transactions and one identity across city services.
Residents can reach city services from a browser or the app.
Identification at city counters by card rather than by document.
Bill payment and permit application available without attending an office.
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
- City websitePublic information and the entry point for online services.
- Mobile applicationResident-facing app for payments, applications and notifications.
- NFC citizen cardsTap identification at city counters for residents who transact in person.
- Bill paymentsPayment of city dues online, recorded against the resident account.
- Permit applicationsApplication submission and tracking from web or app.
- Inclusive accessIn-person and digital routes to the same service, so no resident is excluded by the channel.
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
- Website and contentPublic information and service entry points delivered first.
- Citizen identity and cardsNFC card issuance and counter identification introduced.
- Mobile app and paymentsResident app released with payments and permit applications.
- Support and iterationPost-implementation support and enhancement as services were added.
Frequently asked questions
In Tayabas City it covered a city website, a mobile application, NFC-enabled citizen cards, bill payments, permit applications and the inclusive-access design tying them together. The scope was deliberately not 'put the forms online' — it was the services residents actually transact.
They give residents a single credential for city services — payments, permits and access to public information — so identification does not restart at each office. The card is a key to a record, and the record is what the offices share.
That was an explicit requirement rather than an afterthought. Access had to work for residents who come to a counter as well as those using a phone, which means both channels write to the same record instead of the counter running a parallel paper process alongside a digital one.
Yes, and it is usually the better sequence. One service delivered properly establishes the resident record, the payment integration and the operating habits the rest depend on. Programmes that start with every office at once tend to stall on data quality.
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.