Skip to main content
Redian Software
Banking solution

A digital wallet your regulator and your customers both trust

Build a regulated digital wallet — PPI / e-money, P2P, merchant QR pay, bill pay and multi-currency. Live under RBI PPI, CBK e-money, CBN, IRA-Kenya rails.

CMMI Level 3 Appraised ISO Certified 200+ enterprises 5 regional hubs 9+ years of BFSI
Outcomes our customers see

The numbers we move.

Production benchmarks from real deployments — not vendor brochures.

  • Closed + open loop

    Wallet types on one engine

    Switch behaviour by regulator and product configuration, not separate stacks

  • <2s

    P2P transaction post

    Real-time debit / credit across wallet, bank and mobile-money rails

  • 14-18 wk

    First live wallet

    From contract to first transacting customer in market

  • 8 regulators

    Pre-built reporting

    RBI PPI · CBK · CBN · BoT · BCEAO · BEAC · CBUAE · FCA

What's in the platform

Capabilities, end to end.

A complete module list — designed to remove the gaps where vendor platforms typically leave you in spreadsheets.

  • 01

    Multi-currency wallet ledger

    Tiered wallet accounts with full double-entry ledger, escrow / trust-account handling per regulator, configurable per-tier limits and a tamper-evident audit trail for every credit and debit.

  • 02

    Tiered KYC & onboarding

    Minimum-KYC for low-value wallets and full-KYC for unlimited tiers. Biometric capture, document OCR, liveness, sanctions / PEP screening, and Aadhaar / IPRS / BVN / Emirates ID integration.

  • 03

    Funding & cash-in rails

    NEFT / IMPS / UPI, M-Pesa / Airtel Money / MTN MoMo, EFT / RTGS, card top-up via tokenised PSPs, and agent cash-in through the agency banking network.

  • 04

    P2P, QR pay & virtual cards

    Wallet-to-wallet, wallet-to-bank pull-out, merchant QR pay (BharatQR / EMVCo / M-Pesa Till / Paybill), NFC at supported merchants, and tokenised virtual card issuance on RuPay / Visa / Mastercard.

  • 05

    Bill pay & VAS

    Utility, airtime, DTH, education and government bill payments through BBPS, Pesalink, NIBSS, BillDesk and IndiaIdeas. Configurable cashback, rewards and merchant offer engine.

  • 06

    Cross-border remittance

    Multi-currency wallets, FX pricing engine, corridor pricing per remittance partner, AML and sanctions on every leg, regulator reporting in receiving-country format.

  • 07

    AML, risk & regulator reporting

    Real-time screening per transaction, velocity rules per wallet tier, device binding, behavioural fraud scoring, and pre-built returns for RBI PPI / CBK / CBN / CBUAE / FCA.

Who deploys this

Built for the operating environments we know best.

We've shipped this platform across the most common patterns — find the closest fit to your operating model.

  • Banks & NBFCs

    Banks launching a wallet brand alongside their core banking estate — to capture younger customers, on-board the unbanked, or run a wage / payroll product without opening a CASA for every employee.

  • E-money issuers / PPI brands

    Standalone wallet brands running under an RBI PPI, CBK e-money, CBN, CBUAE or FCA EMR licence — often with cross-border remittance and merchant acceptance.

  • Telcos & mobile money operators

    MMOs extending mobile-money rails into savings, lending, merchant payments and cross-border — frequently with banking-as-a-service into a sponsor bank.

  • Employers & payroll wallets

    Employers issuing closed-loop wage wallets to staff for instant payroll, advances, expense disbursement and benefits — without opening individual bank accounts.

  • Retailers & transit operators

    Retailers and transit operators issuing closed-loop wallets for loyalty, gift cards, fare collection and stored-value passes.

  • Microfinance & SACCOs

    Cooperative SACCOs and microfinance institutions running wallet-based member servicing alongside the core, with M-Pesa and Airtel Money push-and-pull.

Implementation

How a rollout unfolds.

Phased, milestone-driven, with parallel-run safety nets where regulators require them.

  1. 01Weeks 1-3

    Discovery & regulator shaping

    Workshop wallet types (closed / open loop), customer segments, KYC tiers, funding and acceptance rails, regulator obligations (RBI PPI / CBK / CBN / CBUAE etc.). Output: signed solution blueprint and regulator filing plan.

  2. 02Weeks 4-9

    Configuration & build

    Configure wallet tiers, ledger, KYC tiers, funding connectors, merchant acceptance and bill aggregator integrations. Build connectors to core, mobile money, PSPs and AML per the integration register.

  3. 03Weeks 10-13

    Certification & UAT

    PSP and mobile-money operator certification, regulator sandbox sign-off, ASV/PT, and business UAT with operations, risk and compliance teams.

  4. 04Weeks 14-18

    Pilot launch

    Production cut-over for a customer cluster of 1,000-10,000, hypercare desk, daily reconciliation against core and ledger, and weekly steering with sponsors.

  5. 05Months 5-8

    Scale-out & optimisation

    Phased rollout across the full customer base, tuning of velocity rules and fraud models against live data, handover to the operator's run team with SLA-backed AMS.

Solution overview

In depth — how this platform runs.

The long-form view of capability, architecture and deployment model.

Digital wallets have moved from a payments curiosity to the primary money-holding instrument for tens of millions of customers across Africa, India and the GCC — often before they ever opened a bank account. Redian builds the regulated wallet platform that sits underneath: closed-loop, open-loop, multi-currency, telco-grade. This page is for banks launching their own wallet, e-money issuers building a standalone PPI / wallet brand, telcos extending their mobile-money rails, and retailers / employers issuing closed-loop wallets to their customers and staff.

What it does

The platform issues, funds, holds, transfers and redeems balances across wallet accounts that the operator's regulator recognises — RBI PPI in India, CBK e-money in Kenya, CBN under Nigeria's mobile-money guidelines, the Central Bank of the UAE for stored-value facilities and equivalents elsewhere. Customers onboard with eKYC, fund the wallet from a bank, card or mobile money source, send money to other wallet holders or back to a bank, pay at merchants by QR or NFC, settle bills, top up airtime and earn cashback or rewards where the operator configures them.

The platform handles both closed-loop wallets (only usable inside the operator's ecosystem — for example an employer wage wallet, a retailer gift wallet or a transit pass) and open-loop wallets (usable for any merchant payment under the wallet's regulator licence). Both run on the same engine; the regulator and product configuration decide which behaviour is enabled.

Where it fits

We deploy this for four buyer profiles:

  • Banks and NBFCs launching a wallet brand alongside their core banking estate — typically to capture younger customers, on-board the unbanked or run a payroll product without opening a CASA account for every employee.
  • E-money issuers and PPI licence-holders running a standalone wallet brand, often with cross-border remittance, multi-currency and a merchant-acceptance play.
  • Telcos and MMOs extending mobile-money rails into a richer wallet (savings, lending, merchant payments, cross-border) — often with banking-as-a-service integration into a sponsor bank.
  • Retailers, transit operators and employers issuing closed-loop wallets to customers, commuters or staff for loyalty, fare collection or wage disbursement.

The platform pairs naturally with the rest of the Redian banking stack: core banking, agency banking, digital channels, AML screening and the eKYC platform.

Core modules

Customer onboarding and KYC. Tiered KYC — minimum-KYC for low-value wallets, full-KYC for unlimited wallets — with biometric capture, document OCR, liveness checks, sanctions and PEP screening, and national-ID integration where the rails exist (Aadhaar eKYC in India, IPRS in Kenya, BVN in Nigeria, Emirates ID in UAE).

Wallet ledger and accounting. Multi-currency, multi-tier wallet accounts with full double-entry ledger, escrow / trust-account handling per regulator, configurable transaction limits per wallet tier, and a tamper-evident audit trail for every credit and debit.

Funding rails. Top-up from bank account (NEFT / IMPS / UPI in India, M-Pesa / Airtel Money / MTN MoMo across Africa, EFT / RTGS in the GCC), debit / credit card via tokenised PSP integration, agent cash-in via the agency banking network, and cross-border inward remittance.

P2P and merchant payments. Wallet-to-wallet transfers, wallet-to-bank pull-out, merchant QR pay (BharatQR, EMVCo, M-Pesa Till, M-Pesa Paybill), NFC contactless at supported merchants, virtual card issuance (RuPay, Visa, Mastercard) for use at non-wallet merchants.

Bill payments and value-added services. Utility, airtime, DTH, education and government bill payments through pre-integrated aggregators (BBPS in India, Pesalink in Kenya, NIBSS in Nigeria). Cashback, rewards and merchant offer engine.

Cross-border remittance. Multi-currency wallet accounts, FX pricing engine, corridor pricing per remittance partner, AML and sanctions screening on every cross-border leg, regulator reporting in receiving country format.

Compliance and risk. Real-time AML screening per transaction, velocity rules per wallet tier and customer segment, device binding and behavioural fraud scoring, and regulator reporting templates for RBI PPI, CBK e-money, CBN, BoT, BCEAO and CBUAE.

Regulator coverage

Reporting and audit templates are aligned to RBI PPI guidelines (India), CBK e-money regulations (Kenya), CBN mobile-money and e-money guidelines (Nigeria), BoT regulations (Tanzania), BCEAO and BEAC e-money guidelines (Francophone Africa), the Central Bank of the UAE Stored Value Facilities Regulation and the FCA Electronic Money Regulations (UK). Audit trails are immutable and timestamped, supporting both internal audit and supervisory inspections. Data residency options let operators keep PII inside the country of operation in line with each market's data protection law.

Integration with the wider stack

The wallet exposes REST and event APIs and ships with pre-built connectors for:

  • Core banking — Temenos T24, Finacle, Flexcube, Navision SACCO, Sacco Solutions, in-house cores
  • Mobile money — Safaricom Daraja, Airtel Money, MTN MoMo, Tigo Pesa, M-Pesa Tanzania
  • Card networks and PSPs — Visa, Mastercard, RuPay, AmEx; PSPs in scope per market
  • AML & KYCeKYC platform, Hyperverge, Onfido, Aadhaar eKYC, BVN, IPRS
  • Bill aggregators — BBPS, Pesalink, NIBSS, BillDesk, IndiaIdeas
  • Cross-border — major remittance partners (TransferWise, Western Union, MoneyGram, regional aggregators)

Why Redian

Wallet platforms are unforgiving — a settlement bug on the 1st of the month means employees on a wage wallet cannot draw their salary, and the operator's brand collapses overnight. Redian engineers wallet stacks with the operational rigour the regulator and the operations team both demand: paired-environment deployments, blue/green release for terminal and merchant estates, store-and-forward in low-connectivity catchments, and 24x7 NOC support across our Nairobi, Noida and Dubai hubs.

We have shipped wallet, core banking, agency and digital channel work for banks, telcos and e-money issuers across India and Sub-Saharan Africa since 2016 — see the broader BFSI practice and the Cameroon core banking rollout. Our engineers know the regulator-facing reporting (RBI, CBK, CBN, BoT, BCEAO, BEAC, CBUAE) and the local payment rails (Pesalink, NIBSS, NPCI, M-Pesa, Airtel Money) that make or break a wallet go-live.

Where you need to extend the bench, our staff augmentation and GCC models put Redian engineers alongside your in-house team under your governance.

Working with Redian

Most wallet programmes we take on are 14–18 weeks to first live wallet and 6–8 months to full rollout, depending on regulator certification, KYC partner integration and PSP / mobile-money certification timelines. We will scope yours against your existing core or telco rails, your regulator's specific wallet guidelines and the funding and acceptance rails your customers actually use.

Talk to our BFSI team about your wallet plan, or browse our BFSI case studies for comparable rollouts.

Why Redian

What makes this platform different.

Independent reasons clients pick us over incumbents and over generic global platforms.

  • Built for emerging-market wallets

    Live deployments across India and Sub-Saharan Africa with mobile-money-native funding rails, tested patterns for low-connectivity catchments and proven KYC integrations.

  • Regulator-aware by design

    Reporting templates and audit trails aligned to RBI PPI, CBK e-money, CBN mobile-money, BoT, BCEAO, BEAC, CBUAE Stored Value and FCA EMR — generated from live transactions, not retro-fitted.

  • Core, switch & MMO agnostic

    Pre-integrated with Temenos, Finacle, Flexcube, home-grown cores, plus M-Pesa Daraja, Airtel Money, MTN MoMo and major card networks — we plug into your rails, not replace them.

  • CMMI Level 3 delivery

    Appraised delivery process with traceable requirements, change control and security testing — the assurance posture wallet boards and the regulator both expect.

Tech & integrations

What the platform talks to.

Open APIs, standard integrations, configurable from day one.

  • Java
  • Spring Boot
  • Kotlin
  • TypeScript
  • Node.js
  • Python
  • PostgreSQL
  • Oracle
  • Redis
  • MongoDB
  • Kafka
  • AWS
  • Azure
  • Docker
  • Kubernetes
  • NGINX
  • M-Pesa Daraja
  • Airtel Money
  • MTN MoMo
  • NPCI UPI
  • BharatQR
  • EMVCo QR
  • Visa
  • Mastercard
  • RuPay
  • Aadhaar eKYC
  • Hyperverge
  • Onfido
  • BBPS
  • Pesalink
  • NIBSS
  • Grafana
  • Elastic Stack
Proof from production

A deployment that mirrors your use-case.

Real customer · real numbers · real go-live. Most of our work is under NDA — this is one we can share publicly.

BankingAfrica

Core Banking + Digital Channels for a Cameroon-based Bank

Client · Confidential — Cameroon

  • 9 months

    Live in production

  • 250,000+

    Active customers

  • −60%

    Cost-to-serve

Full core banking modernisation plus mobile, internet and agency banking for a Cameroon-based bank — live in 9 months, now serving 250,000+ customers.

Tech stack

JavaSpring BootPostgreSQLKafkaReactKotlinSwiftAWS
Frequently asked questions

Everything you wanted to ask before the demo.

Don't see your question? Ask us directly →

Can the platform issue both closed-loop and open-loop wallets?

Yes — both run on the same engine. The regulator licence (e.g. RBI PPI small / full, CBK e-money, CBN mobile-money) and the wallet product configuration decide which behaviour is enabled. Operators with multiple licences can issue both wallet types from one platform.

Which regulator licences does the platform cover?

RBI PPI guidelines (India), CBK e-money regulations (Kenya), CBN mobile-money and e-money guidelines (Nigeria), BoT regulations (Tanzania), BCEAO and BEAC e-money guidelines (Francophone Africa), CBUAE Stored Value Facilities Regulation (UAE) and FCA Electronic Money Regulations (UK). New licences are added per deployment.

Which funding rails are supported out of the box?

NEFT, IMPS, UPI, RuPay, M-Pesa, Airtel Money, MTN MoMo, Tigo Pesa, EFT, RTGS, plus card top-up via tokenised PSPs and agent cash-in through the agency-banking network. Cross-border inward remittance through major partners is supported with corridor-level pricing.

How does KYC work — does it support tiered limits?

Yes. Minimum-KYC for low-value wallets uses basic ID, name and mobile match with sanctions / PEP screening. Full-KYC for unlimited wallets adds biometric liveness, document OCR and national-ID integration (Aadhaar eKYC in India, IPRS in Kenya, BVN in Nigeria, Emirates ID in UAE). Velocity and balance limits apply per tier.

Can the wallet integrate with our existing core banking?

Yes. We have production integrations with Temenos T24, Finacle, Flexcube and several home-grown cores. The wallet ledger settles into the bank's GL on a configurable cycle, with three-way reconciliation between wallet, core and the national switch.

What about merchant acceptance — QR, NFC, virtual cards?

All three. The platform supports BharatQR / EMVCo QR / M-Pesa Till / Paybill QR pay, NFC at supported merchants, and tokenised virtual card issuance on RuPay, Visa and Mastercard so wallet holders can pay at any merchant that accepts those networks.

How long until our first customer is using the wallet?

14-18 weeks for a focused first launch — typically a single wallet tier on one or two funding rails — with phased rollout to full feature set and customer base over the following 4-6 months. Regulator certification timelines vary by market and are scoped during discovery.

Still figuring it out? Tell us your operating environment and we'll send a tailored architecture and pricing within one business day.

Book a demo
See it live

Ready for a tailored Digital Wallet Platform walkthrough?

Tell us your regulator, your incumbent system and the outcome — we'll send a demo plan and pricing within one business day.