Getting started

Toss not working or a payment stuck? A decision path for pending transfers

Toss not working or a transfer shows pending? A decision path: did money leave, did it arrive, what to note, and how to avoid paying twice by mistake.

Editorial illustration for Toss not working or a payment stuck? A decision path for pending transfers

When Toss is not working, the question that matters most is whether any money moved. If nothing was debited, you can retry once the app works. If money left your account but the other side does not show it, do not pay again until you have checked your statement and read the app's help page. Toss is a name shared by more than one product, so this article gives a general decision path and not app-specific screens.

Step one: did money leave your account?

Open your bank or card app, not the payment app, and look at the latest transactions. Your bank statement is the independent record. Write down the date, the amount and any reference number. If there is no debit, the payment did not go through, and it is generally safe to try again when the app is working.

What does each outcome mean?

Bank showsApp showsWhat to do
No debitFailed or pendingWait, check again; retry only after the debit is clearly absent
DebitSuccessNothing; keep the confirmation
DebitFailed or pendingDo not pay again; read the app's help on timelines; contact support with the reference
Two debitsOne paymentNote both references; raise with the app and your bank

Worked example: a transfer of ₹3,200

Say you send ₹3,200 and the app shows pending at 6:40 pm. Your bank shows one debit of ₹3,200 at 6:40 pm with a reference. At 7:30 pm the status has not changed. Write down: 6:40 pm, ₹3,200, reference, status pending. Check the app's help page or your bank for how long such cases normally take, because we cannot state a figure. If the recipient still has not received it at the stated time, contact support with those four facts. Sending a fresh ₹3,200 in the meantime would leave you ₹6,400 out of pocket if the first one also completes.

Can an expense tracker catch double debits?

It can help you notice them. SpendixAI flags possible duplicate imports, and its Possible duplicate charges report lists the same amount to the same merchant within two days, which is exactly how an accidental second payment looks on a statement. You import statements as PDF, CSV or Excel, so this is a review you do after the fact, not a live alert.

What should you send to support?

  1. The date and time.
  2. The amount and the account it left.
  3. The reference number from your bank statement.
  4. A screenshot of the app's status.
  5. What you have already tried.

How do you make the next payment safer?

Before sending a larger amount, send nothing twice and double check the recipient's details. Keep the confirmation screen until the money has plainly arrived. Take a screenshot of it, because confirmation screens vanish. If the amount is significant, consider confirming with the recipient that it arrived before you close the matter. These steps are quick and they leave you with proof, which is what support teams ask for first. If a payment later turns out to have failed, also check that no standing instruction or repeat payment is tied to it, since a repeated debit next month would be a second surprise. Note the amount and date of the failed attempt in your own records, so that your totals do not count money that never left.

What should you avoid?

  • Sharing PINs or one-time codes with anyone who contacts you offering a refund.
  • Calling numbers found in search results instead of the official app or card.
  • Retrying repeatedly while the status is unclear.
SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports