Agency banking is how retail banks, MFIs and SACCOs reach customers the branch network can't economically serve — kirana stores, fuel stations, SACCO front offices, mobile money kiosks in peri-urban and rural catchments. Redian builds and operates MBranch, our Micro ATM and Remote Teller platform that turns a third-party retailer into a regulated banking touchpoint. This page is for bank COOs, heads of alternate channels and digital banking leads scaling out a CICO (cash-in / cash-out) network across India, East Africa or West Africa.
What MBranch does
MBranch functions as a full mini bank in a single hand-held device. Agents in the field serve customers across every branch service a bank actually needs at the last mile — cash withdrawal, cash deposit, funds transfer, balance enquiry, mini-statement, cheque deposit, loan repayment, loan disbursement, account opening (DD/CD), biometric registration, customer enrollment, chequebook and stop-payment requests, ATM card requests, mini-statement reprint, and agent reports — from one permissions-driven home screen. Each service is exposed to an agent only if their profile allows it.
Customers are identified through whichever rail suits the transaction — a magnetic or smart card swipe, an mPOS read, a mobile number lookup, or a customer ID. High-risk transactions and onboarding trigger a fingerprint scan on the device, so the bank — not the agent — owns the KYC trail. A thermal receipt is printed and handed to the customer on the spot, and every transaction posts in real time against the agent's float wallet and the customer's CASA account in the core banking system, with a tamper-evident audit log the regulator can inspect.
The MBranch device
MBranch runs on a 7-inch tablet form factor engineered for field use — single hand-held unit, no peripherals to carry. On board:
- Fingerprint scanner for biometric authentication (AEPS-compatible where applicable)
- Primary and secondary smart card readers, plus a magnetic card swipe for interoperability across payment cards
- Integrated thermal printer with paper cover — receipt printed and handed over on the spot
- Bluetooth, dual serial and dual USB connectivity, DC-jack power
- Charge and Bluetooth status LEDs, hardware ON/OFF slide switch
Every device is registered in a web-based Management Portal before it can transact. The record binds the device to a bank code, branch code and agent, sets which peripherals (printer, card reader, fingerprint, mPOS, PIN) are enabled, and configures the agent's transaction limits — so a device that moves outside its permitted configuration is inert.
Where it fits — the reference architecture
MBranch sits alongside Internet, Mobile, ATM, Card Management and Mobile Wallet as a branchless banking delivery channel — feeding through a Financial Switch (ISO 8583) into the core, and alongside peripheral risk modules (loan origination, AML, micro-finance, risk).
Under the hood MBranch is a four-tier system:
- Field — the MBranch device (card reader, fingerprint scanner, thermal printer) plus, optionally, an agent smartphone or tablet.
- Transport — a Mobile Server forwarding ISO 8583 messages, and an SMS adapter for one-way encrypted notifications.
- Processing — a Payment Processor that routes, authorises and responds to the device; a Security Engine that exchanges encryption keys periodically and never stores critical data; and a transactions / agents / audit database.
- Integration — a CBS Interface (SOAP mediation to core banking), a Switch Interface (ISO 8583 to a third-party or national switch), and an eKYC / AEPS SOAP service for Aadhaar-linked verification where the market supports it.
Downstream, MBranch talks to the Core Banking system, third-party switch, AEPS, government services and omni-channel back-end, and out to Payment Gateways — NPCI, Visa, MasterCard, Amex — via the switch. In low-connectivity catchments, terminal apps queue transactions offline and replay when the link returns, with duplicate-detection on the server so a re-sent transaction never double-posts.
Security and performance
MBranch is engineered for a regulated channel that can go down and no-one gets an SMS about it — every design choice starts there.
- No critical data on the device. Card CVV and PIN are never persisted on the handset.
- Short-lived keys. The Security Engine issues encryption keys bound to the device ID and session, and rotates them every 24 hours by default. The rotation interval can be calibrated tighter for high-sensitivity data.
- Encrypted SMS envelope. A one-way encrypted mobile number rides in the notification SMS so the server can validate the originator.
- Remote kill-switch. In the event of a threat or breach, the mobile application can be uninstalled from the server without physical recovery of the device.
- Secured biometric and card auth. PIN- and fingerprint-based card transactions with configurable e-authentication policies.
- Sub-5-second response. MBranch transactions complete in under 5 seconds on Wi-Fi or 3G — including biometric capture, switch call, core post and receipt print.
Where it fits — buyers we deploy for
- Tier 2/3 commercial banks in East and West Africa scaling beyond their branch footprint, typically running 500–5,000 agents and looking to add 200–400 per quarter.
- Microfinance banks and SACCOs where the agent network is the primary channel, not an alternative one. Float economics and commission tiering matter more than channel parity here.
- Business correspondent (BC) operators in India aggregating agents on behalf of one or more sponsor banks, with the regulator-mandated separation between BC technology and bank core.
Channels and core modules
Agent channels. The MBranch handheld is the flagship. In parallel, we deliver Android smartphone apps for agents using their own device with a Bluetooth biometric peripheral, USSD menus for feature-phone agents in low-bandwidth corridors, and a browser-based teller console for SACCO front offices and larger super-agents — all sharing the same transaction set, commission rules and audit trail.
Agent lifecycle. Onboarding workflow with document capture, geo-tagging of the agent outlet, due-diligence checks, and tiered activation (e.g. cash-in only → full CICO → account opening). Suspension, reactivation and termination flows with full audit.
Float and commission engine. Agent float top-up via bank transfer, super-agent reallocation or mobile money. Real-time float visibility, low-balance alerts, and commission calculation by transaction type, volume band and tier — paid out on a configurable cycle without manual reconciliation.
Settlement and reconciliation. End-of-day settlement files into the core banking ledger and the national switch. Three-way reconciliation between agent device logs, host transaction logs and core postings.
Risk and compliance. Velocity limits per agent, per customer and per transaction type. Integration with the bank's AML screening for threshold breaches, structuring patterns and watchlist hits. Geofencing so a terminal that moves outside its registered outlet triggers an alert.
Customer onboarding at the agent. Tier-1 account opening at the till with biometric KYC, instant account number issuance, and downstream sync to the core. This is often the entry point for the bank's broader lending journey.
Why Redian
Agency banking is unforgiving — a settlement bug at 8pm on a Friday means agents can't trade on Saturday morning, and the bank loses its most valuable distribution channel for 48 hours. Redian is CMMI Level 3 Appraised and ISO certified, and we engineer MBranch with the operational rigour that demands: paired-environment deployments, blue/green release for terminal estates, and 24×7 NOC support across our Nairobi, Noida and Dubai hubs.
We've shipped agency, core and digital channel work for African and South Asian banks since 2016 — see the core banking rollout for a Cameroonian bank and the broader BFSI practice. Our engineers understand the regulator-facing reporting (CBN, CBK, RBI, BoT) and the switch integrations (Interswitch, NIBSS, Pesalink, NPCI) that make or break 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 MBranch programmes we take on ship against a timeline agreed at the end of Discovery, with a phased rollout — first live agent cluster, then full rollout, depending on core integration depth and switch certification timelines. We'll scope yours against your existing core, your regulator's specific agent-banking guidelines, and the channel mix you actually need.
Talk to our BFSI team about your agent network plan, or browse our BFSI case studies for comparable rollouts.
