← All case studies

Mapping one KYC vendor relationship across five apps and three internal teams

Integration Engineer Jan 2026 – ongoing
Middleware / webhooksReact NativeFlutterNative Android

The problem

First Bank runs biometric KYC across five separate channels — its core mobile app, a new super-app, a token-activation app, a DRC-market app, and online banking — built independently by different internal teams and an external vendor, on React Native, Flutter, and native Android. Each channel had drifted onto a different SDK version, retry policy, and fallback behavior, with no single owner able to see the whole picture.

My approach

Ran a channel-by-channel audit against the partner’s own integration engineer and IT infrastructure contacts to document what each app actually implemented — not what was assumed — versus the bank’s centralized middleware, which authenticates and routes every callback back to the right requesting channel.

What I built

A single source-of-truth map of all five channels: SDK version and retry/fallback behavior per app, which team owns each one, and where the middleware’s basic-auth-routed callback model was (or wasn’t) being used consistently. Flagged the channels missing a Job Status API fallback for undelivered callbacks as the priority gap.

Outcome
Gave the bank's technology and infrastructure teams a shared reference for the first time across all five channels, surfacing inconsistent retry/fallback handling before it caused an incident, and clarifying ownership for the two channels still mid-build.