Field report SE-86 / M2 · sheet /operations

Operations & RestructuringFiled from the territory

NPCI opens Android security talks with Google over UPI fraud

After 25.47 billion UPI transactions in October 2026, NPCI opened talks with Google on Android safeguards as sideloaded apps and overlay malware target UPI PINs.

Grid
SE-86 / M2
Surveyed
November 20, 2026
Reading
3 min read
Correspondent
Olivia Hart
UPI Fraud: NPCI Turns to Google to Harden Android Security
Fig. SE-86 / M2UPI Fraud: NPCI Turns to Google to Harden Android Security — FunkyFocus / pixabay

Field notes

  1. NPCI opened talks with Google on Android-level fraud controls, reported 17 November 2026.
  2. UPI processed a record 25.47 billion transactions in October 2026.
  3. RBI data showed digital payment fraud rose to 3.58 lakh cases in September.
  4. The small-value electronic-fraud compensation framework takes effect in January 2027.
  5. Server-side controls combine three checks: security-patch status, behavioural signals and revoked attestation keys.

By Olivia Hart

NPCI has opened talks with Google on operating-system-level safeguards against UPI fraud, according to The Economic Times on 17 November 2026. The move follows rising fraud alongside record usage: UPI processed 25.47 billion transactions in October 2026. Payment apps say a new class of attacks now targets the handset itself rather than a user’s mistake.

The immediate objective is to block sideloaded malware that silently steals UPI PINs. For payment teams, this shifts enforcement from customer awareness into Android’s installation and permission controls.

What is changing inside Android?

Customer campaigns have long focused on sharing an OTP, scanning a fake QR code or approving a deceptive collect request. Those warnings do not address weaknesses that third-party payment apps cannot see or stop, three people in the payments industry told ET.

  • Sideloaded APKs: Malicious Android packages arrive through messaging apps, fake customer-support links or spoofed update prompts, and users install them outside Google Play Store.
  • Overlay malware: Ghost Overlays and variants of the GhostBat remote-access trojan abuse Android’s “display over other apps” permission. They place an invisible layer over a genuine payment app and capture the UPI PIN as it is typed.
  • Older handsets: Google’s “restricted settings” in newer Android versions limit sideloaded apps, but many Indian users still run devices without those protections.

Payment apps say they can face large liabilities for fraud they had no way to prevent. That exposure prompted NPCI to raise the issue with Google. NPCI and Google did not respond to ET’s queries.

Vishwas Patel, chairman of the Payments Council of India, said: “This is an App world issue. Feedback has gone to Google from many in the app ecosystem and we believe that Google is doing whatever it can to minimise frauds from malicious, sideloading third-party applications on the Android operating system.”

What does the payments industry want from Google?

One payment app official said awareness alone is no longer enough. The official asked Android to restrict critical permissions—accessibility services, device admin and overlays—for apps installed outside vetted stores, backed by multi-step safeguards.

Industry members also proposed extending Google’s Play Integrity API, which payment apps already use, to detect and blacklist devices running on leaked attestation keys. The proposal would place more device screening inside Android, reducing the burden on payment apps to identify sideloaded threats.

How can banks and fintechs close the gap?

Narasimhan Elangovan, who heads cyber security and data privacy at Ascentium India, said strengthening Android is only part of the answer. “The objective should be to make a compromised phone insufficient, by itself, to defeat the wider payment system,” he said.

Banks and fintechs should verify device integrity on their own servers before allowing sensitive actions. They should combine security-patch status with behavioural signals, with failing devices facing transaction limits or extra verification. A compromised device should not necessarily lose all access, because the proposed control reduces risk without shutting out the customer.

In operating terms, this is a two-gate model: Android screens the handset, then the bank server checks it again. The server-side test would reject phones below a minimum security-patch level and check every device attestation against Google’s list of revoked keys.

Why the fraud response matters for Indian banks

RBI data showed digital payment frauds rose to 3.58 lakh cases in September. The regulator’s compensation framework for small-value electronic fraud takes effect in January 2027, prompting banks to seek a central claims system.

RBI has also tightened incident reporting through its cyber resilience rules for non-bank payment system operators. For lenders, neither Android hardening nor customer education can carry the fraud response alone.

Google’s device controls, paired with bank-side integrity checks, could close a gap that customer education cannot. That combination changes the control point: Android blocks or flags risky devices, while financial institutions retain final checks before sensitive actions.

via bfsi.eletsonline.com (Source)

Share this article:

More from Olivia Hart

Olivia Hart

Show full bio

News editor covering regulation, policy and their impact on corporate strategy and chief-executive leadership at CEO Frontier.

510 articles

Filed under

Adjacent sheets

« Previous articleNext article »

End of sheetSE-86 / M2 · November 20, 2026