Getting started

Jupiter not working? Three questions that find the fault fast

Jupiter not working on your phone? Three quick questions separate an app fault from a phone or network fault, and your statement shows if money moved.

Editorial illustration for Jupiter not working? Three questions that find the fault fast

When Jupiter is not working, ask three questions in order: is it only this app, only this phone, or only right now? The answers narrow the fault to the app, the device or the network in a couple of minutes, and your bank statement then tells you whether any payment went through. Do these checks before you reinstall or retry a payment.

Is it only this app?

Open another app that needs the internet, such as a browser. If it loads, your connection is fine and the issue sits with this one app. Open the app store and look for a pending update, because an old version can stop working when the service changes something behind the scenes. Then close the app fully from the recent apps list and open it again.

Is it only this phone?

If you have a second phone, or a family member who will let you check, try the same login there. If it works, something on your phone is the cause. The usual suspects are low storage, a stuck background process, a wrong date and time setting, and a battery saver mode that restricts background work.

  • Set date and time to automatic.
  • Free up some storage, even a few hundred megabytes helps.
  • Turn off battery saver for this app.
  • Restart the phone.

Is it only right now?

Some faults are on the service side and fix themselves. If everything else checks out, wait twenty to thirty minutes and try again instead of hammering the screen. Repeated taps on a pay or transfer button are what create duplicate attempts.

What if a payment was in progress?

This is the part that costs money. Say you tried to pay ₹2,400 and the app froze on a spinner. Before you try again, open your bank statement or your bank's own app and look for a debit of ₹2,400 at that time.

Bank showsMeaningYour move
Debit of ₹2,400Money leftKeep proof, do not pay again, ask the seller to confirm
No debitNothing movedSafe to retry once
Debit then credit of ₹2,400ReversedRecord both, then retry if still needed

If you paid twice by mistake, the sum is simple: 2 × ₹2,400 = ₹4,800 out, ₹2,400 more than you owed. Record both lines so you can ask for the extra back.

What to do about your own records

A failed app is a good reminder that you need a record that does not depend on the app. If you track spending in SpendixAI, upload the bank statement for the account involved and review the rows before saving. The statement is the source, so the entry shows what really happened rather than what a frozen screen suggested. You can also add the expense by hand.

One more habit helps: note the time you first noticed the fault. If a payment later appears on your statement with a timestamp close to that moment, you can connect the two without guessing.

When to contact support

If the fault survives all three questions, contact support with a short message: what you tried, what time it began, the app version, and the amount and date of any payment. Add screenshots. Wait for the company's reply for as long as its own help page says to expect, and keep a note of the reference they give you.

  • Date and time of the failure.
  • Screenshot of the error.
  • Bank statement line, if any money moved.
  • Steps already tried.
SPENDIXAI JOURNAL

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

Explore your reports