SwissPay

Design Project

SwissPay

Designing a Digital Wallet Platform for Secure Payments, Bill Payments, and Financial Operations

Digital wallets have evolved beyond peer-to-peer payments into comprehensive financial platforms. SwissPay was designed to simplify how users add money, pay bills, verify their identity, and transfer funds while giving operations teams complete visibility into settlements, reconciliation, and financial transactions.

As the lead product designer, I defined the end-to-end product experience across consumer and administrative platforms, balancing usability, regulatory compliance, fraud prevention, and operational efficiency.

Concept and product design work; not launched publicly.

“Trust is built through transparency.”

TL;DR

Problem
A wallet covering payments, BBPS bill pay, KYC, and bank payouts had to stay simple for customers while giving finance teams full visibility into settlements and reconciliation.
My role
Lead Product Designer (design project).
What I did
Designed the consumer wallet, guided KYC, a single bill-payment pattern for every BBPS service, payout status tracking, and a Super Admin dashboard for collections, settlements, and reconciliation.

Project Snapshot

Role

Lead Product Designer

Timeline

Design project

Platform

Web & Mobile

Domain

FinTech • Digital Wallet • Payments

Responsibilities

  • Product Strategy
  • FinTech UX
  • Payment Workflow Design
  • Information Architecture
  • Design System
  • Cross-functional Leadership

The Challenge

A digital wallet isn't simply a payment interface. Every transaction depends on multiple financial systems working together—payment gateways, banking networks, identity verification, bill payment infrastructure, settlement processes, and fraud controls.

The challenge was to design a platform that simplified these complex financial operations while maintaining transparency, security, and regulatory compliance for both customers and internal operations teams.

Every money movement needs a visible status—for the customer and for the operations team.

Product Strategy

SwissPay had to balance three competing priorities: user simplicity, regulatory compliance, and operational transparency. The design resolves that tension by giving each stakeholder only the complexity relevant to their role.

Design Principles

These principles kept SwissPay trustworthy for consumers and operable for finance teams.

01. Financial products should reduce uncertainty, not increase it.

02. Compliance should feel guided rather than restrictive.

03. Every financial transaction should communicate its status clearly.

04. Admin tools carry the operational depth so the consumer wallet can stay simple.

05. Trust is built through transparency.

Key Challenges

Regulatory Compliance

Designing financial workflows that satisfy KYC requirements without unnecessary friction

Multi-Provider Integration

Unifying payment gateways, BBPS, payouts, and identity verification APIs

Operational Transparency

Giving finance teams real-time visibility into collections, settlements, and balances

Trust & Security

Building confidence throughout payment, withdrawal, and verification journeys

Scalability

Supporting growth from early-stage operations to high-volume financial processing

Building for Scale

The platform was designed to support rapid business growth without redesigning core financial workflows.

Reusable foundations in the design:

  • •

    Modular payment architecture

  • •

    Reusable transaction workflows

  • •

    Unified bill payment patterns

  • •

    Multi-bank reconciliation dashboards

  • •

    Configurable administrative controls

  • •

    Extensible design system

Super Admin platform for financial operations
Consumer wallet across payments and payouts

The experience was designed to evolve from early-stage transaction volumes to enterprise-scale financial operations while maintaining consistency across the product.

Key Design Decisions

Rather than exposing financial plumbing, we shaped SwissPay around clear money moments—add funds, verify identity, pay bills, withdraw, and monitor operations.

Product Principle

Each stakeholder sees only the complexity relevant to their role.

Decision

Instant wallet credit after successful payment.

Why

Users expect immediate confirmation after adding money. Delayed balances reduce trust and increase support requests.

Outcome

Designed immediate feedback and explicit transaction states for every top-up.

Instant credit and transparent wallet states

Decision

Guided KYC instead of document-heavy onboarding.

Why

Identity verification is mandatory, but financial onboarding should remain approachable.

Outcome

A step-by-step flow covering Aadhaar, PAN, and bank verification.

Decision

Unified bill payment experience across multiple services.

Why

Users shouldn't experience different interfaces for electricity, gas, FASTag, mobile recharge, or loan EMI payments.

Outcome

One reusable payment pattern defined for all BBPS services.

Decision

Operations dashboard centered around financial visibility.

Why

Operations teams require real-time awareness of collections, settlements, payouts, reconciliation, and bank balances.

Outcome

Collections, settlements, payouts, and bank balances consolidated into one monitoring view.

Centralized collections, settlements, and reconciliation

Decision

Transparent payout workflow.

Why

Users need confidence when transferring wallet balances to their bank accounts.

Outcome

Payout status states designed for both IMPS and NEFT timing.

Simplifying the wallet for consumers and concentrating operational depth in admin tools kept the design approachable without giving up financial control.

Trade-offs & Constraints

Trade-off

Rather than exposing advanced financial controls to every user, we intentionally simplified the wallet experience while moving operational complexity into the administrative platform.

This gives up direct user configurability in exchange for a clearer, safer wallet with fewer ways to make costly mistakes.

Trade-off

Rather than designing provider-specific bill payment flows, we invested first in a unified BBPS pattern.

This defers some service-specific customization, but gives electricity, gas, FASTag, recharge, and EMI one reusable payment pattern.

Constraints

  • KYC and regulatory compliance requirements

  • Multi-provider payment gateway complexity

  • BBPS service fragmentation

  • IMPS and NEFT payout timing differences

  • Fraud prevention and settlement accuracy

  • Web and mobile continuity

Systems Thinking

SwissPay connected consumer money moments to operational financial systems through a predictable lifecycle.

  1. Add Money
  2. Verify
  3. Pay / Transfer
  4. Settle
  5. Reconcile

What Changed

Before

Separate financial services with disconnected experiences.

After

The design connects payments, bill payments, verification, and payouts through one consistent wallet experience.

Before

Operations teams relied on fragmented financial information.

After

The Super Admin design centralizes collections, settlements, reconciliation, and banking operations in one view.

My Role

I led the end-to-end product experience across the consumer wallet, administrative platform, and operational workflows.

My work focused on simplifying financial interactions while aligning closely with engineering, payment partners, and business stakeholders.

Key responsibilities included:

  • •

    Defining wallet architecture

  • •

    Designing payment and payout journeys

  • •

    Structuring KYC onboarding

  • •

    Building Super Admin dashboards

  • •

    Creating reusable design system components

  • •

    Leading cross-functional product direction

Design Outcomes

Product

  • •

    Wallet, payments, bill payments, payouts, and KYC designed as one connected system

  • •

    Architecture designed to support multiple payment providers and banking integrations

User Experience

  • •

    Guided flows for top-up, KYC, bill payment, and payout

  • •

    Explicit status states for every transaction and payout

Leadership

  • •

    Defined the end-to-end product experience across consumer and administrative platforms

  • •

    Reusable UX patterns documented for future financial capabilities

Mobile wallet experience across payments and transfers

Future Opportunities

  • •

    Expanded financial services layered onto the existing wallet foundation

  • •

    Richer fraud and dispute workflows with clearer consumer communication

  • •

    Deeper multi-bank reconciliation insights for high-volume operations

Reflection

Designing SwissPay reinforced that successful financial products aren't defined by the number of payment options they support—they're defined by how confidently users complete financial tasks.

Simplifying compliance, moving operational depth into admin tools, and making status visible at every step of the transaction lifecycle were the decisions that shaped the design.

Successful financial products aren't defined by payment options—they're defined by confident completion.

What I Learned

Role-appropriate complexity is the product strategy in FinTech UX.

Key Takeaways

  • 01

    Trust in financial products comes from status clarity—not feature count.

  • 02

    Compliance works best when it feels guided rather than obstructive.

  • 03

    Consumer simplicity and operational depth can coexist when each lives in the right surface.