Results for "npci"

If fingerprints consistently fail after **3–4 attempts**, do not keep forcing capture — NPCI may trigger a **biometric lock** on the customer's Aadhaar. **Recommend switching to Iris authentication:** - Device: **Mantra MIS100V2** or compatible Iris scanner - Iris authentication has a **99.2% first-attempt success rate** for elderly villagers - Works regardless of fingerprint wear from farming or construction work > Position the scanner **10–15 cm** from the customer's eyes in *indoor shaded light* (avoid direct sunlight) for best results.

Do **NOT** pay cash from your own pocket if your BC portal shows *Failed* or *Timeout*. As per NPCI circular on AePS transactions, when an amount is debited due to a communication switch timeout, an automated reconciliation cycle runs at **T+1 days**. If the acquiring bank does not confirm settlement, the amount is automatically credited back within **T+5 business days**. > Most SBI customers see auto-reversal within 48–72 hours in practice.

Yesterday around **3:30 PM**, a customer visited my CSP center for an AePS cash withdrawal of **₹10,000** from their State Bank of India (SBI) account. During transaction processing, my portal showed: > **Transaction Timeout — Switch Inoperative (Response Code 91)** But the customer immediately received an SMS confirming a debit of ₹10,000. I did **not** dispense cash because no success receipt was generated. The customer is panicking and threatening a police complaint. **My questions:** - What is the standard NPCI auto-reversal timeline? - Should I raise a chargeback ticket on my BC partner portal or ask the customer to visit their home branch?

As per **CBDT Notification No. 70/2019** and RBI guidelines, Business Correspondents (BCs) and White Label ATM operators are **100% EXEMPT** from Section 194N TDS deduction on cash withdrawals made for banking operations. Your branch is deducting TDS because they haven't flagged your current account as a **`Banking Correspondent Kiosk Pool Account`** in their Finacle / CBS software. **Documents to submit to your branch:** 1. Copy of **CBDT Notification No. 70/2019** 2. Your **BC Agent Agreement** with the bank / aggregator 3. A written request letter to the Branch Manager citing the exemption 4. Recent **NPCI / UIDAI registration certificate** as BC operator > Once the Branch Manager flags the account in CBS, TDS deductions stop immediately and previously deducted TDS can be claimed as refund in ITR.

**Error 55** during merchant 2FA occurs because NPCI matches the live biometric capture against the BC agent Aadhaar demographic database with a stricter PID block threshold (minimum **65% quality score**). Ensure you are capturing the **exact finger** (usually right thumb or index) that has the highest biometric quality score in your bank's BC registration profile. > If unsure which finger was registered, contact your BC partner's onboarding team for the enrollment record.

Since the new **NPCI 2-Factor Authentication (2FA)** merchant login rules came into effect, I frequently get: > **Error 55: Merchant Aadhaar Biometric Mismatch / Device Authentication Failed** Setup details: - Device: **Mantra MFS100** - OS: Windows 10 Due to this, my AePS terminal remains locked for the **entire day**. Has anyone found a permanent fix?

**Split transactions** means processing multiple withdrawals in quick succession for the same customer to evade limits, maximize commission, or charge unauthorized convenience fees. ## Prohibited Patterns | Example | Why It's Flagged | |---------|-----------------| | Rs.1,000 + Rs.1,000 within 5 minutes for same customer | Splitting to evade per-transaction limit | | Withdrawing Rs.510, Rs.1,020, Rs.2,020 | Non-round amounts indicate hidden fee deduction | | Adding Rs.10–Rs.20 "convenience charge" to withdrawal | Unauthorized fee charging against NPCI rules | ### How NPCI Detects This NPCI's **automated AI monitoring** flags: - Non-round transaction amounts (ending in 10, 20, 50) - Multiple transactions for the same Aadhaar within a short window Detection triggers an **instant terminal freeze alert** to the acquiring bank.

## L0 vs L1 Biometric Device Architecture | Feature | L0 (e.g. MFS100, Morpho E3) | L1 (e.g. MFS110, Morpho L1) | |---------|------------------------------|-------------------------------| | Encryption location | Host OS (Windows driver) | On-device hardware crypto chip | | Vulnerability | Memory replay / spoofing attacks possible | Cryptographic signing happens inside scanner | | NPCI AePS status | Being phased out | **Mandatory from April 2024** | ### Why L1 is more secure In **L0 devices**, fingerprint image encryption happens at the OS level, leaving a theoretical window for memory replay attacks. In **L1 devices**, the dedicated hardware cryptographic processor inside the scanner signs and encrypts data *before* it ever reaches the host computer. > All AePS applications now enforce L1 device whitelist validation at the NPCI switch level.

⚠️ **Important compliance alert for all BC agents** NPCI has issued strict warnings regarding **split transactions** in AePS. A fellow BC agent in our district had his merchant ID **permanently blocked** and an **FIR registered**. What exact transactions are classified as split transactions?

UIDAI and NPCI have mandated the **phase-out of L0 biometric scanners** and migration to L1 devices. Questions: 1. What is the technical difference between L0 and L1? 2. Is **Mantra MFS100** completely discontinued? 3. What is the current pricing for **Mantra MFS110 L1**?