What we found
- Single source, but it is a first-party official FTC press release describing its own enforcement action and settlement figure.
- The mechanism described (search ads carrying biller names and logos, undisclosed add-on fees, unconsented subscription charges) is stated directly in the source, not inferred.
- Downgraded from certainty because the matter rests on allegations resolved by a proposed stipulated order awaiting a judge's signature, and no consumer-harm numbers are given.
- Reviewed by 3 models, 2 from independent houses.
What we don’t know
- How many consumers were charged undisclosed fees, and the typical amount per person.
- Which billers' names and logos appeared on the landing pages.
- How the $2.1 million in redress will be distributed and whether consumers must apply.
- Whether the search ads are still appearing at the time of publication.
The bench — who voted
3 INDEPENDENT AI MODELS REVIEWED THIS. 2 OF 3 — ONE MODEL DISSENTED. READ WHY.
The card names a count. Here are the seats behind it, with what each one said.
DISSENT, PRESERVEDThe headline CLAIM as written — an online bill payment firm, misleading search ads posing as billers, undisclosed fees, $2.1 million settlement — is fully carried by the row. The problem is confined to the expanded finding, which should either be cut back to the row or be republished with the underlying press release and complaint attached as evidence.
DISSENT, PRESERVEDOn the grade I would defend 'high' even though the documented harm here is fee-level rather than total loss. An ordinary reader cannot tell a paid search result that overcharges from one that takes the payment and never pays the biller; both present identically, and biller-impersonation search ads are a high-volume vector touching utilities, loans and rent. The mitigation offered — type the address yourself or use the one on the paper bill — is correct and worth publishing regardless of how the sourcing objections are resolved.
DISSENT, PRESERVEDPublishing a named company and two named individuals on the strength of one unnamed-firm summary line is the specific risk I want on the record, independent of whether the underlying facts turn out to be right.
Reviewed by 3 independent models; all judged the finding to go beyond the evidence.
▼ Protocol & challenge record
ON THE RECORDI do not accept the 'high' confidence label as it stands. The sourcing is strong — one first-party FTC release, mechanism stated not inferred — but confidence in this system is supposed to describe the finding as written, and the finding as written contains a self-contradiction about legal posture (court found a ROSCA violation / 'these are allegations... nothing here is a finding') and a sourced-tagged sentence about 'outright scams' that the source does not contain. Sound source, unsound write-up. Until those two are fixed, high is the wrong number.
ON THE RECORDThe most serious problem here is not a citation-tagging problem, it is a fairness problem, and I want it on the record in plain words. Doxo is a named, real, operating company. This alert never tells the reader that. It puts Doxo one sentence away from 'outright scams', gives it bank and card watch icons, and paints a risk_line about paying 'a look-alike page'. A reader finishing this alert will believe Doxo is a criminal impersonation operation. What the FTC actually alleged is that a genuine third-party bill-pay platform misrepresented its affiliations and buried fees and subscription terms — serious, but categorically different. Publishing the current framing about a named company is the kind of thing that gets a publication sued, and it would deserve it.
ON THE RECORD'Never pay a bill through a search result' is bad advice dressed as strong advice. It is not in the source, it is not achievable, and it teaches readers a rule they will break within a week — which discredits the rest of the guidance. The type-in-the-address instruction does all the useful work. Drop the 'never'.
ON THE RECORD'ATTENTION: VETERANS' appearing as a callout option on a record where nothing in evidence mentions veterans is a bigger deal than a stray option in a dropdown. The pipeline correctly blocked the forward-to-a-named-group directives under §11 Rule 2 but let a fabricated demographic audience through on the callout side. That is an asymmetry in the guardrail, not a one-off, and it will recur on other items.
ON THE RECORDThe suppression log should not be read as reassurance. Two of the four suppressed targeting candidates were the bare words 'through' and 'result'. An extractor that nominates prepositions and nouns as populations at risk, and nominates the FTC's own Bureau director's first name as a group to forward the alert to, is not producing signal that anyone downstream should weight.
The sources
Official sourceBill Payment Firm Doxo to Pay $2.1 Million to Settle FTC Allegations It Deceived Consumers and Charged Them Add-On Fees2026-08-17
The FTC announced a $2.1 million settlement over allegations that a bill payment firm used misleading search ads to impersonate consumers' billers and tacked on undisclosed delivery fees and subscription charges.
Other checks
Published under standing founder pass (A9) — every claim source-mapped by the machine.
▼ What the machine checked
- ✓ Not a community submission.
- ✗ Draws on an FTC enforcement release, which names a defendant: "Bill Payment Firm Doxo to Pay $2.1 Million to Settle FTC Allegations It Deceived".
- ✓ All 7 material sentence(s) map to FTC.
- ✗ anthropic returned "overstated"; groq returned "overstated"; openrouter returned "overstated" — published on the receipt, not blocking (A9 amendment).
- ✓ No audience band is set.
No human affirmed these. They were verified by the classifier described in Amendment A9, on 2026-08-24.
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™