Cards and UPI

Lost your card? Pull your recent transactions quickly, step by step

Lost a debit or credit card? Block it first, then pull the last days of transactions, flag unknown rows and report them, with a worked example in rupees.

Editorial illustration for Lost your card? Pull your recent transactions quickly, step by step

If you have lost a card, block it first and list transactions second. Use your bank's official app, the number printed on your statement or the official website to block it, then pull the transactions since you last had the card and mark every row you do not recognise. Speed matters because disputes have time limits.

What do you do in the first ten minutes?

  1. Block or freeze the card using the bank's official app or helpline. Do not search the web for a number; use the one on your statement or the card envelope.
  2. Ask for confirmation that the card is blocked, and note the reference.
  3. Check whether any autopay or subscription is tied to the card, so you can switch it to another payment method.
  4. If the card was stolen with a phone or wallet, change other sensitive settings from a safe device.
  5. Do not read out an OTP to anyone who calls to help; the bank will not need it from you to block a card.

How do you list recent transactions fast?

Open the net-banking or mobile app you already use, go to the account or card statement and choose the shortest date range that covers the time since you last used the card for certain. Download it as PDF, CSV or Excel if possible. A shorter range makes it easier to check line by line. If you cannot get in, call the bank and ask for a mini statement.

A worked example with made-up numbers

Say you last used the card on Friday evening and discovered the loss on Sunday morning. The statement for those two days includes these rows:

RowTimeAmount in rupeesRecognised?
DinnerFriday evening1,240Yes
FuelFriday night1,100Yes
Online orderSaturday afternoon4,999No
CabSaturday night380Yes
Wallet top-upSunday early1,250No

The two unknown rows add up to 4,999 plus 1,250, which is ₹6,249. Those two rows, with date, time, amount and merchant name, are what you give the bank in your dispute. Rows you do recognise stay out of it.

What should you note down for the dispute?

  • Date and time you last used the card.
  • Date and time you noticed it missing.
  • Every transaction you did not make, with amount and merchant.
  • The reference of your block request.
  • A copy of the statement, saved to your device.

Banks have their own timelines for reporting unauthorised transactions and their own liability terms. Find them in your account or card terms, and act well inside them. This article cannot state what applies to you.

How does history in SpendixAI help?

If you have already imported your statements into SpendixAI, the history is searchable by account and date, so you can compare quickly what you normally spend and spot rows that do not fit. It does not connect to the bank, so transactions after your last import must come from a fresh statement upload.

Should you keep a record of card spending in general?

Yes, because the hardest moment to reconstruct your spending is the moment you are under stress. A habit of importing or noting your card spending each month means that on the day a card goes missing you already know your normal pattern: usual merchants, usual amounts, usual times. Anything outside that pattern then jumps out. Gig workers who use a card for fuel, vehicle repairs and phone recharges will see a very regular rhythm, so an odd online order or a late-night wallet top-up is easy to spot.

What next, once the card is replaced?

  • Update the new card on every subscription and autopay you listed.
  • Keep a list of cards and the bank helpline numbers somewhere safe, apart from the cards.
  • Switch on transaction alerts in your bank's own app.
  • Review the next two statements closely.
SPENDIXAI JOURNAL

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

Explore your reports