RBI Penalty Report – 13th November 2026

Entity Profile: One Mobikwik Systems Limited

1. Key Details of the Enforcement Action

Regulated Entity One Mobikwik Systems Limited
Penalty Amount ₹9.00 Lakh (Rupees Nine Lakh Only)
Order & Press Release Dates Order dated November 06, 2026; Published November 13, 2026 (PR: 2026-2027/1496)
Statutory Powers Invoked Section 30(1) read with Section 26(6) of the Payment and Settlement Systems (PSS) Act, 2007
Inspection Reference Period June 2025 to March 2026
Regulatory Directions Violated RBI Master Directions on ‘Prepaid Payment Instruments (PPIs)’ and ‘Fraud Reporting’
Sustained Charges
  1. Allowing fund transfers by certain PPI holders to non-pre-registered beneficiaries beyond the prescribed regulatory cap.
  2. Failing to report certain fraud incidents to the RBI within the prescribed statutory timeline.

Note: The RBI clarified that this action is strictly based on deficiencies in regulatory compliance and does not pronounce upon the validity of any transaction or agreement entered into by the company with its customers.

2. Root Cause Analysis (RCA)

Based on the sustained supervisory findings during the June 2025 – March 2026 inspection cycle, the compliance failures stem from two primary operational and technical breakdowns:

  • Inadequate Core Transaction Limit Rules Engine (PPI Transfers): Under RBI PPI guidelines, strict monthly/per-transaction limits apply to fund transfers made to beneficiaries who have not been pre-registered by the wallet holder (typically capped lower than pre-registered beneficiaries to mitigate unauthorized wallet draining). The company’s payment switch or velocity-check logic failed to distinguish between registered and non-pre-registered beneficiary states—or failed to aggregate cumulative transfers across sessions—allowing transactions to breach the ceiling.
  • Fragmented Fraud Detection-to-Reporting Workflow: Delays in statutory fraud reporting typically arise when internal risk/chargeback teams investigate customer disputes in silos without automated triggers feeding into the regulatory compliance desk. Manual triage bottlenecks, unclear internal escalation SLAs, or misclassifying cyber/payment frauds as routine customer disputes directly result in missing RBI’s strict reporting windows.
  • Gaps in Pre-Inspection Compliance Testing: Internal audit and second-line compliance assurance functions did not run targeted edge-case parameter testing on beneficiary registration workflows and regulatory reporting turnaround times (TAT) prior to the statutory inspection.

3. Recommended Preventive Controls

To remediate these deficiencies and prevent recurrence, the following technical and governance controls should be institutionalized:

Control Domain Specific Preventive Mechanism Control Type
Beneficiary Validation & Velocity Caps Hard-code API-level transaction limits tied to beneficiary status flags (is_pre_registered = false). Enforce real-time cumulative velocity counters at both the wallet ID and device/PAN level that automatically reject transactions exceeding prescribed RBI caps. Automated Preventive (System Hard-Stop)
Cooling-Off & Step-Up Authentication Implement mandatory cooling-off periods upon adding new beneficiaries alongside multi-factor authentication (MFA) before unlocking higher transfer tiers. Automated Preventive (Access & Limit Control)
Automated Fraud Reporting SLA Tracker Integrate the Fraud Risk Management (FRM) case tool with the compliance portal. Configure automated countdown alerts (e.g., at 50% and 80% of the statutory reporting window) upon fraud confirmation, auto-generating draft regulatory returns (FMR). Automated Detective & Escalation Control
Continuous Regulatory Parameter Audits Conduct monthly automated reconciliation scripts scanning 100% of outbound PPI fund transfers against beneficiary registration timestamps and auditing all closed/open fraud tickets for statutory filing timestamps. Detective Assurance Control

4. Key Lessons Learnt for Regulated Entities

  • Granular Rule Enforcement Over Broad Limit Checks: Compliance in digital payments requires enforcing conditional rules (such as beneficiary registration state), not just aggregate wallet balance or KYC tier caps. Any product UX shortcut that bypasses beneficiary pre-registration must strictly inherit the lower regulatory threshold.
  • Timeliness in Fraud Reporting is Non-Negotiable: Under the PSS Act, 2007 and RBI Master Directions, late reporting of fraud is treated as a standalone regulatory violation regardless of whether financial losses were recovered or customer liability was zeroed out.
  • Post-Facto Submissions Do Not Mitigate Technical Breaches: Even after considering written replies, additional submissions, and personal hearings, the RBI sustains penalties where objective data logs demonstrate a breach of hard regulatory limits or statutory timelines.
  • Reputational Impact Outweighs Monetary Quantum: While a ₹9.00 lakh penalty is modest relative to transaction volumes, public disclosure via an RBI Press Release impacts partner bank relationships, merchant onboarding, and investor governance ratings—making proactive RegTech automation a high-ROI priority.

RBI Press Release

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top