To collect broadband payment UPI transactions without mix-ups, give every payment a clear customer reference before you mark a recharge as paid. A simple counter process works for cash and UPI, while an online recharge page can remove the manual matching step for customers who pay themselves.
The “who paid ₹500?” problem
UPI makes it easy for a customer to pay from a phone. The problem starts when several customers pay the same amount to one shop QR code or to the operator’s phone number. A bank notification may show an amount and a payer, but your first question is still: which connection should receive the recharge?
This becomes harder when you run more than one ISP, have staff at the counter, or take payments while handling new connections and complaints. A payment is not fully recorded until you can connect four things:
- The customer or connection.
- The amount and plan.
- The UPI transaction reference.
- The recharge status.
Do not use a screenshot as the only record. It can help during a busy counter interaction, but the transaction reference and your own customer record are what make the payment easy to find later.
What you need before collecting UPI
Keep this process ready before you put a QR code on the counter:
- A single business UPI QR or UPI ID that your team is authorised to use.
- A customer list with the connection ID, name, mobile number and ISP.
- The current plan or recharge amount.
- A small payment register, spreadsheet or billing panel with a separate status field.
- A rule that staff record the customer reference and UPI transaction ID before closing the counter entry.
If you use a static QR, the customer may have to type the amount. Ask the payer to check the payee name and amount in the UPI app before entering the UPI PIN. NPCI’s UPI FAQ also says that customers can view past and pending transactions in their UPI app’s transaction history.
For safety, your staff should never ask for a customer’s UPI PIN, OTP or bank password. NPCI’s fraud-awareness guidance explains that scanning a QR code and entering a UPI PIN is for making a payment, not receiving one.
Step 1: Find the customer before taking payment
Why: the customer record is the link between the money and the internet connection.
Ask for the customer’s connection ID or registered mobile number. Search your list and confirm the customer name, ISP, current plan and amount due. If two customers have similar names, read out the last few digits of the connection or mobile number and ask the payer to confirm.
Do not start with “send ₹500 to this number”. Start with the connection. The payment amount is the second check, not the customer identifier.
If your customer uses a nickname in the mohalla, keep the formal connection ID in the record and add the nickname only as a helpful search label. This prevents staff from choosing the wrong person when two families have the same first name.
Step 2: Use one clear UPI payment instruction
Why: one standard instruction prevents staff from sending customers to different numbers or QR codes.
Show the same QR code at the counter and repeat the amount aloud. Ask the customer to follow this order:
- Scan the QR code or enter the authorised UPI ID.
- Check the payee name shown by the app.
- Enter the exact recharge amount.
- Review the amount and payee before authorising with the UPI PIN.
- Keep the success screen open until the shop confirms the payment reference.
If the UPI app provides a note or message field, you can ask the customer to enter a short connection code. Treat that as an extra clue only. Different apps and bank screens may display notes differently, so your main record should still be the customer ID and transaction reference.
For a counter payment, write or enter the customer reference before the customer scans. That way, the next staff member knows which account the payment is meant for even if the counter gets busy.
Step 3: Confirm the payment before marking it paid
Why: a payment request, screenshot or notification preview is not the same as a confirmed transaction.
Check the shop’s bank or merchant notification and open the transaction details when needed. Match the amount, time and transaction reference to the customer record. Then set the entry to UPI confirmed and continue with the recharge.
Keep these statuses separate:
| Status | What you do | What you do not do |
|---|---|---|
| UPI confirmed | Record the transaction ID and process the recharge | Do not delete the reference after recharging |
| Pending | Keep it open and check the transaction history or bank status | Do not ask the customer to pay again immediately |
| Failed or declined | Record the attempt if useful and start a fresh payment only after checking the first status | Do not treat a failed screen as a successful payment |
| Paid but recharge not completed | Keep the UPI reference attached and investigate the recharge status | Do not blindly retry a timed-out recharge |
NPCI notes that a UPI payment can show as pending and that a debit reversal may take time in some failed cases. If the customer’s account is debited but the outcome is not clear, keep the original reference, check the status and use the bank or payment-support route instead of creating a duplicate payment.
Step 4: Record the payment in one row
Why: one complete row makes a later search faster than scrolling through bank notifications.
Record the following fields immediately:
| Field | Example | Purpose |
|---|---|---|
| Date and time | 18 October, 11:20 am | Finds the payment in transaction history |
| Customer reference | Connection ID or short code | Identifies the right account |
| ISP | OneBroadband or GTPL | Sends the recharge to the correct upstream account |
| Amount | ₹500 | Catches wrong-amount entries |
| UPI transaction ID | Reference from the confirmed transaction | Proves which payment was matched |
| Recharge status | Pending, confirmed or completed | Stops an unresolved item being forgotten |
Use one row per payment. If a customer pays twice, create two rows and resolve them separately. If a staff member accepts cash for one customer and UPI for another, do not combine both into a single end-of-day total.
Step 5: Reconcile UPI payments at closing time
Why: a short daily check catches unmatched payments before the customer returns asking about an expired connection.
At the end of each shift or day:
- Filter the register for UPI payments.
- Compare each row with the bank or merchant transaction list.
- Mark confirmed payments that have a matching reference.
- Put unknown payments in an unmatched list instead of guessing the customer.
- Review pending, failed and paid-but-not-recharged entries separately.
- Check that each completed recharge has a customer and an ISP attached.
For an unmatched payment, search the transaction reference first. If you do not have it, compare the payer details, time and amount with the customers who were due that day, then call the payer for the connection ID. Do not allocate a payment only because the amount happens to match.
Keep the unmatched list small by giving customers a simple instruction: “Please tell us your connection ID before you pay, and show the UPI transaction reference after payment.” It takes a few seconds and gives your staff a repeatable record.
Let customers pay on a recharge page
Counter collection is useful when a customer visits your shop. It is less useful when you spend the day matching payments from customers who pay from home. An online recharge page puts the customer reference into the payment journey before the UPI payment is made.
With ISP Square, the customer uses a web page, so there is no app to install. The customer pays online, the ISP account is topped up, and the operator can see the payment. That removes the “whose ₹500 is this?” step for those online recharges.
The practical flow is:
- Give the customer the recharge-page link.
- The customer opens it and selects the relevant connection details.
- The customer reviews the recharge and pays online with UPI.
- You check the payment and recharge record in the operator panel.
Keep the counter process for walk-ins and customers who need help. Use the online route for customers who are comfortable paying on their own. This gives both groups a clear path without forcing every payment through your personal phone number.
If you resell more than one ISP, read the guide to running OneBroadband and GTPL from one partner login. The wider goal is one customer view, not a separate payment notebook for every upstream provider.
See every payment with the customer record
A UPI list tells you money moved. A billing record tells you what that money was for. For a broadband operator, the useful view includes the connection, plan, expiry, payment and history together.
ISP Square’s customer list is designed to show customers across connected ISP accounts in one place. That is useful when a customer says, “I paid yesterday,” but you need to check the plan, expiry and payment history before taking action. It also gives staff a shared record instead of leaving the answer inside one person’s phone.
The same principle applies to partner collections. If a partner collects from their own customers, record the customer and payment against the correct partner wallet rather than adding everything to the operator’s counter total. For a broader look at this setup, see the practical guide to ISP billing software for Indian resellers.
Plans start low — see current pricing — and choose the setup that matches your customer and partner work. If you want to see the product flow, visit the ISP Square features page.
Verify the process with a small test
Before asking every customer to use the new process, run a small test with one staff member and one customer record. Confirm that the person taking payment can find the customer, record the transaction reference, update the status and locate the entry again later.
Use this checklist:
- The QR code or UPI ID displays the expected payee name.
- The customer reference is written before payment.
- The amount is checked before the UPI PIN is entered.
- The confirmed transaction ID is attached to the correct customer.
- Pending and failed payments remain visibly different from completed ones.
- A completed recharge can be found from the customer record.
- The end-of-day list shows no unexplained UPI amount.
Once the test works, print the short instruction near the counter. Train staff to follow the same words every time. Consistency matters more than a complicated register.
Troubleshooting common UPI collection cases
Two customers paid the same amount. Search by transaction reference, time and payer details. Never assign by amount alone.
The customer shows a screenshot but you cannot find the payment. Ask for the transaction ID and check the bank or merchant transaction history. Leave the entry pending until the payment is confirmed.
The payment is pending. Do not ask for a second payment straight away. Check the customer’s transaction history and the shop’s transaction status, then follow the bank’s support process if the result stays unresolved.
The payment is confirmed but the recharge is not complete. Keep the UPI transaction ID with the recharge record. Check the recharge status and follow the ISP or billing workflow; do not blindly retry a timed-out recharge.
A customer paid to an old UPI number. Do not guess which connection the money belongs to. Record the payment details, confirm the payer and update the team’s printed and shared payment instruction so the same mistake does not repeat.
A staff member is absent. The payment must still be searchable by customer reference and transaction ID. A shared billing record is safer for continuity than a private chat or notebook kept at one counter.
FAQ
Can customers pay broadband bills by UPI?
Yes. You can accept a counter payment through an authorised UPI QR or UPI ID, or send customers to an online recharge page when your setup provides one. In both cases, confirm the amount and payment status before marking the customer paid.
How do I match a UPI payment to the right broadband customer?
Find the customer by connection ID or registered mobile number before taking payment. Then record the confirmed UPI transaction ID against that customer; do not match payments by amount alone.
What should I do if UPI money is debited but the recharge is not done?
Keep the original transaction reference and check whether the UPI status is confirmed, pending or failed. Do not make a blind second recharge; follow the bank and ISP support process if the result is not clear.
Do I need a customer’s UPI PIN to receive payment?
No. The customer enters the UPI PIN in their own app to authorise a payment. Never ask for the PIN, OTP or bank password, and be careful with QR codes or links sent by unknown people.
Can UPI replace cash collection at a broadband shop?
UPI can reduce cash handling, but the main improvement comes from attaching every payment to a customer record. Keep one process for UPI and cash, with separate payment modes and the same customer and recharge checks.
