Why UPI 123PAY was introduced
Many people use basic or feature phones rather than a smartphone payment app. UPI 123PAY extends ways to initiate UPI payments for this audience.
The Reserve Bank of India’s launch announcement described app-based, missed-call, interactive voice-response and sound-based approaches. That announcement explains the original design; it should not be read as a list of features available on every phone today.
The practical question is which supported service the customer can actually use. Begin there rather than giving one set of steps as though all implementations were identical.
Different methods can serve the same purpose
An interactive voice-response service uses an automated call flow. Other implementations can use a feature-phone application or another supported mechanism. Their enrolment screens, supported functions and device requirements can differ.
For a current provider example, PhonePe’s August 2026 announcement describes a feature-phone service using an SMS-based architecture on supported devices. The provider’s specific implementation does not establish compatibility with every handset or another provider’s process.
This is why a glossary explanation is more durable than a copied list of button presses. Use the provider’s current official instructions when setting up a particular phone.
What “without internet” does and does not mean
In the supported context, the user may make a payment without a smartphone internet connection. That does not mean the phone requires no connectivity of any kind or that the banking service operates without its own systems.
Check the actual method’s requirements. A voice-based interaction, an SMS-based implementation and a smartphone app should not be described as the same channel.
Nor does the phrase remove authentication. The customer must complete the applicable bank and provider process. Never tell someone that a basic phone allows unrestricted access to an account or makes a private payment credential unnecessary in every situation.
Helping a customer use the correct service
First identify the provider, phone and bank involved. Obtain setup information from the provider’s official website or bank channel rather than an unsolicited caller or forwarded message.
The customer should control their own authentication. A helper can explain the instructions without collecting the customer’s PIN or taking over an unfamiliar call that asks for sensitive information.
Before treating a merchant payment as complete, check the receiving-side transaction record. A customer starting a call or pressing a confirmation button is not, by itself, evidence that the merchant has received the payment.
An example at a small shop
Illustrative example: A customer with a supported feature phone asks whether they can pay digitally. The retailer should establish which payment method the customer has already set up and which receiving method the shop accepts.
The customer then follows that provider’s instructions and checks the recipient and amount. The retailer checks the actual payment result before recording the sale as paid.
If the customer wants to pay a utility bill, keep the payment method separate from the bill-payment service. BBPS explains a bill-payment ecosystem; UPI 123PAY describes ways the customer may access UPI. One name does not automatically establish the other service’s availability.
Questions about UPI 123PAY
Does every feature phone support every method?
No. Check the provider’s supported device and service requirements.
Is UPI 123PAY the same as UPI Lite?
No. They describe different access or payment arrangements. Do not transfer one product’s balance, limits or authentication behaviour to the other.
Can a retailer activate it for anyone without bank checks?
No. The applicable bank and provider enrolment process still applies. An explanation at a counter does not replace it.