How Rapido®Pay intercepts malicious QR codes, detects social engineering phishing attempts, and safeguards users before payment PIN authentication.
With over 14 billion monthly UPI transactions in India, malicious actors frequently deploy deceptive QR stickers in retail stores or send phishing QRs over messaging channels. Common attack vectors include:
@sbi-reward-claim instead of legitimate @sbi).| Evaluation Layer | Inspection Criteria | Risk Impact |
|---|---|---|
| 1. Protocol Validation | Verifies raw URI begins with valid upi://pay and adheres to NPCI specification standards. |
Fails invalid/malformed non-UPI URLs instantly. |
| 2. Handle & Domain Verification | Extracts the acquiring banking PSP handle (e.g., @bankhandle, @corporatebank, @retailpsp) against a certified registry of RBI-authorized banking handles. |
Flags unregistered or spoofed banking handles. |
| 3. Lexical Threat Heuristics | Scans payee name (pn), notes (tn), and VPA for social engineering keywords: lottery, prize, gift, refund, bonus, helpdesk. |
Assigns high threat penalty (+40 to +60 score). |
| 4. MCC & Merchant Cross-Match | Inspects Merchant Category Code (mc). If a merchant claims to be a supermarket (5411) but provides a personal P2P handle, a discrepancy is raised. |
Warns user of retail QR tampering. |
| 5. Amount Anomalies | Flags unexpected fixed amounts or zero-balance authorizations without valid invoice references (tr). |
Prompts user confirmation before intent hand-off. |
Rapido®Pay adheres strictly to a zero-custodial architecture: