Skip to content
Nikhil Sharma
Airtel Payments Bank · Business

Airtel Payments Bank for Business

Combining merchant payments, current account, settlement, and lending into one business banking experience.
Status
Field report v1 · shipped
Duration
Three quarters
Case type
Business app + ecosystem strategy
Role
Head of Product Design
Team
4 designers, 2 PMs, 10 engineers, business, lending, analytics, operations, compliance
At a glance
3 quarters
Strategy, design, and ship
4 designers / 2 PMs / 10 engineers
Core product team
5 priority metrics
CA cross-sell, Soundbox adoption, settlement linkage, lending funnel, app adoption
Tier-3 / tier-4
Primary merchant design context
AI Insights
Designed and in development
The problem

The merchant experience was fragmented.

Merchant payments, Current Account, settlements, QR, Soundbox, and lending opportunities were not experienced as one connected business relationship.

The old business app was also carrying real product debt: slow loading, confusing navigation, unclear labels, visual clutter, backend failures, and everyday tasks that took far longer than they should.

For small merchants, especially in tier-3 and tier-4 markets, this meant daily business tasks took more effort than they should.

The business insight

Merchants were already connecting payments and banking.

Market visits showed that many merchants were using Airtel Payments Bank Current Account as their settlement account.

That was the strategic opening.

Most merchant players can help businesses accept payments. Airtel Payments Bank could go further: payment acceptance, settlement, current account, QR, Soundbox, reports, and future lending could live inside one owned banking ecosystem.

When merchants used Airtel Payments Bank Current Account for settlement, settlement could become instant instead of moving through another bank account with a time lag.

The shift

From payment acceptance to business banking.

The goal was not only to help merchants accept payments.

The goal was to turn a merchant relationship into a business banking relationship.

Airtel Payments Bank for Business combined merchant use cases and current-account use cases into one app, creating a clearer path for current account cross-sell, Soundbox adoption, settlement linkage, and transaction-led lending.

What shipped

A business banking app covering:

  • Today's collection
  • Settlement balance
  • Current Account balance
  • QR payments
  • Soundbox management
  • Transaction history
  • Settlements
  • Reports
  • Current Account cross-sell
  • Loan / lending eligibility
  • Business app adoption flows
  • Language / vernacular support considerations
  • AI Insights as an in-development layer

The app is shipped. AI Insights is designed and in development.

Key product decisions
01

Make Current Account the business anchor

Current Account was not treated as a separate banking product. It became the anchor that connected settlement, merchant acceptance, and future lending.

02

Combine merchant and banking into one dashboard

Merchants needed one place to see collections, settlements, Current Account balance, QR payments, Soundbox, and transactions.

03

Anchor the homepage in daily merchant questions

The homepage centered on today's collection and settlement balance because merchants primarily ask: how much did I collect, where is my money, and has it settled?

04

Design for small-merchant ease of use

Most merchants were from tier-3 and tier-4 markets, so the app had to be simple, fast, clear, vernacular-aware, and task-first.

05

Use settlement behavior to cross-sell Current Account

If a merchant was settling into another bank account, there was a time lag and a weaker Airtel Payments Bank relationship. Current Account settlement made the value proposition stronger.

06

Solve the Soundbox app-adoption gap

Soundbox confirmed payments aloud, so merchants had less reason to open the app. The app needed useful reasons beyond payment alerts.

07

Add AI Insights as a reason to return

AI Insights was designed to help merchants understand business performance: nearby similar-store comparison, ARPU comparison, best-performing day, and local rank/percentile.

Future monetization was explored as a merchant intelligence subscription, potentially around ₹10/month.

Before / after model
Before
  1. Merchant accepts payment
  2. Checks payment in old merchant app
  3. Settlement may go to another bank
  4. Current account lives separately
  5. Soundbox reduces need to open app
  6. Cross-sell and lending hard to discover
After
  1. Merchant opens Business App
  2. Sees today's collection and settlement balance
  3. Manages QR / Soundbox / transactions
  4. Sees Current Account as business anchor
  5. Links settlement to APB Current Account
  6. Discovers lending and growth opportunities
Research & market learning

Built from market visits, not assumptions.

The strategy came from market visits, merchant interviews, prototype testing, field observation, task completion on the old app, and competitive benchmarking.

Research showed two important things.

First, the old experience was too slow and difficult for daily merchant tasks.

Second, Soundbox reduced app habit because merchants already heard payment confirmations from the device. To make the app valuable, it had to help merchants grow their business, not only check payments.

Design principle

Ease of use for small merchants.

Language / vernacular

The experience considered major Indian languages such as Hindi, Bengali, Tamil, Punjabi, English, and others. Voice and sound cues were planned for future accessibility, but not shipped yet.

UI evidence

Airtel Payments Bank for Business

The merchant and business banking journey.

Metrics being tracked
Primary metrics
  • Current Account cross-sell
  • Soundbox adoption
  • Settlement account linkage
  • Loan eligibility / lending funnel
  • Business App adoption

The app has shipped recently, so actual post-launch performance metrics are still being measured.

My role

As Head of Product Design, I helped frame Airtel Payments Bank for Business as a combined merchant-banking experience.

The insight came from market visits: merchants were already connecting merchant payments and current-account settlement in practice, but the product experience was fragmented.

  • Identifying the disjointed merchant / current-account experience
  • Framing Current Account as the anchor for the business app
  • Shaping the combined merchant + business banking experience
  • Identifying the Soundbox app-adoption problem
  • Helping reposition the app from payment acceptance to business growth
  • Conceptualizing AI Insights as a reason for merchants to return
  • Aligning product, business, lending, analytics, operations, compliance, design, and engineering
Lessons
01

A merchant app should not only show payments. It should help run the business.

02

A convenience product can weaken app habit. Soundbox solved payment confirmation, but reduced reasons to open the app.

03

Current Account can become a moat when settlement, merchant acceptance, and lending are connected.

04

Small merchants need speed and clarity before sophistication.

05

Growth features work better when they are useful, not just visible.

Related