TL;DR
- On September 4 and September 9, 2026, the FTC settled with payment processor Nuvei ($4.85 million) and ISO Humboldt Merchant Services ($12 million) over inadequate screening of high-risk and fraudulent merchants.
- Both orders require processors to actively monitor merchant chargeback rates and cut off anyone crossing risk thresholds, the same kind of thresholds Visa already enforces through its Acquirer Monitoring Program (VAMP).
- Subscription and recurring-billing merchants run structurally closer to those thresholds than one-off retail, because a disputed failed renewal counts the same as fraud in the ratio, putting them closer to the line processors are now under federal pressure to enforce.
What happened
On September 4, 2026, the Federal Trade Commission finalized a settlement requiring payment processor Nuvei to pay $4.85 million in consumer redress and overhaul its merchant screening practices. The FTC’s complaint alleged Nuvei processed more than $30 million in consumer payments between 2017 and 2023 for Reimage, an offshore tech support scam, and separately maintained accounts for merchants making false earnings claims, merchants impersonating government entities, and merchants other processors had already terminated for excessive chargebacks. The order bars Nuvei from providing payment services to telemarketing tech support vendors and requires it to screen prospective clients, monitor high-risk categories such as outbound telemarketing, and investigate any existing client whose chargeback rate exceeds limits set in the order.
Five days later, on September 9, 2026, the FTC filed suit against Humboldt Merchant Services, the business name of 5967 Ventures, an independent sales organization (ISO) based in Tempe, Arizona, in the U.S. District Court for the Eastern District of Michigan. The complaint alleged Humboldt engaged in credit card laundering, processing transactions through more than 1,000 shell merchant accounts that functioned as fronts for fraudulent operations, moving an estimated $100 million between 2021 and 2023. Humboldt settled for $12 million and agreed to stop processing for straw companies, merchants already flagged on Mastercard’s high-risk chargeback lists, merchants facing law enforcement action, and e-commerce firms using only third-party mailbox addresses. The company made no admission of wrongdoing and attributed the conduct to former leadership.
Why chargeback ratio is the common thread
Both settlements center on the same operational failure: a processor kept moving money for merchants whose dispute or fraud profile should have triggered a cutoff. That standard is not new. Visa’s Acquirer Monitoring Program (VAMP), which replaced two older fraud and dispute programs, already scores every acquirer and merchant on a ratio: reported fraud (via TC40 reports) plus disputes (via TC15 reports), divided by settled transactions, counting card-not-present activity only. Acquirers cross into “Above Standard” at a 0.5% ratio and “Excessive” at 0.7%. Merchants have their own bar, and Visa lowered it in April 2026, from 2.2% down to 1.5%. Once a merchant is enrolled as Excessive, there is no warning tier: Visa assesses $8 per disputed or fraudulent transaction.
A chargeback, for readers newer to the term, is a forced reversal a customer’s card-issuing bank pushes back through the network when the customer disputes a charge, distinct from a refund the merchant issues voluntarily. Subscription and recurring-billing businesses generate more of them than one-off retail for a structural reason: involuntary churn, the loss of a paying customer because a renewal payment failed rather than because the customer chose to cancel, is a routine feature of card-based billing, not an edge case. When a renewal fails and retries, and a customer notices an unexpected or repeated charge attempt, some meaningful share dispute it with their bank instead of contacting the merchant. That dispute counts identically to a fraud report in the VAMP ratio, regardless of whether anything fraudulent happened.
Two federal settlements landing eight days apart do not change the math of that ratio. They change the incentives around it. A processor operating under an FTC consent order, or simply watching a peer get one, has a new reason to treat a merchant sitting close to a chargeback threshold as a liability worth exiting rather than managing, even when the merchant’s actual behavior is legitimate. For a subscription business running close to that line, the risk is no longer just the $8-per-transaction VAMP fee. It is a review, a rate change, or a processor deciding the relationship is not worth the regulatory exposure.
How orchestration architecture absorbs this
The exposure described above is concentrated by design whenever a merchant’s entire renewal volume runs through a single processor: one underwriting decision, one risk appetite, one point of failure if that processor tightens its posture or draws regulatory scrutiny.
SGW Payment’s routing model addresses the first half of that concentration. Through a single SDK and API integration, SGW connects merchants to a network of payment providers and routes each transaction to the provider most likely to approve it. The practical effect for chargeback exposure is that a merchant’s book is not read, priced, or risk-managed by a single processor’s underwriting team. If one provider in the network becomes more conservative, for reasons connected to its own regulatory posture or otherwise, the routing layer keeps other approval paths live rather than leaving the merchant dependent on that one relationship’s judgment call.
The second half is geographic. SGW acts as the payments infrastructure layer for international expansion: when a client enters a new market, SGW stands up the local setup on the client’s behalf, incorporating entities where required, opening banking and acquiring relationships, negotiating PSP contracts in the jurisdiction, and running the downstream finance operations, including reconciliation, cash flow, reporting, and local tax clearance in every jurisdiction it processes in. A byproduct of that structure is that dispute and underwriting exposure sits inside multiple local acquiring relationships rather than being funneled entirely through one global processor’s risk book. Transactions also process locally rather than cross-border, which on its own lifts issuer approval rates significantly and compounds with the routing layer, and fewer failed authorizations upstream means fewer retries and disputes downstream.
Takeaways you can act on this quarter
- Calculate your own VAMP-style ratio before a processor does it for you. Fraud reports plus disputes, divided by settled transactions, card-not-present only. Know where you sit relative to the 1.5% merchant threshold.
- Audit your retry logic for dispute risk, not just approval rate. Repeated authorization attempts on a declined card can read like card testing to a fraud model and add to your dispute count either way.
- Treat single-processor dependency as a line item on your own risk register. A processor’s regulatory exposure is now a variable in whether your account stays in good standing, not just a vendor-management detail.
- If you are entering a new market, price out a local acquiring relationship rather than routing that volume through your current processor’s global rails. Building local entity, banking, and acquiring yourself typically takes 6 to 12 months per market; that is the benchmark to measure any alternative against.
- Check your existing processors’ regulatory history, including FTC and state enforcement actions, the same way you would check a vendor’s uptime record. A processor already under a consent order has less room to tolerate a borderline account than one that is not.
Sources
- Payment Processor Nuvei Must Implement Robust Merchant Screening Practices and Pay $4.85 Million to Settle FTC Charges (Federal Trade Commission, September 4, 2026)
- Processor pays $12M to settle ‘sham’ merchant case (Payments Dive, September 9, 2026)
- Stricter VAMP Ratio Thresholds Are Now in Effect: Here’s How to Stay Compliant (Merchant Risk Council, 2026)
About SGW Payment. SGW Payment helps online businesses capture more revenue and reduce processing costs. Through a single SDK and API, SGW connects merchants to a network of payment providers and routes each transaction to the provider most likely to approve it. On top of the technology, SGW acts as the payments infrastructure layer for international expansion, standing up the local payments stack (entity, banking, acquiring, and finance operations) in every new market, so transactions process locally rather than cross-border. Learn more at sgw-payment.com.
