The challenge
Registering an applicant and transferring a property in Punjab depends on several outside systems: the national identity authority, government and private fee collection, and the tax authority. The new platform had to talk to all of them securely, and keep working at hundreds of service centers when any one of them was slow or changed.
What I built
- Integration microservice: every external system is reached through one dedicated microservice, so a change or failure at a partner never spreads into the core services.
- Secure integration wrapper hosted in a whitelisted environment, because government endpoints only accept calls from approved networks.
- Applicant registration flow: capturing and verifying the citizen before any land transaction.
- Property transfer flow: the end-to-end transfer, including the fee payments it requires.
- Biometric device integration for in-person thumb-impression verification at the counter.
Integrations
| System | What it is | What I built |
|---|---|---|
| NADRA | National identity authority | CNIC and thumb-impression verification |
| ePay | Government payment gateway | Government fee payments in the transfer flow |
| Payzen | Payment gateway | Non-government fee payments |
| FBR | Federal tax authority | Challan (tax payment) verification |
| Phone verification | SMS service | Contact number verification |
Technical highlights
- Platform of 14 microservices behind an Ocelot API Gateway, containerized with Docker.
- Integrations isolated from business services, so problems with a partner system are contained in one place.
- Angular 18 front end.
Results
500+service centers live across Punjab
14microservices in the platform
5external integrations built and owned