Bill CleanupPersonal finance admin

That $1 Charge You Don't Recognize: Routine Verification Hold or Card Testing?

A $1 charge on a credit card or bank statement is usually a temporary verification hold, not a real charge: payment processors like Stripe describe merchants sending a $1 authorization to confirm a card is valid, PayPal charges up to $1 when a card is added or edited, and Google posts GOOGLE *TEMPORARY HOLD while verifying a card. Holds like these drop off on their own and are tied to something you just did — adding a card, starting a trial, renting, or fueling. The dangerous cousin is card testing, where fraudsters probe a stolen card number with small transactions before larger ones. Use the decision tree below: match the $1 line to a recent action of yours; if nothing matches, treat it as a probe and call your issuer.

Bill CleanupReviewed September 13, 20267 min read

A 1 dollar charge on a credit card statement is usually machinery, not theft. Payment systems verify cards with tiny temporary authorizations: Stripe's support documentation describes businesses sending a $1 authorization simply to confirm a card is valid, PayPal states it charges up to $1 when you add or edit a card and releases the pending line after verification, and Google labels its version GOOGLE *TEMPORARY HOLD while it checks a card. These holds are not settled charges — they drop off on their own, typically within days, and they correlate with something you just did.

The reason you should still look twice is the dangerous cousin: card testing. Stripe's fraud-prevention documentation describes how fraudsters validate stolen card numbers with small transactions or authorizations before attempting bigger ones. The two look similar on a statement; the difference is whether the tiny charge matches a recent action of yours. That one question drives the whole decision tree.

Who this is for

This guide is for anyone who found a $1, $0, or similarly tiny line on a card or bank statement and is deciding between "ignore it" and "cancel the card." Both are sometimes right, and picking wrong in either direction costs you — panic-cancelling a card breaks every autopay on it (and, as the card-updater guide explains, may not even stop the charges you wanted stopped), while ignoring a real probe hands a fraudster a validated card number.

It is not a full fraud-response guide, and it does not cover larger unknown charges — for those, run the statement descriptor decoder first.

The one question that classifies the charge

Did you, or anyone on the account, do something in the last few days that stores or verifies a card? Verification holds are triggered by your own actions. The classic triggers:

  • adding or editing a card in a wallet or account (PayPal's documented up-to-$1 verification is exactly this),
  • starting a free trial or new subscription (the merchant verifies the card it will bill later — pair this with the free-trial first-24-hours guide),
  • checking into a hotel, renting a car, or paying at a fuel pump,
  • saving a card with a new online store or booking platform.

If one of those happened, you are almost certainly looking at a hold. If none of them happened — and nobody else on the account did them either — treat the line as a possible probe.

The decision tree

Question If yes If no
1. Is the line pending rather than posted? Continue — holds live in pending A posted $1 charge deserves a closer look; continue
2. Did anyone on the account add a card, start a trial, book, rent, or fuel in the last few days? Verification hold: note it and watch it drop off Continue
3. Does the descriptor match a company you have a relationship with (for example GOOGLE *TEMPORARY HOLD on a card in your Google account)? Verification hold: same as above Continue
4. Is it a single, one-time tiny line? Watch list: calendar a check in a week; no action if it drops off Continue
5. Are there several tiny charges, repeats, or tiny charges from unknown merchants across days? — Treat as card testing: call your issuer now

Actions per verdict:

Verification hold. Do nothing except note it. It should disappear from pending or drop off within days. If the same "hold" posts and stays past a statement cycle, it is no longer a hold — dispute it as a billing error with your records, per the FTC's dispute guidance, or use the duplicate-charge proof packet if it shadows a real purchase.

Watch list. One unexplained tiny line, nothing else suspicious: screenshot it with the date, set a reminder for seven days, and check whether it dropped off. Escalate only if it posts or gains company.

Card testing suspected. Call the number on the back of the card, not a number from a search. Say what you see: small unfamiliar authorizations, no matching activity. The issuer decides on reissue; if the card is replaced, expect the cleanup that follows — walk the recurring payment map so your legitimate autopays survive the swap.

Why fraudsters bother with $1

A stolen card number is inventory of unknown quality. Before using or selling it, the holder wants proof the card is live — and a tiny authorization is a cheap test that many cardholders never notice, which is precisely what Stripe's card-testing documentation describes from the merchant-defense side. That has a practical consequence for you: the $1 probe itself is not the loss. It is the reconnaissance. The response that matters is preventing the follow-on charge, which is why the "several tiny charges from strangers" branch of the tree goes straight to the issuer rather than to a $1 dispute.

Common mistakes

  • Disputing a pending hold. Pending authorizations routinely change or vanish; issuers generally want you to wait for posting, and most holds resolve themselves first.
  • Cancelling the card over one explainable line. If the $1 matches your own trial signup from Tuesday, the card is fine. Save the panic for unmatched patterns.
  • Ignoring repetition. One tiny line is noise; three tiny lines from unknown merchants is signal.
  • Forgetting other account holders. A spouse's new wallet setup generates the same holds yours does. Ask before acting.
  • Treating the $1 as the whole problem. If testing is confirmed, watch the account daily for the follow-on charge until the reissued card arrives — that larger charge, not the probe, is the one to dispute.

Next action

Walk the decision tree for the tiny line on your statement now, then run the statement descriptor decoder on anything else you cannot name — the two guides together turn a statement scan into a five-minute routine.

FAQ

Why is there a $1 charge on my credit card?

Most likely a temporary verification authorization: processors and merchants confirm a card is valid by sending a small authorization, as Stripe's support documentation describes, and PayPal documents charging up to $1 when a card is added or edited. It is pending, not settled, and drops off on its own.

How long does a $1 verification hold stay on my card?

Typically a few days, though PayPal notes a verification line can persist longer depending on the bank. If a supposed hold posts and survives a full statement cycle, treat it as a billing error and dispute it with your records.

Is a $1 charge a sign my card was stolen?

Only when it does not match anything you did. A tiny authorization tied to your own card-add, trial, rental, or fuel stop is routine. Several tiny charges from merchants you do not know, with no matching activity, fits the card-testing pattern — call your issuer.

Should I dispute a $1 charge?

Not while it is pending. If it never drops off and posts, or if it is part of a suspicious pattern, contact your issuer — for a pattern, ask about fraud and reissue rather than filing a $1 billing dispute.

Claim ledger

Claim Source Checked Confidence
Businesses may send a $1 temporary authorization to verify a card, and it is not a settled charge. https://support.stripe.com/questions/unexpected-1-charge-on-customers-bank-statement 2026-09-13 High
PayPal charges up to $1 to verify an added or edited card, showing as pending until it clears, with duration depending on the bank. https://www.paypal.com/us/cshelp/article/why-did-paypal-charge-1-to-my-card-help173 2026-09-13 High
Google uses a GOOGLE *TEMPORARY HOLD descriptor for pending card verification that goes away when the transaction completes. https://support.google.com/googlepay/answer/7644142 2026-09-13 High
Card testing means fraudsters validate stolen card numbers with small transactions or authorizations before larger fraud. https://docs.stripe.com/disputes/prevention/card-testing 2026-09-13 High
Cardholders should review statements and can dispute unauthorized or erroneous charges. https://consumer.ftc.gov/articles/using-credit-cards-and-disputing-charges 2026-09-13 High

Sources

Sources

  1. https://support.stripe.com/questions/unexpected-1-charge-on-customers-bank-statement
  2. https://www.paypal.com/us/cshelp/article/why-did-paypal-charge-1-to-my-card-help173
  3. https://support.google.com/googlepay/answer/7644142
  4. https://docs.stripe.com/disputes/prevention/card-testing
  5. https://consumer.ftc.gov/articles/using-credit-cards-and-disputing-charges

Reviewed

Scope: Personal finance admin. We update this guide as the underlying search behaviour changes.

Billing errors and dispute evidence

Decode the Charge: What SQ*, APPLE.COM/BILL, GOOGLE*, and PAYPAL Prefixes Mean on Your Statement

An unknown charge on a bank statement usually is not fraud — it is a real purchase hiding behind a processor's descriptor. SQ* means a business that takes payments through Square; APPLE.COM/BILL is Apple billing for apps, subscriptions, or a family member's purchase; GOOGLE* prefixes are Google products with per-product formats; PayPal lines can be any merchant you approved an automatic payment for. Each of those processors runs an official lookup: Square's receipt lookup, Apple's reportaproblem.apple.com, Google's statement-charge page, and PayPal's automatic payments list. Run the 15-minute identification workflow below before you file any fraud claim.

Reviewed September 13, 20268 min read
Subscriptions and recurring charges

You Replaced Your Card, but the Subscription Charged the New Number Anyway? That Is a Card Updater, Not a Glitch

If you got a new card and a subscription still charged you, the most likely explanation is a card-on-file updater network. Visa Account Updater and similar issuer programs pass your new card number and expiration date to participating merchants automatically, so a card swap alone does not stop recurring billing. To actually stop a charge: cancel with the merchant and save proof, revoke the billing authorization in writing, ask your card issuer whether an account updater applies and how to exclude the merchant, and only then treat a repeat charge as a billing error you can dispute.

Reviewed September 13, 20268 min read
Billing errors and dispute evidence

Duplicate Charge on a Bill? Build This Proof Packet Before You Ask for a Refund

If you see a duplicate charge on a bill, do not start by calling it fraud or demanding a guaranteed refund. First confirm whether both charges actually posted, whether one is only a pending authorization, whether the dates, amounts, invoice or order numbers, and account credits match, and whether the merchant already corrected one line. Then send the merchant a short refund request with the proof packet. Escalate to the card issuer or payment provider only if the merchant cannot explain or correct the duplicate and your records support the billing-error claim.

Reviewed September 5, 202611 min read