RBI Cyber Rules for Payment Apps: 6-Hour Reporting, 12-Hour Cooling

The Reserve Bank of India has tightened cyber security rules for the non-bank companies that run much of India’s digital payment system, from NPCI and card networks to wallet issuers and payment aggregators. Under new Master Directions dated November 5, 2026, these firms must report any cyber attack, major outage or unusual incident to the RBI within six hours of detecting it. The rules also include a 12-hour cooling period for online payments after a customer changes the mobile number or email linked to a payment instrument, a step aimed squarely at account takeover fraud.
The full name of the document is the Reserve Bank of India (Cyber Resilience and Digital Payment Security Controls for non-bank PSOs) Master Directions, 2026. It was issued under the Payment and Settlement Systems Act, 2007, and replaces the earlier set of directions from July 30, 2024 along with several older circulars.
Who Has to Follow the New Directions
The rules apply to authorised non-bank payment system operators (PSOs), split into three groups:
| Category | Who is in it | When the rules apply |
|---|---|---|
| Large | CCIL, NPCI, NPCI Bharat BillPay, card networks, non-bank ATM networks, white label ATM operators, large PPI (wallet) issuers, TReDS platforms, bill payment operating units, payment aggregators | From the date of publication on the RBI website |
| Medium | Inbound cross-border money transfer operators, medium PPI issuers | From the date of publication |
| Small | Small PPI issuers, instant money transfer operators | April 1, 2028 |
A wallet issuer that grows into a bigger category gets one year to meet the stricter rules. Banks are not covered by this document, which is written only for non-bank operators.
The Six-Hour Clock and Other Duties for Payment Firms
The headline change is speed. An “unusual incident”, which covers cyber attacks, critical system outages, internal fraud and settlement delays, must reach the RBI in a set format within six hours of detection. Cyber incidents must also be reported separately to CERT-In, the national cyber security agency. Ravi Prakash of Apollo Infowaves told ETV Bharat the rule shows security “can no longer remain a reactive compliance function.”
Other back end requirements include:
- Disaster recovery: backup sites must be in a different seismic zone from the main data centre, with recovery drills at least twice a year.
- Audits: an annual system audit, with the report filed within two months of the financial year end (by June 1 for firms on an April to March year). Problems found must be fixed within three months.
- Logs: audit logs kept for at least five years.
- Vendors: critical third party software must have its source code held by the firm or kept in escrow, and vendors must meet set security standards. Srinivas L of 63SATS Cybertech called the source code rule the most significant change.
- Testing: security testing and audits of cloud providers at least once a year.
What Changes for You as a Wallet, Card or App User
Most of the rules work behind the scenes, but several will show up on your phone. Here is a plain reading of the customer facing controls:
- 12-hour wait after changing your number or email. If the mobile number or email linked to your wallet or card is changed, online payments stay blocked for at least 12 hours. This is meant to stop fraudsters who take over an account by swapping the contact details. If you change your number yourself, plan big payments around this window.
- Apps tied to your phone and SIM. Mobile payment apps must be bound to your device and SIM, and you will be asked to re-bind after a period of not using the app. Moving your SIM to a new phone may therefore mean verifying the app again.
- Clearer alerts. Alerts must hide your full account details, show the actual merchant name rather than a payment gateway’s name, and put any OTP at the end of the message. Fund transfer alerts must show the beneficiary and amount.
- Report fraud inside the app. Every operator must let you flag a fraudulent transaction through its app or website.
- Auto logout and lockouts. Idle sessions end automatically, and access locks after a set number of wrong attempts, with a notification to you.
- Wallet loading checks. PPI issuers can apply a cooling period on transfers and cash withdrawals right after money is loaded into a wallet.
Card networks will also have to set transaction limits at card, card range (BIN) and issuer level, and run alerts for issuers round the clock. For context on how UPI grew to dominate everyday payments, see our report on demonetisation, 10 years on.
If Money Is Taken From Your Account: Steps to Follow
The six-hour rule is a duty on companies. It does not set a deadline for customers or promise a refund. Your own speed still matters most, because a quick complaint improves the chance of freezing the money. Police cyber cells advise these steps:
- Call 1930 at once, the national cyber crime helpline.
- File a complaint on the National Cyber Crime Reporting Portal and upload proof such as screenshots, transaction IDs and phone numbers.
- Contact your bank or wallet to dispute the transaction, block UPI, and ask for the receiving account to be frozen. Use the in-app fraud reporting option now required by the RBI.
- Keep all evidence: SMS alerts, WhatsApp or Telegram chats and bank messages.
- Ignore “refund” calls. Do not pay again and block anyone who offers recovery for a fee.
Why the RBI Is Moving Now
Operators such as NPCI, card networks and big wallet firms sit at the centre of everyday payments, so an outage or breach at one of them can affect many users at once. By forcing early reporting and stricter vendor and recovery rules, the central bank wants to spot attacks faster and limit the damage. Large players have to comply right away, while smaller wallet firms get until April 2028. The official circular, numbered RBI/DPSS/2026-27/475, is available on the Reserve Bank of India website.
This article is general information and not financial or legal advice.



