Compliance · India
AI over payment data, stored only in India.
RBI’s 2018 directive requires payment system providers to store the entire payment data in India. An AI system running in your Indian environment meets that without exceptions to manage.
- Since
- April 2018
- Scope
- Payment system data
- Processing abroad
- Data back in India within 24 hours
- Our approach
- AI runs in your Indian environment
In short
The Reserve Bank of India requires payment system providers to store all data relating to payment systems only in India. If data is processed abroad, it must be brought back to India within 24 hours. Running AI over payment data on infrastructure in India keeps it within the rule.
What it asks
Requirements, and how we meet them.
| Requirement | How DeepVox addresses it |
|---|---|
| Storage only in India | Index, logs and models run in your Indian data centre or private cloud. |
| Processing abroad | Not needed: inference happens in India. |
| Auditability | System audit trail available to your internal and external auditors. |
FAQ
Questions, answered.
Does this apply to all banking data?
The 2018 directive targets payment system data. Other banking data may be governed by other RBI rules; we map them in discovery.
Can we use a hosted model for some tasks?
Only for tasks that don’t involve payment data, and only if you choose it. The gateway makes that a per-agent decision.
Related
DPDP Act
The DPDP Rules phase in over 18 months.
Learn more →SEBI CSCRF
CSCRF controls are binding for SEBI-regulated entities.
Learn more →Other markets
Europe, the United States and India.
Learn more →General information, not legal advice. Have your counsel confirm how each rule applies to you. Updated October 2026.
Start with two weeks of evidence, not a sales call.
A fixed-price discovery sprint, credited against whatever comes next. Or write to sales@deepvox.ai.