What Merchant Account Management Actually Covers · Midcore Operations
Midcore Operations
Managed Payments Operations

What Merchant Account Management Actually Covers

Visa tests every acquirer's portfolio against one published ratio each month. Merchant account management exists to stay ahead of that number.

Published
4 November 2026
Reading time
9 min read
Author
Managed Payments Operations practice
Topic
Managed Payments Operations
Key takeaways
  • Visa's Acquirer Monitoring Program tests a single published ratio, fraud and disputes divided by settled transactions, against each acquirer's whole portfolio and against every individual merchant inside it. A processor risk inquiry is usually just this number crossing a line someone was not watching.
  • Visa Core Rules Section 1.1.8.1 makes the acquiring Member, not the merchant, solely responsible to Visa for a merchant's activity and requires the Member to indemnify Visa for claims arising from it. That liability, not customer service, is why an acquirer monitors and reserves against merchant risk proactively.
  • The Excessive Merchant threshold in the US, Canada, the EU, and the AP region dropped from 220 basis points to 150 basis points on April 1, 2026. A monitoring program built around last year's number is now flagging merchants later than Visa actually will.
  • A separate enumeration ratio, measuring card-testing attacks rather than confirmed fraud or disputes, carries its own threshold and its own 300,000 transaction count trigger. A program that only reviews the fraud and dispute ratio monthly can miss an enumeration spike that builds in days.

What merchant account management actually covers starts with a number most merchants never see and most platforms never calculate correctly: the ratio of fraud and disputes to settled transactions that Visa recalculates for every acquirer, and every merchant inside that acquirer’s portfolio, every single month. A processor risk inquiry rarely shows up as a surprise to the team actually running that calculation. It shows up as a surprise to everyone else.

The ratio that actually drives the risk inquiry

Visa’s Acquirer Monitoring Program, VAMP, consolidated what used to be three separate programs, the Acquirer Monitoring Program, the Fraud Monitoring Program, and the Dispute Monitoring Program, into one global metric. The VAMP ratio is defined as the count of card-not-present fraud transactions and disputes divided by the count of settled transactions on VisaNet, domestic and cross-border combined. Visa runs this calculation every month, at two levels: the acquirer’s entire portfolio, and each individual merchant inside it.

At the portfolio level, an acquirer is identified as Above Standard once its VAMP ratio reaches 50 basis points. It is identified as Excessive once that ratio reaches 70 basis points. Both designations also require the portfolio to clear a minimum monthly count of fraud and disputes before Visa applies them. Below that portfolio-level designation, Visa applies a separate Excessive Merchant threshold to individual accounts. A merchant whose own ratio crosses that line, while the acquirer’s broader portfolio has not, still gets flagged individually. This is the mechanism behind nearly every processor risk inquiry that lands on an account manager’s desk asking for an explanation of a specific merchant’s recent activity.

What a portfolio-wide flag actually requires, not just a single account

An acquirer whose entire portfolio crosses the Above Standard or Excessive designation faces a different consequence than a single flagged merchant. Visa’s own program materials state that an entity identified as exceeding program thresholds is required to implement risk mitigation control measures, and at the portfolio level that requirement applies across the acquirer’s full book of merchants, not to one account in isolation. This is why a monitoring program built only around individual merchant accounts misses half the picture. A portfolio can drift toward the 50 or 70 basis point line gradually, through a slow accumulation of smaller fraud and dispute increases spread across dozens of merchants, none of which individually crosses the Excessive Merchant threshold on its own. Monitoring only at the merchant level, account by account, can miss that aggregate drift entirely until Visa’s own monthly calculation flags the whole portfolio at once, at which point the required mitigation plan has to address every merchant in the book, not just the one or two that would have shown up on an account-level review.

Why the acquirer carries this risk, not the merchant

The reason merchant account management exists as a continuous function, rather than a response team that activates when Visa calls, sits in a single rule most merchants have never read. Visa Core Rules Section 1.1.8.1, Taking Responsibility, states that each Member is solely responsible for its acquiring of merchants to accept Visa products. That responsibility includes settlement of transactions and compliance with Visa’s rules. Each Member must also indemnify Visa for claims and liabilities arising from that acquiring activity.

A merchant has no direct contractual relationship with Visa. The acquiring Member does, and that Member is the party Visa holds accountable, financially and contractually, for everything that merchant does on the network. This is precisely why reserves, holds, and ongoing documentation requirements exist. They are not a customer service posture the acquirer chooses to adopt. They are a direct response to a liability structure the acquirer cannot negotiate away. An acquirer that waits for Visa’s monthly VAMP calculation to surface a problem is choosing to discover its own liability exposure a full reporting cycle after that exposure started accumulating.

What changed on April 1, 2026, and why a stale number is dangerous

Visa’s own program documentation makes clear that these thresholds are not fixed. The Excessive Merchant VAMP ratio threshold for the AP, Canada, EU, and US regions was 220 basis points through March 2026. Visa’s program materials state plainly that this threshold dropped to 150 basis points effective April 1, 2026. That brings it in line with the threshold already in place for the LAC region. The CEMEA region’s threshold, 220 basis points with its own minimum count and dollar volume trigger, was not part of that change.

A merchant account management process may still calculate its own internal warning threshold against the old 220 basis point figure. In any region where that number changed, this is not a conservative choice. It is measuring against a number Visa stopped using months ago. A merchant sitting comfortably under an internal 200 basis point alert line, built on the outdated threshold, could already be above the 150 basis point line that actually determines whether Visa flags the account. The gap between the old number and the new one is exactly the range in which a portfolio manager believes an account is safe while Visa’s own system does not.

The enumeration problem moves on a different clock

The VAMP ratio is not the only metric Visa monitors, and it is not the fastest-moving one. A separate enumeration ratio tracks card-testing attacks: the practice of running large volumes of guessed or stolen card numbers against a merchant’s checkout to find which ones are valid. It carries its own threshold entirely independent of fraud or dispute activity. Visa defines the enumeration ratio as the count of enumerated authorization transactions, approved and declined combined, divided by the count of all authorization transactions. That ratio carries a threshold of 2,000 basis points. A separate trigger applies based on raw volume: 300,000 enumerated transactions in a month, regardless of ratio.

Fraud and dispute activity accumulates over weeks before it shows up meaningfully in a monthly VAMP ratio calculation. An enumeration attack can generate the volume needed to cross that 300,000 transaction count trigger within days, sometimes within hours, because it is an automated script hammering a checkout endpoint rather than a slow drift in customer behavior. A monitoring process built entirely around a monthly review of the fraud and dispute ratio will see an enumeration spike only after it has already run its full course, well past the point where faster intervention would have mattered.

A concrete example: the same ratio, two different outcomes

Picture two merchants in the same card-not-present vertical, each processing a similar volume, each sitting at roughly 140 basis points on their own VAMP ratio as of March 2026. The first merchant’s account manager is tracking the actual current thresholds and flags the account as approaching the US region’s new 150 basis point Excessive Merchant line before April 1 arrives, building a mitigation plan, tightening fraud rules, reviewing refund policy, enrolling in a dispute alert service, ahead of the deadline.

The second merchant’s account manager is still working from an internal rule of thumb built around the old 220 basis point threshold and sees a comfortable 80 basis point cushion that no longer exists. When the new threshold takes effect, that merchant crosses into Excessive Merchant status on day one of the new standard, with no mitigation plan in place and a processor risk inquiry already in its account manager’s inbox. Both merchants had the same ratio. Only one had a monitoring process actually calibrated to the number Visa was going to use.

What this actually means for running a merchant portfolio

Merchant account management that is built around this reality looks different from a general account health dashboard. It tracks each merchant’s VAMP ratio against the threshold that currently applies in that merchant’s specific region, not a single global number, because the AP, Canada, EU, US, LAC, and CEMEA thresholds are not identical and do not change on the same schedule. It tracks the enumeration ratio and raw enumerated transaction count separately from fraud and dispute activity, on a cadence fast enough to catch an attack that can cross its 300,000 transaction trigger in days rather than weeks.

It treats a processor risk inquiry as confirmation of something the monitoring process should have already flagged internally, not as the first signal that a problem exists. And it understands why any of this is the acquirer’s job to track proactively in the first place: Visa Core Rules Section 1.1.8.1 puts the liability for a merchant’s activity on the acquiring Member, not on the merchant and not on Visa, which makes continuous portfolio monitoring a direct response to real financial exposure rather than an optional service tier.

Building that monitoring discipline across an entire merchant portfolio, tracking the right ratio against the right regional threshold before Visa’s own calculation forces the issue, is exactly the ongoing work behind Midcore’s merchant management practice. Where the underlying driver is fraud and dispute activity specifically, fraud and chargeback prevention is where the controls that actually lower a merchant’s VAMP ratio get built and tuned. And for a portfolio growing across multiple MIDs or processors at once, keeping threshold tracking consistent account by account is exactly the discipline behind multi-MID setup and management, so a threshold change in one region does not quietly slip past an account sitting under a different processor relationship.

Frequently Asked Questions

What is the VAMP ratio, and why does it matter to merchant account management?

The VAMP ratio is Visa’s core monitoring metric: the count of card-not-present fraud and dispute transactions divided by the count of settled transactions, measured monthly for each acquirer’s portfolio and for each merchant inside it. Crossing the published threshold is what actually triggers the processor risk inquiry, document request, or reserve action that merchant account management exists to anticipate and resolve, rather than react to after the fact.

Why does Visa hold the acquirer responsible instead of going directly to the merchant?

Visa Core Rules Section 1.1.8.1 states that each Member is solely responsible for its acquiring of merchants, including responsibility for settlement of transactions and compliance with Visa’s rules, and must indemnify Visa for claims arising from that activity. The merchant has no direct contractual relationship with Visa. The acquirer carries that liability, which is why the acquirer, not Visa, is the one monitoring volume, ratios, and documentation on every account in its portfolio.

Did the merchant monitoring thresholds actually change recently?

Yes. Visa’s own program documentation sets the Excessive Merchant VAMP ratio threshold at 220 basis points for the AP, Canada, EU, and US regions through March 2026, then states that threshold drops to 150 basis points effective April 1, 2026. A portfolio monitoring process still using the older 220 basis point figure is applying a threshold Visa itself no longer uses in those regions.

Sources: Visa Acquirer Monitoring Program Overview and Visa Core Rules and Visa Product and Service Rules, Section 1.1.8.1.

Managed Payments Operations practiceMidcore Operations · 4 November 2026
All insights
Free consultation

Get your free Assess

Tell us what is happening. We reply within one business day with a US-based practice lead, not a salesperson.

  1. 01Within 1 business dayA US-based practice lead replies and books a 30 minute call.
  2. 02On the callWe map the problem, the volume, the partners, and the constraints.
  3. 03After the callYou get a written read of one to three pages, yours to keep.
  • Handled under NDA
  • Written, not a slide deck
  • No obligation to continue

No obligation. We will tell you if you do not need us.

Before you go

Take the written read with you

Every engagement opens with an Assess: a written read of what is happening, what it costs, and what to do about it. It is quoted on its own and you can stop after it.

+1 (786) 619-0152