Brief
FTC settles with Humboldt Merchant Services over processing for allegedly fraudulent merchants
Humboldt Merchant Services will pay $12 million and be permanently barred from processing payments for merchants with a heightened risk of potential fraud, under a proposed order settling FTC allegations that it processed payments for merchants that defrauded consumers.
The FTC announced an action against payment processor Humboldt Merchant Services, alleging it knowingly facilitated payment processing for sham merchants. The proposed order requires the defendant to pay $12 million and to stop payment processing for certain categories of merchants.
The detail that matters for a store is the scope of the ban: it applies to merchants with a heightened risk of potential fraud, not to all merchants. The evidence does not name those categories, so the practical test for any merchant is whether its own acquirer or processor treats its business as higher risk.
Our reading
Our reading is that the settlement's merchant-category ban, rather than the $12 million figure, is the part a store should watch, because it signals how processors may be pushed to segment and drop higher-risk accounts.
Source details and supporting facts
Each line is stated by the page named above it.
Stated by ftc.gov
- Under a proposed order, Humboldt Merchant Services will be required to pay $12 million.
- Under the proposed order, the defendant will be permanently banned from processing payments for merchants with a heightened risk of potential fraud.
- The settlement resolves allegations that Humboldt processed payments for merchants that defrauded consumers.
Sources
- US Federal Trade Commission press releasesText stored 14 September 2026
How this story was checked. Written from the 1 page listed above, stored 14 September 2026; claims checked against that stored text on 14 September 2026.
What that means
- 3 of 3 reported statements were confirmed against the page that carries them; the rest were removed rather than published.
- Figures in the text were required to appear in the stored source text: yes. Identifiers: yes.
- The check reads stored text only: no claim rests on a fresh look that did not happen.
- Where the reporting was silent, the text says so instead of filling the gap.