FRAUD CHECK — Squire It™
sharelivefraud.com/squire-it
LIVE FRAUD ALERT
LIVEFRAUD Check #15
FTC WARNS

The FTC says that when an unexpected contact insists you pay only by bank transfer, wire transfer, cryptocurrency, payment app or gift card, that demand itself is a sign of a scam.

HIGH CONFIDENCEPublished 2026-08-17
S
Q
U
I
R
E
D
E
S
K
·
C
H
E
C
K
E
D
·
B
A
T
T
L
E
D
·
R
E
C
E
I
P
T
E
D
·
S

What we found

A consumer alert published by the FTC on 22 July 2026 describes a pattern in which someone contacts you unexpectedly and says you have to pay to fix a problem, get a prize or something else. According to that alert, the tell is the payment method: the caller or messenger says the only way to pay is by bank transfer, wire transfer, cryptocurrency, payment app or gift card. The FTC states that reports it has received show this is a scam. If an unexpected demand for money can only be settled by gift card, wire, bank transfer, crypto or a payment app, do not pay — end the contact and look up the organisation's number yourself before you do anything else. The alert does not say how the contact reaches you, so we cannot tell you whether this arrives by phone, text, email or in person. It also gives no figures for how many reports were received, no dollar losses, and names no company or agency being impersonated. Our harvested material contains a single official advisory and no press coverage, community reports or lookup results to sit alongside it. LIVEFRAUD ALERTS is independent and is not affiliated with the FTC or any government agency; this alert restates a public consumer advisory and adds nothing beyond it.
THE RULE
Payments by gift card, wire, bank transfer, crypto or payment app are hard to reverse once sent, so a wrong decision here tends to be final.

What we don’t know

The bench — who voted

4 INDEPENDENT AI MODELS REVIEWED THIS. ALL 4: HIGH RISK.

The card names a count. Here are the seats behind it, with what each one said.

ANTHROPICclaude-opus-5 · HIGH
The finding adds an operational instruction ('end the contact and look up the organisation's number yourself') that does not appear in the single evidence row, while simultaneously asserting the alert 'adds nothing beyond it'. The advice is sound and consistent with standard FTC guidance, but it is the writer's addition and should be labelled as such rather than folded into the paraphrase of the advisory.
DISSENT, PRESERVEDThe pattern is generic, evergreen consumer guidance, not an active or localised campaign. Publishing it under an 'alert' framing with a specific date risks implying a new or ongoing incident when the underlying material describes none. I would present it as standing advice, not as news.
DISSENT, PRESERVEDBecause the evidence establishes no contact channel, no impersonated brand and no loss figures, the piece should carry no implication that readers are currently being targeted by anything in particular. The listed unknowns do this honestly and must not be trimmed in editing.
DISSENT, PRESERVEDI grade the pattern high despite the thin evidence: the payment rails named — gift card, wire, bank transfer, crypto, payment app — are effectively irreversible, so a reader who complies once typically loses the money permanently. The grade reflects the danger of the pattern, not the strength of the sourcing.
GOOGLEgemini-flash-latest · HIGH
Raised no objection; read the evidence as holds.
GROQopenai/gpt-oss-120b · HIGH
Raised no objection; read the evidence as holds.
OPENROUTERopenrouter/free · HIGH
Raised no objection; read the evidence as holds.

Reviewed by 4 independent models; all found the finding carried by the evidence.

▼ Protocol & challenge record
Objection (high): The finding makes three affirmative statements about what the FTC alert *omits* ('The alert does not say how the contact reaches you', 'gives no figures... names no company or agency'), but the harvested row contains only a single opening paragraph — plainly an excerpt, not the full advisory. FTC consumer alerts of this type routinely continue with channel examples, 'what to do' steps and links. We have no basis for characterising the whole document's contents from its lede. These must be reworded to describe our harvest ('the material we hold does not say...'), or the full alert must be retrieved before the omission claims stand.
Not resolved — preserved on the record.
Objection (high): Internal contradiction / channel invention. Sentence 2 says 'the caller or messenger says the only way to pay is...' — 'caller' asserts a telephone channel and 'messenger' a messaging channel. Sentence 5 then says the alert does not disclose the channel. The source says only 'someone contacts you unexpectedly'. One of these two sentences is wrong, and it is sentence 2: it adds channel detail the row does not support, then the limitation line denies that detail exists. Fix by using the source's own neutral wording ('whoever contacted you').
Resolved: Replace 'the caller or messenger says' with the source's neutral formulation ('whoever contacted you says'), which removes the contradiction with the channel limitation at no cost to meaning.
Objection (medium): Source-to-claim stretch in the conjunction. The FTC's tell is a compound: unexpected contact + a demand to pay to fix a problem or claim a prize + payment restricted to those five methods. The headline claim compresses this to 'that demand itself is a sign of a scam', and the risk framing invites readers to treat any bank-transfer or payment-app request as fraudulent. Bank transfers, payment apps and wires are ordinary legitimate payment rails (rent, contractors, invoices, family). The 'unexpected contact / pay to fix a problem or get a prize' precondition must survive into the claim line, or the piece produces false positives it cannot defend.
Not resolved — preserved on the record.
Objection (medium): The advice sentence is unsourced and imports an entity the source never mentions: 'look up the organisation's number yourself'. The advisory describes 'someone', not an organisation, and the finding itself concedes no impersonated company or agency is named. The advice therefore presupposes an impersonation scenario that the evidence does not establish. Either drop the 'organisation's number' step or ground it in a cited FTC recommendation.
Not resolved — preserved on the record.
Objection (medium): Jurisdiction mismatch versus audience. The sole source is the US FTC, and its warrant is 'reports to the FTC' — i.e. US consumer reports. The piece is written for a non-US readership (British spelling, day-first date) and is flagged 'ATTENTION: EVERYONE', with no note that the underlying evidence base, the reporting channel and any redress route are US-specific. Non-US readers are given no correct place to report.
Not resolved — preserved on the record.
Objection (medium): Confidence 'high' is doing work the evidence cannot bear at the level of the *published artefact*. It is defensible that the FTC said this; it is not defensible to publish a high-confidence 'alert' whose own finding admits it 'adds nothing beyond' a public advisory, with a single excerpted row, no corroboration, no incident, no numbers and no target. The confidence field is being read by the reader as confidence in the alert's newsworthiness and specificity, not merely in the quotation's accuracy. At minimum the confidence reasons must state that this is quotation confidence only and that the item is evergreen guidance, not a live incident.
Not resolved — preserved on the record.
Objection (low): Date currency unverified. The row is dated 2026-07-22. Nothing in the packet establishes that this date is in the past relative to publication, that the alert has not since been updated or superseded, or that there is any time-sensitive hook justifying an 'alert' framing for guidance the FTC has published in substantially similar form for years. A future-dated or long-stale source would each be fatal in different ways and neither has been ruled out.
Not resolved — preserved on the record.
Objection (low): Callout and share directive are mismatched to the source and to each other. 'ATTENTION: EVERYONE' is the absence of targeting and inflates a generic advisory; the alternative option 'ANYONE ASKED TO PAY BY GIFT CARD' is closer to the evidence. The share directive also silently drops two of the five listed methods (bank transfer, payment app), narrowing the warning after the finding widened it.
Resolved: Switch the callout to 'ATTENTION: ANYONE ASKED TO PAY BY GIFT CARD' and restore all five payment methods, or an explicit 'and similar' clause, in the share directive.
Objection (low): The risk_line ('hard to reverse once sent... a wrong decision here tends to be final') is an unsourced editorial assertion carrying no row_id. It is plausible and widely held, but the packet's only source says nothing about reversibility. Either cite it or mark it explicitly as our own assessment.
Resolved: Prefix the risk_line as an editorial assessment rather than a sourced statement, e.g. 'Our assessment: payments by...'.
Preserved dissent
ON THE RECORDI do not think this should run at all in its present form. The finding concedes, in its own words, that it 'restates a public consumer advisory and adds nothing beyond it': there is no incident, no victim, no impersonated brand, no channel, no report count, no loss figure, no geography, and no corroborating row of any kind. What remains is a single excerpted paragraph of evergreen guidance that the FTC has been publishing in one form or another for a decade. Dressing that in 'ATTENTION: EVERYONE', a high-confidence label, a share directive and a finality-flavoured risk line manufactures urgency the evidence does not contain, and every such item spends down the reader's willingness to act on the alerts that do describe something real.
ON THE RECORDI regard OBJ-1 as the most serious defect on the page, and not a cosmetic one. Telling readers what an official advisory 'does not say', on the strength of its first paragraph, is an assertion about a document we have not read. It is also self-serving: each stated omission makes our thin harvest look like a limitation of the FTC rather than a limitation of our own collection. If we cannot retrieve the full alert, the honest formulation is 'the excerpt we hold does not say', and the piece should say so in those words.
ON THE RECORDI also think the blanket framing in the claim line is affirmatively harmful, not merely imprecise. 'Bank transfer... that demand itself is a sign of a scam' will be read by some readers as 'bank transfers are a scam'. The FTC's warrant depends entirely on the unexpected-contact precondition, and stripping it out converts sound advice into a rule that misfires against landlords, tradespeople and relatives. If the compound condition is not restored to the claim, I would not put my name to the check.

The sources

Official sourceA way to spot scams: how someone asks you to pay2026-07-22
The FTC's 22 July 2026 consumer alert says an unexpected contact demanding payment only by bank transfer, wire transfer, cryptocurrency, payment app or gift card is a scam, based on reports to the FTC.
Authority: official. Retrieved 2026-08-17.
Limitation: General guidance rather than an incident report: no contact channel, no report counts, no loss totals, no named impersonation target and no affected group described.
Open the original source →

Other checks

Every check we have published →

Share this receipt
sharelivefraud.com/check/6qaiXiU

Approved by ihubglobalhq on 2026-08-17, after the six-point evidence checklist.

Something wrong here? Tell us and we'll correct it — corrections are published, not quietly edited.

Phishy? Send it → sharelivefraud.com/squire-it

Not affiliated with any government agency, credit bureau, bank, platform, or law-enforcement agency. Informational only — not legal or financial advice.

Naming a source is not an endorsement, and being named here is not an accusation against any company.

Powered by SquireIt™

Verify this receipt at squireit.com

Join Squire’s First Watch

Alerts before the feed. Credit when your summons becomes a receipt. A vote on what we check next. Founding names are permanent.

Get the next one

We publish a receipt for every alert, including the ones we decide not to run.

We will ask you to confirm before anything is sent. Your address is used for this and nothing else, and is never shared.