India’s central bank is considering a technical change to how certain digital transfers are processed—adding a deliberate time lag as a fraud-mitigation control. According to Inc42 Media, the Reserve Bank of India (RBI) is discussing measures in a discussion paper titled “Exploring safeguards in digital payments to curb frauds”, with feedback open until May 8. The proposal includes a 1-hour delay for processing digital transactions of ₹10,000 or more and a 24-hour delay for citizens aged 70 years and above for transactions of ₹50,000 and above.
A core proposal: slowing down certain APP transfers
The RBI’s focus is on authorised push payments (APP)—a payment category where the payer authorizes the transfer to a payee. In its discussion paper, the RBI argues that a time lag could act as a preventive control by disrupting the fraudster’s psychological influence over the victim and by giving the payer an opportunity to reconsider the transaction, as described by Inc42 Media.
Under the proposal, users would experience a 1-hour lag for transactions exceeding ₹10,000. Inc42 Media reports that the delay would be implemented on all merchant transactions made from UPI, cards, and net banking.
Notably, the proposal is not described as a blanket delay for every kind of payment. Inc42 Media says the RBI has proposed exemptions for recurring payments like e-mandates and for payments made via cheques. That carve-out suggests the RBI is trying to balance fraud prevention with continuity for payment flows that may not be easily paused without breaking user expectations.
How the mechanism could work: overrides and whitelisting
Inc42 Media also reports that the RBI is considering an option to handle time-sensitive transactions. Specifically, the RBI may provide a way for the payer to override the lag for a specific transaction by explicitly authorizing it—for example, through a whitelisting mechanism. In such cases, the delay may be bypassed, according to the reporting.
The proposed control could also be structured around payees rather than individual transactions. Inc42 Media states that instead of allowing whitelisting of transactions or in addition to it, payees can be whitelisted by the payer. Under that approach, all payments to whitelisted payees would not be subjected to time lag.
From a technology standpoint, these details matter because they imply the fraud-mitigation logic would need to integrate with existing payment rails—UPI, cards, and net banking—while also supporting payer-controlled configuration (whitelists) and per-transaction override flows. Even without implementation specifics in the source, the described design points to a system that can classify payments (merchant vs. recurring vs. exempted), apply timing rules, and consult payer preferences before enforcing the delay.
Targeted protection for older users and larger amounts
The RBI’s discussion paper also includes a demographic and threshold-based safeguard. Inc42 Media reports that for APP transactions worth ₹50,000 and above, the central bank suggests a 24-hour delay for citizens aged 70 years and above.
While the source excerpt cuts off before fully describing the complete details for this higher tier, the reported structure indicates a layered approach: a shorter delay for transactions above ₹10,000 in general, and a longer delay for older users above a higher threshold. This kind of tiering is a common pattern in risk controls—applying stronger friction where the expected downside (for example, harm from fraud) is higher, while keeping lower-friction controls for less risky scenarios. Here, the RBI’s stated rationale—disrupting psychological pressure and providing reconsideration time—aligns with that tiering logic.
Why this matters for digital payments technology
The RBI’s proposal is essentially a time-based safeguard layered onto existing digital payment channels. As Inc42 Media notes, the backdrop is an ongoing increase in digital financial theft. In that environment, the RBI appears to be exploring whether adding processing delay can reduce successful APP fraud outcomes without requiring changes that would stop payments entirely.
There are several technology implications that observers may watch for if the RBI moves from discussion to implementation:
1) Payment orchestration changes across rails. Because the delay is described as applying to merchant transactions across UPI, cards, and net banking, the safeguard would need consistent enforcement logic across systems that may differ in how they authorize, confirm, and settle payments.
2) Risk controls that depend on payment type. The proposed exemption for recurring e-mandates and cheques implies the system would classify payment categories and selectively apply delays.
3) A new user-controlled trust layer. The whitelisting and override mechanisms imply a configuration model where payers can pre-authorize certain transactions or payees. That adds a new dimension to payment UX and state management: the system would need to reliably maintain and apply whitelist status at time of authorization.
4) Operational trade-offs around time-sensitive flows. Inc42 Media explicitly mentions that some transactions may be time-sensitive and therefore may need an override path. Implementing that without undermining the fraud-mitigation goal would likely require careful rules for what can be overridden and how that authorization is performed.
Finally, the RBI’s discussion paper process—feedback open until May 8—signals that these design choices are still under review. The source frames the proposal as part of a broader set of measures, but the excerpt focuses on the time lag, exemptions, and whitelisting concepts. As the consultation progresses, the industry may look for additional technical details on enforcement, edge cases, and how the delay interacts with existing payment confirmation and user authorization steps.
Source: Inc42 Media