Digital Rupee (CBDC) vs UPI: Benefits for Merchants

Disclaimer: CBDC/Digital Rupee is currently in a phased pilot. Features and merchant acceptance may vary. Check with your bank for current availability.

With the Reserve Bank of India (RBI) actively expanding its Digital Rupee pilot program, many merchants are understandably asking: if UPI is already fast and free, why do we need a Central Bank Digital Currency (CBDC)? The two systems look similar on the surface — both let customers scan a QR code and pay — but the underlying architecture, settlement mechanics, and long-term implications are very different.

This guide explains how the Digital Rupee works technically, where the pilot currently stands, and what merchants should understand before the broader rollout progresses.

What is the Digital Rupee (CBDC)?

The Digital Rupee (officially the e₹) is a digital form of sovereign fiat currency issued directly by the Reserve Bank of India. It is not a cryptocurrency, a stablecoin, or a private payment instrument. It is the Indian rupee, represented as a cryptographic token.

The key distinction from money held in a bank account is who bears the liability. When you keep ₹500 in a savings account, that money is a liability of your commercial bank — the bank owes you ₹500. If the bank were to fail, that claim would be subject to the deposit insurance ceiling. When you hold ₹500 in a Digital Rupee wallet, those tokens are a direct liability of the RBI, the central bank. In this sense, e-Rupee tokens behave exactly like physical cash: the ₹500 note in your pocket is a liability of the RBI, not of any commercial bank.

Technically, the RBI’s retail CBDC (e₹-R) uses a two-tier distribution model. The RBI issues tokens to participating commercial banks, and those banks distribute tokens to end-users through CBDC wallet applications. The tokens themselves are stored on the user’s device (or in a bank-managed custodial wallet) as cryptographic bearer instruments.

The RBI Pilot: Phases and Participating Banks

The RBI launched its retail Digital Rupee pilot in December 2022, starting with four banks in four cities. The pilot has since expanded in stages.

Phase 1 (December 2022): State Bank of India, ICICI Bank, Yes Bank, and IDFC First Bank in Mumbai, New Delhi, Bengaluru, and Bhubaneswar.

Phase 2 expansion: The pilot extended to additional banks including Bank of Baroda, Union Bank of India, HDFC Bank, and Kotak Mahindra Bank, covering more cities across India.

Current status (2026): The pilot remains in a controlled expansion phase. The RBI is studying transaction volumes, offline functionality, interoperability with UPI infrastructure, and user behavior before committing to a full public rollout. The pace of expansion is deliberate — the RBI has emphasized that it will not rush deployment at the cost of systemic stability or user trust.

Merchants interested in accepting Digital Rupee should contact their bank directly to understand whether their branch or merchant vertical is included in the current pilot scope.

e-Rupee vs UPI: The Core Technical Differences

While the payment experience looks identical to the customer — open app, scan QR, confirm — the backend mechanics are fundamentally different.

1. What moves during a transaction

In a UPI payment, no money actually moves between devices. UPI is a messaging protocol. When a customer pays ₹500 via UPI, NPCI sends a debit instruction to the customer’s bank and a credit instruction to the merchant’s bank. The banks then update their internal ledgers. The customer’s device never holds the actual money.

In a Digital Rupee payment, cryptographic tokens move from the customer’s wallet to the merchant’s wallet. The merchant’s wallet receives bearer tokens that represent value directly, without any message passing through a bank’s core banking system. This is the digital equivalent of handing over a physical note.

2. Settlement finality

UPI transactions go through NPCI’s clearing and settlement cycle. While UPI is fast, merchant settlement typically follows a T+1 or same-day cycle depending on the payment aggregator or bank used.

Digital Rupee transactions settle instantly and finally at the moment of transfer. Once a token lands in the merchant’s wallet, the settlement is complete. There is no pending state, no chargeback risk on received tokens, and no dependency on interbank clearing.

3. Internet and infrastructure dependency

UPI requires the customer’s device to reach NPCI’s servers and both the sender’s and receiver’s bank servers to be reachable. This means UPI can fail during bank maintenance windows or network outages.

The Digital Rupee is being designed with offline capability as a core feature. Using proximity technologies such as NFC or Bluetooth Low Energy, tokens can be transferred directly between two devices without any internet connection. This is particularly significant for merchants in rural areas or markets with unreliable connectivity.

4. Programmability

One property that has no UPI equivalent is token programmability. CBDC tokens can be issued with embedded conditions — for example, government subsidy tokens that can only be spent at designated PDS stores, or corporate expense tokens restricted to approved vendor categories. As the pilot matures, this feature is expected to be used in targeted welfare distribution and enterprise expense management.

Merchant Acceptance Flow

Under the current pilot, here is how a Digital Rupee payment works at a merchant’s point of sale:

1. The merchant displays a QR code — this can be their existing UPI QR or a dedicated CBDC QR issued by their bank.
2. The customer opens their CBDC wallet application (provided by their participating bank).
3. The customer scans the QR, enters the amount (or it is pre-filled), and confirms the payment with their PIN or biometric.
4. The cryptographic tokens transfer from the customer’s wallet to the merchant’s wallet.
5. The merchant’s wallet balance updates immediately. No clearing cycle is required.

The RBI has worked to ensure interoperability: customers using CBDC wallets can pay at UPI QR codes, and the underlying routing determines which rail carries the transaction. However, interoperability behavior can vary between banks and pilot phases. Merchants should verify with their bank how CBDC receipts appear in their merchant dashboard.

Why Merchants Should Understand e-Rupee

For retail merchants and online businesses, the Digital Rupee addresses several structural limitations of the current payments ecosystem:

Zero banking downtime risk. Because e-Rupee transactions bypass commercial bank core banking servers, payments are not disrupted when a bank undergoes scheduled maintenance.

Instant, final settlement. Token receipt equals settlement. For merchants managing cash flow, this eliminates the uncertainty of pending UPI settlements.

Zero MDR. As a sovereign currency instrument, Digital Rupee transactions attract 0% Merchant Discount Rate. There is no interchange fee, no acquiring bank margin, and no scheme charge. This mirrors the MDR-zero policy already applied to UPI person-to-merchant transactions.

Potential for new use cases. As programmable token features become available, merchants in sectors like agriculture, healthcare, or government procurement may be able to receive designated subsidy payments directly in their CBDC wallet.

Preparing Your Payment Infrastructure

The most practical step for merchants today is to ensure they are working with payment software that gives them flexibility across payment rails. Because the CBDC pilot is still expanding, the merchant infrastructure you set up now should be able to handle UPI, RuPay, and eventually Digital Rupee payments without requiring a complete overhaul.

VyaparGateway provides APIs, intent links, and webhook infrastructure that connect merchants directly to payment rails. Whether a customer pays via UPI, RuPay Credit Card on UPI, or — as the pilot expands — Digital Rupee, the goal is that your merchant dashboard reflects accurate, real-time settlement data.

The broader CBDC rollout timeline remains at the RBI’s discretion and will depend on pilot learnings, regulatory readiness, and banking system preparedness. Merchants are advised to stay informed through their bank’s merchant communications and the RBI’s official announcements rather than rely on third-party timelines.

---

Disclaimer: CBDC/Digital Rupee is currently in a phased pilot. Features and merchant acceptance may vary. Check with your bank for current availability.