Banque Misr onboarding & KYC

The problem

A national bank needed digital account opening that could satisfy AML and regulatory obligations without turning every application into a manual review. The existing flow could not scale with demand, and compliance requirements were shaping the architecture from the outset rather than being layered on afterwards.

What I did

1. 01Split onboarding into roughly twelve independently deployable Spring Boot services on Spring Cloud, each owning one stage of the journey.
2. 02Architected the KYC module around identity verification and document-processing workflows aligned to FATF and Central Bank of Egypt standards, with Camunda BPMN modelling the review paths.
3. 03Designed a security framework on Spring Security and LDAP, and drove OWASP adherence across the team.
4. 04Profiled the hot onboarding paths and reworked Redis caching plus the PostgreSQL and Oracle query strategies behind them.

Outcome

The platform serves roughly 500,000 customers. Average API response latency fell about 35% on high-traffic onboarding flows, and security review findings dropped roughly 30% team-wide.

Stack

Java Backend Engineer · Xebia

Client work under a delivery partner — the platform is not publicly reachable, so there is no live link.