If a payment app is not working, first decide which of three things has failed: the app will not open, a payment did not go through, or money left your account but the other side has not received it. Each has a different fix, and mixing them up wastes time. The rule that matters most is never to retry blindly before checking your statement.
Which kind of problem do I have?
| What you see | Likely area | First action |
|---|---|---|
| App crashes or freezes | Device or app version | Close, update, restart |
| Login screen loops | Account or connection | Check network and time settings |
| Payment shows failed, no debit | Payment did not complete | Safe to retry after checking statement |
| Payment shows failed, money debited | Pending settlement | Wait, note details, contact support |
| Payment shows success, seller says no | Matching issue | Share the reference with the seller |
Should I retry a payment that failed?
Only after you have looked at your bank or card statement. A screen that says failed can still be followed by a debit that is reversed later, or in rare cases a debit that is not. Retrying immediately can mean paying twice. Open the statement, look for the amount, and wait a little if a pending line appears.
What do I do when money is debited but not received?
- Take a screenshot of the screen with the amount, date, time and any reference number.
- Check your own statement for the debit line and write down its date and amount.
- Open the app's official help page, which you reach by typing its name yourself, and look for the steps for a debited but unconfirmed payment.
- Raise the query there with the reference, and keep the ticket number.
- If the seller is waiting, tell them honestly that the status is under check, and share the reference only with them.
A worked example of recording a stuck payment
Say you pay ₹2,850 for a school uniform order and the app errors out. Your statement shows a debit of ₹2,850 at 4:12 pm. You wait a day, and a credit of ₹2,850 arrives. Net effect: 2,850 - 2,850 = ₹0. If you had retried, your records would show two debits of ₹2,850 and one credit, so you would be down ₹2,850 until the second attempt was explained. Writing each line in your notes stops confusion.
How can a tracker help?
A tracker cannot fix a payment app, but it can make a duplicate visible. SpendixAI flags possible duplicate imports and has a Possible duplicate charges report that lists the same amount to the same merchant within two days, which is useful for spotting a double debit. It works from statements you upload, so the report only covers what is in your statements.
How do I keep a payment diary for a month?
A payment diary sounds fussy, but it settles disputes quickly. For any payment above a sum you care about, write the date, the amount, the payee, the app used and what the statement later showed. After a month you can see how often an app fails and whether the pattern points to a time of day, a particular network or one bank account. That pattern is also useful evidence when you contact support, because it shows you have checked the basics.
Quick checklist
- Screenshot every failed or pending screen
- Check the statement before retrying
- Allow time for reversals before escalating, and read the app's own help page for how long
- Keep ticket numbers in one note
- Mark the transaction as pending in your own record until the credit appears
Useful ideas start with a clearer picture of your own spending.
Explore your reports

