Law / India

RBI Authentication Mechanisms for Digital Payment Transactions Directions, Strong Authentication

Reserve Bank of India (Authentication mechanisms for digital payment transactions) Directions, 2025, paras. 3, 4, 6, 7, 9 and 10

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 payment system providers and payment system participants, banks and non-banks, for domestic digital payment transactions (reached by declaring that you are a bank or a payment provider).
  • Authenticate every digital payment transaction with at least two distinct factors (something the user has, knows or is), unless the transaction falls under an exemption listed in Annexure 1; for a transaction other than a card present transaction, make at least one factor dynamic, so that the proof of possession is unique to that transaction (paragraph 6(a) and (b)).
  • Choose factors so that compromise of one does not affect the reliability of the other (paragraph 6(c)).
  • Offer an authentication or tokenisation service that is accessible to all the applications and token requestors in the operating environment, for every use case and channel (paragraph 7).
  • If you are an issuer, ensure the robustness and integrity of the authentication mechanism before deployment, and compensate the customer in full without demur for a loss from a transaction effected without complying with the Directions (paragraph 9).
  • If you issue cards, by put in place a mechanism to validate non-recurring cross-border card not present transactions, with your Bank Identification Numbers registered with the card networks (paragraph 10).

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

Who enforces it

Enforcement body

The Reserve Bank of India, which issues these Directions under section 18 read with section 10(2) 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

The Directions apply to all payment system providers and payment system participants, banks and non-banks alike, for domestic digital payment transactions. Paragraph 3 requires compliance by unless a provision says otherwise. Paragraph 6(a) requires every digital payment transaction to be authenticated by at least two distinct factors of authentication unless exempted.

Paragraph 6(b) requires at least one factor to be dynamically created or proven for a transaction other than a card present transaction. Paragraph 7 requires a system provider or participant to offer an authentication or tokenisation service that is accessible to all applications and token requestors in the operating environment.

Paragraph 9 requires an issuer to ensure the robustness and integrity of the authentication mechanism before deployment and to compensate the customer in full for a loss from a transaction that did not comply. Paragraph 10 requires a card issuer to put in place by a mechanism to validate non-recurring cross-border card not present transactions where an overseas merchant or acquirer raises the authentication request.

When LexLint raises it

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

Back to the example  ·  Lint your app

Page updated .