Engineering case study · IFIC Bank PLC

From identity capture to a bank account.

My full-stack contributions to branch-led and remote eKYC onboarding, with a focus on core banking integration, data migration, and operational reliability.

Next.js.NET 8Oracle 19cIdentity verification

Explore the engineering Download CV

Conceptual illustration of an identity card, face capture, approved document, and secure storage

ROLE

Full-stack engineer

Frontend, backend, and integration work within the bank engineering team.

CONTEXT

Branch-led + Selfled

Both channels in production since 27 September 2026, across 189 branches and 1,224 sub-branches.

FOCUS

Reliable system boundaries

Verification, CBS outcomes, file references, and migration.

My contributions

The workflow is only as reliable as its handoffs.

Two channels. One onboarding journey.

I worked across branch-led onboarding, remote Selfled account opening, and the internal review console. The work connects guided customer forms, identity checks, risk grading, and maker-checker/BAMLCO review.

Next.js interfaces and .NET 8 backend workflows
Field validation, Bangla input, and applicant capture
Onboarding completion and dedup checks before account creation

Core banking that can handle a retry.

A timeout does not necessarily mean a customer or account was never created. I implemented progress-aware orchestration that reuses recorded results and distinguishes a refusal from an unconfirmed outcome.

Customer creation, account opening, and joint-holder attachment
Preservation of created customer identifiers on failure
Bounded execution and explicit retry classifications

Moving data without losing its context.

I built PostgreSQL-to-Oracle migration tooling with preparation, validation, reconciliation, and rollback generation. Legacy file locators let the file service retrieve historical documents on demand.

Profiles, accounts, roles, transaction data, and onboarding progress
Explicit write guards and expected-schema checks
Shared file service and reusable backend client

Verification that tells the right story.

I improved EC verification, face capture, and photo persistence so both reviewers and customers can distinguish identity mismatches from service failures. Photo references are saved before a capture step is marked complete.

Date-of-birth retry handling and readable Bangla logs
Preserving verified captures during incomplete replacements
Clear separation between service outages and mismatches

The tools behind day-to-day operations.

I worked on account-opening PDFs, joint-applicant ordering, document access, and integration-log investigation. These details help support teams follow what happened across a multi-service workflow.

Individual and joint account-opening forms
Scoped integration searches and credential masking
Trace identifiers, approval notifications, and dashboard totals

Engineering in a team

This case study describes my contributions to a shared banking platform. It focuses on implemented capabilities; it does not claim sole ownership or unmeasured improvements in speed, accuracy, or uptime.

All projects