Skip to content

PSP operations

Merchant Monitoring for PSPs: Risk, Chargebacks and VAMP

Approval is a prediction, and merchant monitoring checks whether it was right. A merchant that looked fine at onboarding can change products, double its volume overnight or start drawing disputes, and the PSP carries the cost if it can't pay them.

Card schemes watch too. Visa measures fraud and disputes for every acquirer's portfolio each month, so a PSP's weakest merchants become its acquirer's problem, and then the PSP's. This page covers what to watch, how Visa's thresholds work, and what a monitoring program does when a merchant crosses a line.

What merchant monitoring watches

Each signal compares what a merchant is doing now with what it said it would do, or with what it did last month. The table lists the ones most monitoring programs track.

Signal Example trigger What it can mean
Volume against expectation Monthly volume twice the figure given at onboarding Growth, or a merchant processing for someone else
Average ticket Ticket size triples in a week A product change the PSP didn't approve
Fraud and dispute ratio Ratio climbing toward a scheme threshold Weak fraud controls or unhappy customers
Refund rate Refunds rising faster than sales Delivery problems ahead of chargebacks
Decline rate Many declines on small amounts Card testing through the merchant's checkout
New countries or card ranges Sudden traffic from markets the merchant doesn't serve Fraud, or an unreported change of business
Category drift The website now sells something else The merchant category code no longer fits

No single signal proves anything. Two or three moving together usually do, and merchant risk monitoring that catches them early works on combinations of rules rather than one threshold at a time, which is what real-time merchant monitoring means in practice.

Visa's VAMP ratio and thresholds

Visa's Acquirer Monitoring Program, VAMP, combines fraud and disputes into one count-based ratio on card-not-present transactions. Its fact sheet defines the VAMP ratio as the count of fraud reports (TC40) plus disputes (TC15), divided by the count of settled transactions (TC05).

The thresholds work at two levels. An acquirer's whole portfolio is Above Standard at a ratio of 50 basis points or more and Excessive at 70 or more. A single merchant becomes an Excessive Merchant in Asia-Pacific, Canada, the EU and the US at 150 basis points with at least 1,500 fraud and dispute counts a month, a threshold Visa lowered from 220 basis points on April 1, 2026.

Other regions differ. In Latin America the merchant threshold is 150 basis points, and in CEMEA it's 220 basis points with at least 150 counts and USD 75,000 a month.

A worked VAMP example

Take a hypothetical EU merchant with 120,000 settled card-not-present transactions in a month. It gets 2,000 counts. That's 1,300 fraud reports and 700 disputes, the kind of mix a merchant sees when a wave of stolen cards hits its checkout in the same month that a delivery delay sends customers to their banks.

Its VAMP ratio is 2,000 / 120,000 = 1.67%, or about 167 basis points. With at least 1,500 counts, that's above the 150-point merchant threshold. Cut disputes to 300 through refunds and better descriptors, and the ratio falls to 1,600 / 120,000 = 1.33%, back under the line. The fraud reports alone, 1,300, were already close to the count minimum, so fraud controls matter as much as dispute handling here.

A merchant monitoring program: the action ladder

Monitoring is only useful if each alert leads to a defined response. A merchant monitoring program usually escalates in steps, from the lightest action to the heaviest.

  1. Alert the risk team and record the trigger.
  2. Contact the merchant and ask what changed.
  3. Lower volume or ticket limits while the review runs.
  4. Raise the rolling reserve or delay payouts.
  5. Suspend processing.
  6. Terminate the merchant and keep the evidence.

Write down which signals jump straight to step 4 or 5. A merchant showing card testing on its checkout shouldn't wait for a phone call before limits change.

Merchant risk management software

Spreadsheets can't watch a portfolio in real time, so this is where software matters most. Our merchant management system watches each merchant's transactions as they happen, flagging unusual spikes and threshold breaches, and it tracks chargeback ratios so your team can act before they reach penalty thresholds.

Merchants are reassessed as their behavior and volumes change, and their category codes stay current for risk and pricing. Rules and alerts are yours to configure, and the evidence of every check stays in the system for audits, alongside the reserves and holdbacks that underwriting set.

Questions

What is merchant monitoring?

It's the ongoing review of a merchant's transactions and disputes after approval, so a PSP can spot rising risk and act before losses arrive.

What is the VAMP ratio?

Visa's count of fraud reports plus disputes, divided by the count of settled card-not-present transactions, measured each month for acquirers and for individual merchants.

What's Visa's excessive merchant threshold in 2026?

In Asia-Pacific, Canada, the EU and the US, a VAMP ratio of 150 basis points or more with at least 1,500 fraud and dispute counts a month, since April 1, 2026.

What should merchant risk management software do?

Watch transactions in real time, compare fraud and dispute ratios with scheme thresholds, alert the risk team on rule breaches, reassess merchants as they change, and keep the evidence for audits.

Set up monitoring rules with us

Bring the thresholds your acquirer works to, and we'll show them as alerts and actions on the platform.