{"id":138,"date":"2026-10-31T13:15:00","date_gmt":"2026-10-31T07:45:00","guid":{"rendered":"https:\/\/ispsquare.com\/blog\/?p=138"},"modified":"2026-10-31T13:15:00","modified_gmt":"2026-10-31T07:45:00","slug":"broadband-recharge-failed-money-deducted","status":"publish","type":"post","link":"https:\/\/ispsquare.com\/blog\/broadband-recharge-failed-money-deducted\/","title":{"rendered":"Broadband Recharge Failed but Money Deducted: What to Do"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">When a broadband recharge failed but money deducted, the safest operator action is to pause the next recharge and confirm the payment status first. This checklist helps you match the customer\u2019s bank result with the ISP account, explain the refund path, and keep a clean record.<\/p>\n\n\n\n<aside class=\"ap-card\" aria-label=\"ISP Square Starter\">\n<span class=\"ap-card__badge\">For small operators<\/span>\n<div class=\"ap-card__body\"><p class=\"ap-card__name\">ISP Square Starter<\/p><p class=\"ap-card__best\">Best for a shop reselling one ISP<\/p><ul class=\"ap-card__features\"><li>1 ISP account<\/li><li>Up to 500 customers<\/li><li>Up to 5 partners<\/li><li>2 staff logins<\/li><li>Online recharge page for customers<\/li><li>KYC and stock tracking<\/li><\/ul><\/div>\n<div class=\"ap-card__side\"><p class=\"ap-card__price\">\u20b9399\/month (\u20b93,990\/year) <small><\/small><\/p><a class=\"ap-card__btn\" href=\"https:\/\/ispsquare.com\/#pricing\">See plans \u2192<\/a><\/div>\n<\/aside>\n\n\n\n<h2 class=\"wp-block-heading\">What you need before you check<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Keep the customer and payment details together before you open a support ticket. Ask for:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>Customer name, registered mobile number, connection ID and ISP name.<\/li>\n\n\n<li>Amount, date and approximate time of the recharge attempt.<\/li>\n\n\n<li>UPI transaction ID or RRN, bank reference, and a screenshot of the status.<\/li>\n\n\n<li>The recharge page or payment gateway reference, if your system shows one.<\/li>\n\n\n<li>The customer\u2019s current ISP account status and the last successful payment.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Do not ask the customer for a UPI PIN, card PIN, password or full bank credentials. A transaction reference and status screenshot are enough to investigate the payment.<\/p>\n\n\n\n<aside class=\"ap-note\"><p>A debited payment can still be pending at the bank, payment provider or merchant side. Keep the original transaction open until you know whether the ISP account was topped up or the payment was reversed.<\/p><\/aside>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Do not recharge again<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: A second attempt can create two valid payments when the first one completes later.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Tell the customer that you are checking the first transaction.<\/li>\n\n\n<li>Put the connection ID and payment reference in your shop\u2019s ticket or register.<\/li>\n\n\n<li>Do not ask the customer to pay again while the first payment is pending or unconfirmed.<\/li>\n\n\n<li>If the customer needs urgent service, explain the status before discussing a separate payment. Record any new payment separately.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Success looks like: there is one clearly identified first transaction, and nobody has accidentally created a duplicate recharge.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: Check payment status against the ISP account<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: \u201cFailed\u201d on one screen and \u201cdebited\u201d in the bank app do not by themselves show whether the ISP received the recharge.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check the same transaction in three places:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li><strong>Customer\u2019s bank or UPI app:<\/strong> confirm whether the status is successful, pending, failed or reversed. Note the UPI reference number and the exact message.<\/li>\n\n\n<li><strong>Your payment or recharge record:<\/strong> search by amount, time, mobile number, connection ID and reference. Do not search by amount alone if several customers paid the same plan amount.<\/li>\n\n\n<li><strong>The ISP account:<\/strong> check whether the plan validity, balance or recharge history changed. Use the ISP\u2019s reference where available.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Use this working table while you investigate:<\/p>\n\n\n\n<figure class=\"wp-block-table ap-table\"><table><thead><tr><th>Bank or payment status<\/th><th>ISP account status<\/th><th>Operator action<\/th><\/tr><\/thead><tbody><tr><td>Successful<\/td><td>Recharge reflected<\/td><td>Tell the customer the recharge is complete and share the reference.<\/td><\/tr><tr><td>Successful<\/td><td>Recharge not reflected<\/td><td>Keep the payment reference, verify the correct connection and raise it with the payment provider or ISP support. Do not collect a second payment yet.<\/td><\/tr><tr><td>Pending<\/td><td>No clear recharge result<\/td><td>Wait for the final status while monitoring the original reference. Do not retry blindly.<\/td><\/tr><tr><td>Failed or declined<\/td><td>No recharge<\/td><td>Explain that the payment should follow the bank or payment provider\u2019s reversal process. Keep the reference until the customer sees the credit.<\/td><\/tr><tr><td>Reversed or refunded<\/td><td>No recharge<\/td><td>Confirm the amount and date of the credit, then start a fresh recharge only after the customer agrees.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">If you resell more than one ISP, record the ISP beside the connection ID. A single customer can have different accounts, plans and payment histories. The <a href=\"https:\/\/ispsquare.com\/blog\/onebroadband-partner-login-gtpl-together\/\">One Broadband Partner Login: Run It With GTPL<\/a> guide explains why keeping those partner accounts in one view reduces this type of mix-up.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Success looks like: you can say whether the money is only debited, whether the merchant received confirmation, and whether the ISP account changed.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Explain the refund timeline correctly<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: A customer needs a useful next action, but a broadband operator should not promise a refund deadline that belongs to a different payment flow.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a domestic UPI transaction, RBI defines <code>T<\/code> as the calendar day of the transaction. Its failed-transaction framework separates two common cases:<\/p>\n\n\n\n<figure class=\"wp-block-table ap-table\"><table><thead><tr><th>Situation<\/th><th>RBI framework<\/th><th>What it means for your ticket<\/th><\/tr><\/thead><tbody><tr><td>Account debited, but a beneficiary account was not credited in a UPI funds transfer<\/td><td>Auto-reversal by the beneficiary bank by T+1 when the beneficiary cannot be credited; compensation is specified for delay beyond T+1<\/td><td>Use this only when the payment was a funds transfer, not simply because a customer used UPI.<\/td><\/tr><tr><td>Account debited, but the merchant did not receive transaction confirmation for a UPI merchant payment<\/td><td>Auto-reversal within T+5; compensation is specified for delay beyond T+5<\/td><td>This is the closer match when a customer paid through a broadband recharge checkout but your merchant side received no confirmation.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">These are outer limits in the RBI framework. Banks and other participants are expected to resolve failed transactions sooner. The <a href=\"https:\/\/www.rbi.org.in\/Scripts\/NotificationUser.aspx?Id=11693\" target=\"_blank\" rel=\"noopener\">RBI notification on failed digital transactions<\/a> also says that compensation, where applicable, is to be credited without waiting for a separate claim.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The payment route matters. If the recharge used a card, wallet, IMPS flow or another payment method, its applicable rule may be different. Do not tell every customer \u201cUPI refund comes in one day\u201d or \u201cwait five days\u201d without checking the payment status and route.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The <a href=\"https:\/\/www.npci.org.in\/what-we-do\/upi\/faqs\" target=\"_blank\" rel=\"noopener\">NPCI UPI FAQ<\/a> says that a failed UPI payment can be refunded after the account is debited and advises the customer to contact their bank if the refund is not received within one hour. That is a good first escalation for the customer, while the RBI TAT remains the formal outer-limit reference for the relevant failed-transaction category. The customer can also use the <a href=\"https:\/\/www.npci.org.in\/register-a-complaint\" target=\"_blank\" rel=\"noopener\">NPCI complaint page<\/a> with the transaction details.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Success looks like: the customer knows which bank or payment provider to contact, and your ticket contains the applicable status and reference instead of a guess.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Tell the customer what is happening<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: Clear language prevents a second payment and gives the customer a record they can use with their bank.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Send a short message based on the actual status. For example:<\/p>\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\">\n<p class=\"wp-block-paragraph\">We have recorded your broadband recharge payment of \u20b9[amount] made on [date] at [time]. The payment reference is [reference]. We are checking whether the ISP received confirmation. Please do not pay again now. If your bank shows the payment as failed, keep the reference and contact your bank through the UPI app or bank support if the credit does not appear.<\/p>\n<\/blockquote>\n\n\n\n<p class=\"wp-block-paragraph\">Change the middle sentence when you know more:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li><strong>Successful and reflected:<\/strong> \u201cYour recharge is complete. The ISP reference is [reference].\u201d<\/li>\n\n\n<li><strong>Successful but not reflected:<\/strong> \u201cThe payment is successful on the bank side, but the ISP update is still being checked. We have opened a follow-up with reference [reference].\u201d<\/li>\n\n\n<li><strong>Pending:<\/strong> \u201cThe bank has not given a final result yet. We are monitoring the original payment. Please do not repeat it.\u201d<\/li>\n\n\n<li><strong>Failed or reversed:<\/strong> \u201cThe recharge was not completed. Please watch for the reversal against reference [reference].\u201d<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Do not write \u201crefund guaranteed today\u201d unless the bank or payment provider has confirmed the credit. Do not ask the customer to send a screenshot containing their UPI PIN, full card number or other secret information.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Success looks like: the customer has the amount, date and reference, understands whether to wait or contact the bank, and has not been told to share confidential credentials.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Handle a timed-out recharge without a blind retry<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: A timeout means your screen did not receive a final answer; it does not prove that the upstream payment or ISP action never happened.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use this sequence:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Save the original transaction ID, time, amount and connection ID.<\/li>\n\n\n<li>Refresh or reopen the transaction record using the same reference. Do not create a new recharge from a blank form.<\/li>\n\n\n<li>Check whether the customer\u2019s bank has marked the transaction successful, pending, failed or reversed.<\/li>\n\n\n<li>Check the ISP account and recharge history for the same customer and time.<\/li>\n\n\n<li>If the result is still unknown, escalate the original reference to the payment provider or ISP support. Ask for a status check, not a second debit.<\/li>\n\n\n<li>Close the case only after the recharge is reflected or the customer confirms the reversal.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">ISP Square is designed around this distinction: it provides an online recharge page, connects the operator\u2019s ISP partner account, and shows the operator the result. For a timed-out recharge, it does not blindly retry the transaction. That protects the operator from turning one uncertain payment into two attempts. The site\u2019s <a href=\"https:\/\/ispsquare.com\/#trust\">trust and payment workflow information<\/a> is useful when you are deciding how to standardise this process for staff.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Success looks like: the original transaction has one final outcome, and your ledger or ticket shows the reference, action taken and closure note.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verify and close the ticket<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Why: A recharge complaint is not finished when you send a message; it is finished when the money and service status agree.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Run this final check:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Match the amount and reference in the bank or payment record.<\/li>\n\n\n<li>Match the customer and connection ID in your operator record.<\/li>\n\n\n<li>Confirm the ISP account\u2019s plan validity, balance or recharge history.<\/li>\n\n\n<li>Record whether the outcome was completed, reversed, or escalated.<\/li>\n\n\n<li>Send the customer the final status and reference.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">For a shop with several staff members, keep the same fields for every ticket. A one-line entry such as \u201cpending, RRN saved, checked at 4:20 pm\u201d is better than a verbal promise that another staff member cannot verify. ISP Square\u2019s <a href=\"https:\/\/ispsquare.com\/blog\/isp-billing-software-india-resellers\/\">billing workflow<\/a> covers the wider value of keeping customer payments and recharge history in one place.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Troubleshooting common recharge cases<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">The customer sees \u201csuccess\u201d, but the ISP account is unchanged<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">First confirm that the successful payment belongs to the correct customer and connection. Then keep the transaction reference and raise a reconciliation request with the payment provider or ISP support. Do not mark the recharge complete only because the customer\u2019s bank shows success.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The customer sees \u201cpending\u201d for several hours<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Do not turn a pending payment into a new recharge automatically. Recheck the original reference, ask the customer to refresh the bank or UPI transaction history, and follow the bank or payment provider\u2019s escalation path if it does not move to a final state.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The bank shows \u201cfailed\u201d, but no refund is visible<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Keep the bank reference and transaction date. Ask the customer to contact the bank through the UPI app or official support channel, and compare the case with the applicable RBI TAT. The customer should not share a UPI PIN or approve a new collect request just to \u201creceive\u201d a refund.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">The same customer paid twice<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Separate the two references and check each one independently. One may be reversed while the other completed. Do not cancel, refund or adjust a payment in your own register until the bank, payment provider or ISP record confirms which transaction reached the merchant side.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Staff already started a second recharge<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Stop further attempts and label both records clearly. Check both bank statuses and both ISP records, then escalate with both references if necessary. A complete audit trail is more useful than trying to fix the register from memory.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">What should I do when a broadband recharge failed but money deducted?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Do not recharge again immediately. Save the bank or UPI reference, check the payment record and the ISP account, then classify the transaction as successful, pending, failed or reversed.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How long does a failed UPI recharge take to refund?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">It depends on the payment flow. RBI\u2019s framework gives T+1 for a failed UPI funds transfer where the beneficiary was not credited, and T+5 for a UPI merchant payment where the merchant did not receive confirmation. Check the exact status and route before giving the customer a timeline.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I recharge again if the first payment is pending?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Not as an automatic action. A pending transaction can later receive a final result, so first keep the original reference and check whether the ISP account was updated.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Who should the customer contact for a failed UPI payment?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The customer should start with the bank or UPI app used for the payment and provide the transaction reference. If the issue remains unresolved, the customer can use the official NPCI complaint route and keep your recharge ticket details.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How can an operator reduce duplicate recharge complaints?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Use one record for each payment reference, check payment status against the ISP account, and give staff a rule to pause on pending or timed-out transactions. A shared customer list, recharge history and operator workflow also make it easier to see which ISP account was actually updated.<\/p>\n\n\n\n<aside class=\"ap-cta\" aria-label=\"Keep every payment traceable\"><div class=\"ap-cta__content\"><p class=\"ap-cta__eyebrow\">Reduce duplicate recharges<\/p><p class=\"ap-cta__title\">Keep every payment traceable<\/p><p class=\"ap-cta__text\">See how ISP Square helps operators manage customer recharges and ISP accounts in one place.<\/p><\/div><a class=\"ap-cta__btn\" href=\"https:\/\/my.ispsquare.com\/get-started\">See ISP Square<\/a><\/aside>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"What should I do when a broadband recharge failed but money deducted?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Do not recharge again immediately. Save the bank or UPI reference, check the payment record and the ISP account, then classify the transaction as successful, pending, failed or reversed.\"}}, {\"@type\": \"Question\", \"name\": \"How long does a failed UPI recharge take to refund?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"It depends on the payment flow. RBI\u2019s framework gives T+1 for a failed UPI funds transfer where the beneficiary was not credited, and T+5 for a UPI merchant payment where the merchant did not receive confirmation. Check the exact status and route before giving the customer a timeline.\"}}, {\"@type\": \"Question\", \"name\": \"Can I recharge again if the first payment is pending?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Not as an automatic action. A pending transaction can later receive a final result, so first keep the original reference and check whether the ISP account was updated.\"}}, {\"@type\": \"Question\", \"name\": \"Who should the customer contact for a failed UPI payment?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"The customer should start with the bank or UPI app used for the payment and provide the transaction reference. If the issue remains unresolved, the customer can use the official NPCI complaint route and keep your recharge ticket details.\"}}, {\"@type\": \"Question\", \"name\": \"How can an operator reduce duplicate recharge complaints?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Use one record for each payment reference, check payment status against the ISP account, and give staff a rule to pause on pending or timed-out transactions. A shared customer list, recharge history and operator workflow also make it easier to see which ISP account was actually updated.\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Broadband recharge failed but money deducted? Check UPI status, avoid duplicate payments and explain the refund process with this operator checklist.","protected":false},"author":1,"featured_media":139,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_singular_sidebar":"","csco_page_header_type":"","csco_page_load_nextpost":"","footnotes":""},"categories":[13],"tags":[102,132,133,131],"class_list":["post-138","post","type-post","status-publish","format-standard","has-post-thumbnail","category-billing-recharge","tag-broadband-recharge","tag-failed-recharge","tag-operator-billing","tag-upi-payment","cs-entry"],"_links":{"self":[{"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/posts\/138","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/comments?post=138"}],"version-history":[{"count":1,"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/posts\/138\/revisions"}],"predecessor-version":[{"id":328,"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/posts\/138\/revisions\/328"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/media\/139"}],"wp:attachment":[{"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/media?parent=138"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/categories?post=138"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ispsquare.com\/blog\/wp-json\/wp\/v2\/tags?post=138"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}