Stanbic IBTC: Digi Assist, On-the-Go Account Opening

1. Regulatory analysis and gap mapping

Started with a deep regulatory analysis of the CBN's tiered KYC framework while mapping the as-is process with relevant stakeholders. I mapped every Enhanced Verification requirement for Tier 3 against what was technically feasible, identified the compliance gaps in the existing onboarding flow, and translated that into requirements the development team could act on. Getting this right at the start was critical; every design decision downstream depended on it.

2. Swim lane process design across four account types

Designed four distinct swim lane process flows covering Tier 1 Savings, Tier 3 Savings, Current Account, and Salary Account onboarding. Each flow mapped the journey across six roles: Staff, Bot, Compliance Officer, KYC Officer, Onboarding Officer, and the Automated Verification and References (AVR) system. The Tier 1 flow was relatively lean. Tier 3, Current, and Salary were significantly more complex, each with different document requirements, PND management logic, verification triggers, and exception handling paths.

3. NIBSS integration workstream

Led the integration workstream for NIBSS. Real-time BVN and NIN validation was the backbone of the entire KYC process, as every account type depended on it. I worked with solution architects and engineering teams to define API contracts, data validation rules, and fallback behaviour when NIBSS returned edge-case responses. This covered both customer-facing validation and compliance-side requirements, with all security standards held to the highest order and data privacy documented across every integration touchpoint.

4. Automated sanctions screening and PND logic

Designed the automated sanction screening logic built into the BOT layer. Once a customer submitted their request, the system conducted automated sanctions screening before any human reviewer touched the account. If screening passed, the account was created and documents were pushed to Finacle, DSX, and Omniflow simultaneously. If screening failed, the Compliance Officer received an automated notification and the account was flagged with a PND. I mapped every branch of this logic, including the False Violation path, across all four account types.

5. Biometrics, OTP, and OCR integration

Oversaw integration of the biometric liveness detection and facial recognition layer, OTP verification via BVN-linked phone number and email, and OCR-based document capture for government-issued IDs. Each had its own vendor coordination, data handling requirements, and failure mode behaviour that needed precise specification in the SRS.

6. BRD and SRS authorship

Authored the Business Requirements Document and System Requirements Specifications as primary author. These were the translation layer between what the business and compliance teams needed and what the development teams could build. I facilitated reviews across Compliance, KYC, Legal, and external technology vendors, incorporating feedback without losing the regulatory integrity of the specifications.

7. AI fraud detection and AML monitoring

Contributed to the design of AI-powered fraud detection and AML monitoring, collaborating with data scientists to define risk signals, transaction anomaly thresholds, and automated compliance reporting requirements tied to the CBN's AML/CFT mandate. This included specifying how cash flow and behavioural data would feed into the credit risk model for future lending extensions built on the same platform.

8. KPI framework and post-launch performance

Defined the KPI framework for post-launch performance measurement, covering account activation rates, verification failure rates by step, processing times, compliance officer review turnaround, and AVR completion rates. I produced performance reports for stakeholder review and used the data to drive iterative optimisations in the months after launch.