Back to selected work

Fintech application

BillBnk
case study.

Agent banking, bill payments, AEPS, wallet operations and multi-bank payouts in one mobile product.

BillBnk interface and project preview
4Core technologiesFullCase studyUXUser focusedWebResponsive

Why BillBnk needed to exist.

Agents often switch between fragmented tools for onboarding, payments, AEPS, wallet activity and payouts.

A mobile fintech product consolidates KYC, bill payment, wallet, AEPS and multi-bank payout workflows.

Who it serves

Banking agents and customers needing assisted financial services.

Business value

Enables agents to serve more customer needs from one product and creates multiple transaction revenue paths.

Designed around the essential workflow.

01

KYC onboarding

Designed as part of a cohesive fintech application experience, with clarity, reliability and practical use in mind.

02

AEPS transactions

Designed as part of a cohesive fintech application experience, with clarity, reliability and practical use in mind.

03

Bills and wallet operations

Designed as part of a cohesive fintech application experience, with clarity, reliability and practical use in mind.

04

Multi-bank payouts

Designed as part of a cohesive fintech application experience, with clarity, reliability and practical use in mind.

Value for users and the business.

Consolidates agent workflows

Expands service coverage

Improves transaction visibility

Built with constraints in view.

Financial compliance is mandatory

External banking dependencies affect availability

A stack where every tool has a clear responsibility.

The architecture for BillBnk was shaped around the product workflow, integration boundaries and long-term maintainability. Technologies are used for specific responsibilities rather than added only to make the stack appear larger.

Experience1 tools

React Native

Delivers shared mobile product experiences across Android and iOS.

Product capability3 tools

KYC

Structures identity-verification steps required by financial workflows.

Wallet

Tracks stored-value operations, transaction history and balance-oriented workflows.

AEPS

Supports assisted banking transactions through the Aadhaar Enabled Payment System.

Clear boundaries

Interface, business logic, persistence and external services remain separated so changes are easier to reason about.

Defensive data handling

Validation and predictable contracts protect downstream workflows from incomplete or unexpected input.

Deployment-aware design

Runtime limits, secrets, external dependencies and failure paths are considered as part of the implementation.

01

Discover

Understand the users, business objective and constraints.

02

Design

Map the core journey and reduce unnecessary interaction.

03

Build

Implement maintainable interfaces, services and data flows.

04

Validate

Test behavior, responsiveness and failure paths before release.

Project by Sandipan Das

Have a similar
problem to solve?

Start a conversation Open GitHub