In this article
Turn an unexplained charge into a concise chronology and evidence packet without delaying an urgent report.
A useful error report separates what the records show from what you think caused it. “The account lost money” is difficult to investigate. “The posted merchant entry is $84, my receipt is $48, and both refer to the purchase on October 6” gives a provider something concrete to examine. The purpose of an evidence packet is clarity, not proving the entire case yourself.
Report urgent concerns before perfecting the packet
Wisely’s transaction-error guidance directs cardholders to contact customer service promptly. If you suspect unauthorized activity, say that clearly and follow the official protective steps. Do not spend hours sorting documents while someone may still be using the account.
The CFPB’s prepaid-card guidance explains that applicable error protections depend on the kind of card and registration circumstances, and that reporting delay can affect responsibility. This article does not calculate a legal deadline for your account. Ask the provider what notices and documents are required and when.
One transaction, one factual summary
Begin with a sentence containing the issue, amount and date. Then identify the evidence. An amount mismatch, a duplicate posted purchase, an ATM cash discrepancy and a purchase you never authorized are different descriptions. Use the one that accurately fits your observations. If you are uncertain whether a charge is familiar, describe that uncertainty rather than making an unsupported accusation.
- Account entry: copy the displayed merchant description, amount, date and status.
- Underlying event: record what you purchased or attempted, with the actual receipt if available.
- Discovery: note when you first saw the discrepancy.
- Contacts: log who you contacted through which verified route, and when.
- Next requirement: record the requested document or action and its stated deadline.
Keep pending and posted evidence apart
Wisely’s pending-debit FAQ distinguishes ordinary pending adjustments from suspected fraud. It generally directs readers to let a normal transaction post so a merchant can update it, while telling readers who suspect fraud to contact customer service. Do not collapse these two branches into “you must always wait.”
If a pending amount changes, add the new observation to the chronology rather than replacing the old one. The earlier screenshot may show why you raised the question, while the later entry may resolve it. A clean record can therefore end with “no unexplained final debit remains,” without anyone having made a mistake in raising the original concern.
Example: two entries with one receipt
Imagine Devon has a $42 store receipt and notices two $42 account entries. One is pending and one is posted. Devon records their status and asks how they affect the account rather than declaring two completed purchases. Later, if the pending entry disappears without another final debit, the record can be closed on that basis.
Change the facts: both entries are now posted and each appears to reduce the account. Devon’s report should include both entries, the one receipt and the observation times. That is a stronger description of the question. The identical amounts alone still do not prove the cause, and the provider must assess the actual transaction records.
Make copies that are safe to use
Keep original records privately and make separate redacted copies when limited information is sufficient. Hide unrelated transactions, full account or card numbers, addresses and other people’s information. Do not alter the merchant, amount, date or status that the report depends on. Label your own annotations so they cannot be mistaken for part of the original statement.
Send documents only through a verified route requested by the provider. A screenshot dropped into a public social-media thread can disclose far more than the error itself. Never include passwords, PINs or one-time verification codes in the packet.
Track the investigation separately from your spending plan
Record the case reference and the next date or event the provider gives you. If a credit appears, ask whether it is provisional or final and what conditions apply. Do not label the case resolved simply because the balance increased. Likewise, a merchant’s promise of a refund belongs in the chronology but is not proof that funds have arrived.
Use the refund-versus-dispute guide if two processes are running at once. The finished packet should let another reader reconstruct the issue in a few minutes: what happened, what remains uncertain, what was reported and what comes next.