StatementDecoder

Pending charge you don't recognize? What it is, why the name looks wrong, and what to do

2026-07-19 · 7 min read

A pending charge you don't recognise is the most common false alarm in personal banking — because pending entries are, by design, provisional. The name is often wrong, the amount is often wrong, and a good share of them vanish without ever posting. Here's how to read one before you panic.

What a pending charge actually is

When you pay by card, two separate things happen. First, an authorisation: the merchant asks your bank to reserve the money, and the reservation shows in your app as "pending". Later — usually one to three days — the merchant settles the transaction, and the charge posts with its final descriptor and amount. Pending entries reduce your available balance but haven't left your account yet.

Why the name looks wrong while pending

The authorisation carries whatever identifier the merchant's terminal or gateway sent — sometimes a parent company, a payment gateway's placeholder, or a truncated processor string — while the settlement usually carries the cleaner, final descriptor. So the same purchase can appear as one name today and a different name when it posts. If a pending line puzzles you, the descriptor anatomy still applies: look for a processor prefix first, and try the exact-string lookup with whatever text you have.

The innocent explanations, in order of likelihood

  • Pre-authorisation holds. Fuel pumps commonly authorise a fixed amount before you pump; hotels and car-hire firms add deposit headroom; bars pre-authorise before a tab. The held amount can be far from what you'll actually pay.
  • Card verification charges. New subscriptions, card-on-file updates and some sign-ups authorise a small amount (often 0.00 or 1.00) just to test the card — these almost always drop off without posting.
  • Delayed or re-sent authorisations. A merchant whose first settlement failed may re-authorise days later, making an old purchase look brand new.
  • Tip and total adjustments. Restaurants authorise the pre-tip amount; the posted charge includes the tip, so pending vs posted amounts differ legitimately.

Will it just disappear?

If the merchant never settles — cancelled orders, expired holds, verification pings — the authorisation lapses and the pending entry disappears, typically within a few days (card-network hold windows vary by merchant type; hotel holds can persist longer). Nothing to do, nothing to dispute: banks generally won't action a pending transaction anyway, precisely because it isn't final.

When a pending charge deserves attention

  • You're certain no one with access to the card made any purchase that could match the amount or timing.
  • Several small pending authorisations appear in quick succession — the card-testing pattern that precedes real fraud.
  • The pending charge comes with a text or email "confirming" a purchase you never made (also a common phishing pretext — go to your bank's app directly, never through the message).

In those cases don't wait for settlement: contact your bank, ask them to decline the authorisation if they can, and request a replacement card — a compromised number stays compromised. The full escalation path is in how to dispute a charge.

The verify-then-act routine

  1. Wait for settlement if nothing else is suspicious — half of mystery pendings resolve into recognisable posted charges.
  2. Once posted, identify the final descriptor properly (the five-minute method).
  3. Still unknown after identification? Now it's dispute territory — with the posted line as your evidence.

And if one mystery pending made you distrust the whole statement, upload it: every posted charge gets identified in one pass, with card-testing patterns and duplicates flagged automatically.