When Setu is not working, the quickest fix is to find out which of three things has stopped: your phone or network, the service you are using, or the bank at the other end. A payment that hangs, a screen that never loads and a status that never changes can all come from any of those three. we cannot see inside Setu and will not guess at its screens or policies, so this is a method that works for any payment or fintech service.
Start with the five-minute checks
- Open a website or another app that needs internet. If that is slow too, the problem is your connection, so switch between mobile data and Wi-Fi.
- Check that the app is updated and that your phone's date and time are set to automatic. A wrong clock breaks sign-in on many apps.
- Close the app fully and reopen it, rather than just switching to it.
- Restart the phone once. It sounds basic, but it clears a surprising number of stuck sessions.
- Try the same action from a browser or another device, if the service offers that. If it works there, the fault is in the app on your phone.
Is the problem on your side or theirs?
Match what you see against this table. It is a rule of thumb, not a diagnosis.
| What you see | Likely side | What to do |
|---|---|---|
| Nothing loads, other apps are slow too | Your network | Change network, wait, retry |
| Only this app fails, everything else works | The app or service | Update, reopen, check its official help page |
| Payment screen says processing for a long time | Service or bank | Do not pay again yet; check your statement first |
| Bank says debited, service says not received | Between the two | Keep the reference and contact the service with it |
| Sign-in keeps failing | Account or session | Use the service's own recovery route, never a link from a message |
What if money left my account but nothing shows as done?
This is the case that costs real money, because the instinct is to pay again. Say you pay a bill of ₹2,450 at 9:42 on the 14th and the screen stays on processing. Your bank shows ₹2,450 debited. If you pay again in panic and both go through, you have paid ₹4,900 for a ₹2,450 bill, and you are now waiting on a refund of ₹2,450.
The calmer route is to leave it for a few hours, then look at your bank statement or passbook. Three outcomes are common: the debit has reversed, the bill shows as paid after a delay, or the debit stands and the bill is still open. Only in the third case do you contact the service, with the date, time, amount and reference number in hand.
What proof should I keep?
- A screenshot of the payment screen with the date, time, amount and any reference or transaction number.
- The debit line from your bank or card statement, with the same amount and date.
- The name of the bill or account the payment was meant for.
- Every reply from support, with the date you received it.
Should I uninstall and reinstall?
Only after the simpler steps, and only after you are sure how you sign in. Reinstalling can log you out, and if you have forgotten the method you can lose access to the account page you need. Take screenshots of any pending payment before you do it.
A short list before you contact anyone
- Write down the amount, date, time and reference in one note.
- Check the bank statement, not just the app, for what actually left your account.
- Look for an existing complaint route on the service's own help page.
- Wait for the reversal window the service or your bank states in its own terms; check those terms for the exact period.
If you record a payment like this by hand in SpendixAI, or import your statement when it arrives, the Possible duplicate charges report lists the same amount to the same merchant within two days, which is exactly the pattern a double payment leaves.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

