Getting started

Slice not working: what to check and how to keep your own record

Slice not working for a payment or card? Run the basic checks, decide whether to retry, and keep a clear record of any failed or doubled transaction.

Editorial illustration for Slice not working: what to check and how to keep your own record

If Slice is not working, begin with the symptom: a payment that fails, an app that will not load, or a transaction that has gone through twice. The first two usually clear with a network change and an app update, but the third needs a record, because the amount has left your account. we will not describe Slice's features, limits or support process, so read those on its own pages.

Failed payment or doubled payment: which is it?

They look similar at the moment of failure but call for opposite reactions. A failed payment means no money should move, so retrying once is reasonable. A doubled payment means you paid twice, so retrying again only makes it worse.

Screen saysBank statement saysWhat it probably isNext step
FailedNo debitA true failureRetry once or use another method
FailedDebit shownA failure with a pending debitWait, then check again; keep a screenshot
SuccessOne debitA normal paymentNothing to do
SuccessTwo debitsA double paymentCollect proof, contact the seller or service

Quick checks before anything else

  • Check your signal and try Wi-Fi or mobile data instead.
  • Update the app and restart the phone.
  • Look at the service's own status or help page for a known issue.
  • Try a small test payment only if the service itself allows it.

What does a doubled payment look like on paper?

Say you buy a ₹1,799 jacket at 7:05 pm. The first attempt shows an error, so you try again, and the second shows success. Next morning your statement has two lines of ₹1,799. Your spend is ₹1,799, but your balance has dropped by ₹3,598, so ₹1,799 is owed back to you.

Write down both times, both amounts and any reference numbers. Then go to the seller's help page and use their route, since the money may need to come back from them. Your bank may be able to help too, but the steps and timelines are theirs to state, so check what they say.

How do I keep my own record?

Keep a running note, or let a tracker do it. In SpendixAI you can add an expense by hand when you spend, then import your statement later and check the Possible duplicate charges report for the same amount to the same merchant within two days. That report is built for the jacket case above.

What if the problem keeps coming back?

  1. Note the dates and times of each failure for a week.
  2. See whether the failures cluster at certain hours or on one network.
  3. Update the app and phone software, and check for any notice on the service's help page.
  4. Contact support once, with your list, rather than many times with one-line complaints.

What details help support solve it faster?

A short, complete message gets a quicker answer than a long, emotional one. Include the date and time of the attempt, the amount, the screen's exact wording, the last four digits of the card or the account used (never the full number), and a screenshot. Say what you want: a reversal, a confirmation or an explanation. If you have to repeat yourself across several chats, paste the same summary each time and note the date of each contact, so your record is in order if you later need your bank to step in.

A closing list

  • One failed payment: retry once, then check the statement.
  • Two debits: stop, collect proof, contact the seller.
  • Repeated failures: keep dates and times, then use official support only.
SPENDIXAI JOURNAL

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

Explore your reports