Why This Sounds Rare, But the Mechanism Behind It Is Real
Running two payment processing relationships at once sounds like an edge case, most merchants have enough on their plate managing one. No source directly studies how common the practice actually is. But the regulatory mechanics that would make it a rational choice for some merchants are real, documented, and worth understanding on their own terms.
That distinction matters for how an agent should read the rest of this piece: the mechanism is sourced, the behavior itself is not.
VAMP’s Actual Thresholds, and What They Are Tied To
Visa’s Acquirer Monitoring Program sets a Merchant-Excessive ratio of 1.5% for most regions, or 2.2% in the CEMEA region, each requiring a minimum of 1,500 combined fraud and dispute reports in a month before the threshold applies. The ratio itself is calculated as the count of reported fraud and disputes divided by the count of total sales, tracked against a single merchant ID. Acquirer-level tiers exist too, “Above Standard” at 0.5% to under 0.7%, and “Excessive” at 0.7% or higher, with enforcement, fees, and penalties that began October 1, 2025.
Every number in that threshold is tied to one specific merchant ID’s own transaction history, not to the business as a whole.
How Splitting Volume Across Two Accounts Could Theoretically Help
This is reasoning, not a confirmed tactic. Because VAMP’s ratio is calculated per merchant ID, a business processing all of its volume through one account concentrates its entire fraud and dispute history against that single ratio. Splitting volume across two merchant IDs, whether at two different processors or two accounts at the same one, would spread that same dispute activity across two separate ratios, each further from the threshold than a single combined account would be.
No source confirms merchants actually reason through VAMP mechanics this explicitly before deciding to run two accounts, but the underlying math is real enough that the incentive would exist for a merchant who understood it.
The Simpler, More Obvious Reason: Redundancy
A second, less technical explanation needs no chargeback-ratio math at all: processing continuity. If one processor’s system goes down mid-shift, a merchant with a second live account can keep accepting cards while the first is unavailable, a real operational concern for any business that cannot afford to simply stop taking payments for an hour.
Rolling reserve exposure is a related, adjacent consideration. A processor typically withholds a percentage of daily sales, illustrated at 10%, for 30 to 180 days on higher-risk accounts as a hedge against chargeback and fraud exposure. A merchant already carrying that kind of reserve on one account may have a reason to avoid concentrating even more risk with a single processor.
Why No Source Actually Confirms Merchants Do This, or How Often
Neither the VAMP mechanics nor the rolling reserve mechanics above are evidence that merchants act on them this specific way. No survey, trade-press report, or card-network publication documents how commonly merchants intentionally run two simultaneous processing relationships, or names chargeback-ratio management or redundancy as their actual, stated reason for doing it.
This piece presents both explanations as plausible mechanisms consistent with how the regulatory and operational landscape actually works, not as documented merchant behavior.
What an Agent Should Do If a Prospect Already Runs Two Accounts
A prospect who mentions they already run two processing accounts is not necessarily divided in loyalty or hard to win. It is worth asking directly why, since the answer could reveal a chargeback-ratio concern worth addressing head-on in the pitch, or simply a redundancy habit that has nothing to do with pricing or service at all.
Either answer is more useful going into a pitch than assuming one reason without asking.
Sources
The external data in this article draws on the sources below. Figures described in the text as estimates or industry triangulations are directional and are not attributed to a single dataset.
- Chargebacks911, Visa Acquirer Monitoring Program (VAMP)
- Clearly Payments, What are reserves in payment processing?