REGULATION · BRIEFINGS

RBI Regulatory Sandbox 2025: Cohorts, Gates & Sponsor Play

On-tap facility (Apr 2025), current gates, and how to pass from proposal to production without tripping compliance.
By bataSutra Editorial · October 24, 2025
In this piece:
  • The short — who should apply and when
  • Where the sandbox stands (on-tap + cadence)
  • Live status summary (as of today)
  • Entry → Exit gates (acceptance criteria)
  • Sponsor-bank models & SLAs
  • Compliance & audit checklist
  • FAQ (timelines, data, customer protection)

The short

  • Status: Theme-neutral, on-tap window is open (since Apr 2025). Expect 6–9 months end-to-end for most pilots.
  • Fit: Tests needing real customers under tight guardrails—UPI offline edges, underwriting with capped limits, RegTech controls.
  • Tripwires: Auto-pause if complaints > 0.3% of sample or NCL > guardrail; deletion proof mandatory at exit.
  • Bank capacity: Sponsor SLAs (onboarding/day caps, dispute TAT) are the bottleneck—lock these before Gate-2.
  • Production: Graduation permits only the tested scope; any expansion is a new approval conversation.

Where the sandbox stands (structure & cadence)

LayerWhat it coversWhat RBI expectsCommon failure
ScreeningEligibility, novelty, consumer benefitProblem clarity; measurable benefit; risk controlsGeneric claims; weak harm mitigation
Test designCohort size, KPIs, stop-lossKPI math (default %, TAT); rollback definedVague KPIs; no rollback
ExecutionLive customers under capsConsent, dispute TAT, real-time logsShadow ops; sponsor delays
EvaluationOutcome vs plan; auditComplete logs; deletion certificatePartial logs/deletion
GraduationScope + safeguardsBounded scope; supervision notesAssuming licence equivalence

Live status summary (today)

PillarCurrent stateWhy it mattersWhat to do this week
WindowOn-tap, theme-neutral window openApply when sponsor capacity is realSecure LOI with hard SLA dates
Recent cohortsPrior Cohort-5 entities remain reference pointsSet KPI baselines realisticallyHarvest benchmarks for your plan
DocsRetail loan reset FAQ updated Oct 1 guides comms styleBorrowed for sandbox comms T&CsMirror format in your comms pack

Entry → Exit gates (acceptance criteria)

GateTo passTripwire (auto-pause)Docs
EntranceEligibility + sponsor LOI + MVD specMissing consent or harm planConcept note; risk register
Go-liveSigned SLAs; customer commsDispute TAT undefinedComms pack; SOPs; TAT matrix
Mid-testKPIs within band; logs completeComplaints > 0.3% or NCL > guardrailKPI pack; incident log
ExitKPIs achieved; deletions certifiedDeletion failure; scope creepAudit report; deletion certificate
GraduationDefined production scope + safeguardsOpen audit itemsClosure note; conditions register

Sponsor-bank models & SLAs

Models

  • Embedded sponsor: Bank runs rails; fintech supplies UX/risk.
  • Aggregator hub: Multi-bank integration with common SLA.
  • Direct-bank pilot: One bank; shortest approvals; capacity-limited.

SLA guardrails

  • Daily onboarding caps; dispute TAT; fraud ops staffing.
  • Data-sharing contract: fields, purpose, retention, deletion, breach window.
  • Change management: versioning; rollback; stakeholder notice.

Compliance & audit checklist

  • MVD plan: Event schema, PII map, retention/deletion, encryption.
  • Consent artifacts: Screenshots/timestamps; withdrawal path.
  • Incident playbook: Thresholds, comms templates, regulator flow.
  • Sandbox logs: Immutable run-logs; access audits; drift notes.
  • Post-test deletion: Certificates from all (sub)processors.

FAQ

  • Is on-tap indefinite? It’s open, but capacity and themes steer prioritisation.
  • How big can a pilot be? Start small; expand only after KPI proof within risk caps.
  • Does graduation equal blanket approval? No—only within tested scope and safeguards.