Law / India

RBI Non-Bank Payment System Operators Cyber Resilience Master Directions, Security Controls

Reserve Bank of India (Cyber Resilience and Digital Payment Security Controls for non-bank PSOs) Master Directions 2026, paras. 4, 8, 16, 18, 19, 20, 26 and 27

In force since .

A sector security regimes rule binding private bodies.

Private right of action
No
Instrument type
a binding direction issued under an act
Obligation class
Security, Governance

What it requires

  • This binds an authorised non-bank payment system operator (reached by declaring that you are a payment provider); the Directions apply from the day they were placed on the Reserve Bank website to large and medium operators and from to small operators (paragraphs 3 and 4).
  • Formulate a Board-approved Information Security policy covering your payment applications and products, and review it annually (paragraph 8).
  • Run a Security Operations Centre that proactively and centrally monitors network and system logs and manages security incidents (paragraph 16(b)).
  • Subject all your applications to security testing, such as source code review, vulnerability assessment and penetration testing, through qualified professionals at least annually, and resolve the deficiencies in a time-bound manner (paragraph 18).
  • For a vendor involved in critical processes and activities, obtain certified assurance from an independent auditor on the vendor's cyber resilience capabilities, and put in place security controls that prevent infiltration from vendor environments (paragraph 19).
  • Put in place a data leak prevention policy covering confidentiality, integrity and availability of business and customer information in transit and at rest, including data at vendor managed facilities (paragraph 20(a)).
  • If you subscribe to cloud services, put in place a cloud operation policy, as part of your Board-approved Information Security policy, covering data localisation, protection and recoverability, and ensure the cloud service provider is audited independently at least annually (paragraph 26).

These lines are LexLint's reading of the law's text.

Who enforces it

Enforcement body

The Reserve Bank of India, which issues the Master Directions under section 10(2) read with section 18 of the Payment and Settlement Systems Act, 2007.

Settledness

As of

What this law does

Drafted with AI

Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made

Research summary

Legal information, not legal advice. This is LexLint's own research summary of a public legal source, and it creates no attorney-client relationship. For decisions that matter, consult qualified counsel in the relevant jurisdiction. About LexLint

Paragraph 4 applies the Master Directions to all authorised non-bank payment system operators. Paragraph 3 brings the Master Directions into effect on the day they are placed on the website of the Reserve Bank for large and medium non-bank operators and from for small ones. Paragraph 8 requires an operator to formulate a Board-approved Information Security policy and review it annually.

Paragraph 16 requires a Security Operations Centre that monitors network and system logs and manages security incidents. Paragraph 18 requires an operator to subject all its applications to security testing through qualified professionals at least annually. Paragraph 19 requires an operator to obtain certified assurance from an independent auditor on the cyber resilience of a vendor involved in critical processes.

Paragraph 20 requires an operator to put in place a data leak prevention policy covering data held at vendor managed facilities. Paragraph 26 requires an operator subscribing to cloud services to put in place a cloud operation policy covering data localisation, protection and recoverability.

When LexLint raises it

When your app profile says your app is a payment provider.

Back to the example  ·  Lint your app

Page updated .