Shell merchant is the term for a card merchant account held by an entity that serves as a front or pass-through for another company. The FTC’s case against Humboldt Merchant Services says Humboldt processed payments for more than 1,000 merchants “that were shell entities that served as fronts or pass-throughs for fraudulent companies engaged in unauthorized billing scams” (FTC case page). The FTC states this as the allegation in its complaint. Humboldt agreed to pay $12 million in the settlement.
Run it: website cloaking checker loads a merchant’s site as a reviewer and as a customer and shows where the pages differ. Cases and rules as of 20 Nov 2026.
What the Humboldt order makes a processor do
FTC v. 5967 Ventures LLC (Humboldt Merchant Services), E.D. Mich., filed 8 Sep 2026 with a $12 million stipulated settlement (FTC press release). The FTC’s complaint says Humboldt processed about $100 million through more than 1,000 sham merchant accounts in 2021 to 2023 (Payments Dive, 9 Sep 2026). Humboldt says the settlement formalizes controls already in place, with no admission of wrongdoing, and that the conduct was under former leadership. Order terms, as summarized by Greenberg Traurig:
| duty | term |
|---|---|
| never process for | straw companies, certain MATCH-listed merchants, e-commerce merchants whose only address is a mailbox, registered-agent office or virtual office |
| screening | verify business, ownership, addresses, prior processors, chargeback history, websites used across the purchase flow; a documented principal-verification call for new businesses |
| website review | regularly, from an IP address not associated with Humboldt |
| escalation | chargeback rate above 1.0% and more than 50 chargebacks in 2 of the last 6 months: investigate at once; stop and close within 60 days unless a written report shows the practices are not deceptive |
| evasion | a client that evades monitoring is closed within 5 business days |
What one looks like
A 2026 Mastercard investigation of a scam-store network gives the signs (Mastercard, Oct 2026):
| sign | what Mastercard found |
|---|---|
| name and address disagree | the payment record named a company headquartered in Lithuania, the website listed a U.S. address |
| sibling sites | 250 other online storefronts with the same owner |
| copied sites | nearly identical code, look and feel; every product rated 4.7 stars and discounted 70% for a “limited time” that never ended |
| moving volume | when disputes and chargebacks got too high on one site, the operators shut it and drove sales through another |
| scale | $50 million in transactions on the merchant IDs identified, so the real scale was likely larger |
The acquirer ended the relationship and listed the merchant on MATCH Pro.
How to spot one
- Compare the legal name in the payment record with the name, address and contact on the site: merchant descriptor.
- Look for sibling sites with the same code, owner, or checkout.
- Re-check after onboarding, because a clean first look can change: merchant monitoring.
- Load the site as different visitors; a front can show an underwriter a clean page: website cloaking checker.
Related
Transaction laundering · GRIP letter · For payment processors
See also: for acquirers and PayFacs · prohibited merchants list · card testing attack [TODO: a shell-merchant example from our own runs, once the demo run is approved]