Case study · Confidential client
Payment Network Merchant, Acquirer & Admin Portals
A case study on keeping a national payments network's portals modern, secure and tested: six Angular major upgrades, a legacy admin CMS rebuilt in modern Angular, and two-factor login for a regulated platform.
Portals · one codebase
Merchants
Acquiring banks
Identity-verification officers
Administrators
Live activity
● Payment approved
● Identity verified
● Settlement reconciled
● Payment approved
- Role
- Main front-end developer, from the first commit
- Project period
- June 2023 to November 2026, at FOO
- Contribution
- About 60% of the portal's commits
- Stack
- Angular, TypeScript, Laravel
AngularTypeScriptRxJSLaravelJasmineKarmaDockerAngular MaterialAngularTypeScriptRxJSLaravelJasmineKarmaDockerAngular Material
6
Angular major upgrades, 13 → 19
21
of the portal's 34 feature modules created by me
5.4 → 9
Laravel upgrade of the legacy admin CMS
22,900+
lines of unit tests I wrote
The context
One codebase, four audiences.
A regulated, GCC-based payments network runs its merchant ecosystem through a single Angular and Laravel codebase. The same platform serves four very different groups of users.
- Merchants
- Acquiring banks
- Identity-verification officers
- Administrators
Building the portals
Lazy-loaded feature modules.
I created 21 of the portal's 34 feature modules. They cover three areas:
01
Merchant operations
- Merchants
- Branches
- Terminals
- Bulk uploads
02
Identity verification
- Case statuses
- MRZ-based name extraction
- Token-protected ID images
03
Platform tools
- User management
- Security settings
- Analytics
- An SDK download area
- An IBAN directory
Upgrades
Six Angular upgrades without a rewrite.
The app started on Angular 13 and was upgraded one major version at a time, so the product kept shipping throughout.
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- Jun 2023Angular 13
- Oct 2023Angular 14, 15 and 16
- Feb 2024Angular 17, with the move to MDC-based Material components
- Jul 2024Angular 18
- Jun 2025Angular 19, plus Laravel 12
Legacy
Retiring a legacy admin CMS.
2017
The starting point
An AngularJS admin CMS on Laravel 5.4 and PHP 5.6.
January 2025
First upgrade
Upgraded to Laravel 9 and PHP 8.1, and moved into Docker.
Late 2025
Rebuilt in Angular
The screens were rebuilt as Angular modules inside the new portal.
- Dashboard and configuration
- Bank, acquirer and merchant management
- Messaging and app-version tools
Security
Security for a regulated platform.
Two-factor login
Google Authenticator sign-in, prepared for production in December 2025.
Log masking
Sensitive data masked in logs (October 2024).
SSRF fix
A server-side request forgery issue closed.
SonarQube findings
Code fixes driven by SonarQube, alongside closing security scan and assessment findings.
Delivery and testing
Built from source, tested at scale.
Delivery
Compiled bundles used to be committed to the repository. In January 2025 I added Docker files and moved the production build into CI, so every deployment builds from source the same way.
Testing
22,900+
lines of Jasmine and Karma tests, about a quarter of the suite
What I took from it
01
Small, steady upgrades cost far less than a rewrite.
02
In regulated software, security and testing are part of the feature itself.
Stack
- Angular
- TypeScript
- RxJS
- Angular Material
- AngularJS
- Laravel
- PHP
- Jasmine
- Karma
- Docker
- SonarQube
Want this on your platform?