What is Acquirer Monitoring Program (AMP)?

Understanding how AMP works isn't just helpful for compliance teams - it matters for anyone involved in merchant underwriting, risk management, or portfolio oversight. This post breaks down what the program monitors, how thresholds are calculated, when an acquirer is placed into the program, and what steps you can take to stay out of it altogether.

Why Payment Networks Put Acquirers in the Hot Seat

When a cardholder swipes their card at a business, the payment doesn't just travel from buyer to seller - it moves through a chain: the card network (like Visa or Mastercard), the issuing bank, and the acquiring bank. The acquirer is the financial institution that holds the merchant's account and processes their transactions.

The acquirer vouches for the merchant. When an acquirer onboards a business, they're basically telling the card network "we've checked this merchant out and we're responsible for how they behave." That's a big commitment, because card networks don't have a direct relationship with merchants - they only see what acquirers bring to the table.

That's why acquirers get held accountable when merchants cause problems. If a merchant racks up chargebacks, processes fraudulent transactions, or runs programs that break network rules, the damage flows upward. The acquirer is on the hook - not just financially, but reputationally too.

Card networks care about this because trust is the foundation of the whole payment system. A high volume of chargebacks or fraud doesn't just hurt one bank or one merchant - it erodes confidence in the network itself and pushes up costs for everyone involved, like banks and cardholders who had nothing to do with the problem.

So card networks created monitoring programs to watch acquirer portfolios for signs of trouble. The idea is to catch patterns early - before a cluster of bad merchants does damage to the network. Acquirers are expected to police their own portfolios, and when they don't, the monitoring programs bring that to light.

What makes this tough is that acquirers sometimes work with merchants in high-risk industries - travel, subscriptions, nutraceuticals - where chargebacks tend to show up more; that's not automatically a problem. But it does mean the acquirer needs to manage those portfolios and keep their numbers in check.

The monitoring programs are there to give acquirers a measurable standard to meet. Rather than leaving it vague, networks set thresholds for fraud ratios and chargeback rates across an acquirer's full book of business. I'll get into how those measurements work and where the lines are drawn.

How VAMP and ACMP Measure Risk - and When You Cross the Line

Visa overhauled its acquirer monitoring system on April 1, 2025. The old programs - VDMP (Visa Dispute Monitoring Program) and VFMP (Visa Fraud Monitoring Program) - were replaced by a single consolidated program called the Visa Acquirer Monitoring Program, or VAMP. The idea was to streamline how Visa tracks risk by combining fraud and dispute signals into one measurement.

VAMP pulls data from two event types. TC40 events are fraud reports filed by card-issuing banks when a cardholder says a transaction was unauthorized. TC15 events are dispute records. Visa adds these together each month to produce a combined event count for the acquirer.

To fall under VAMP scrutiny, an acquirer needs to hit at least 1,500 combined TC40 and TC15 events in a month. If that threshold is met, Visa then looks at the VAMP ratio - the percentage of transactions flagged - and anything at or above 2.2% puts the acquirer in the excessive tier; it's the number to watch.

Mastercard runs a separate system called the Acquirer Chargeback Monitoring Program, or ACMP - it works through two sub-programs that each address a different problem. The Excessive Chargeback Program (ECP) tracks acquirers whose merchants generate too many chargebacks relative to their total transactions. The Excessive Fraud Merchant program (EFM) focuses on fraud volume from specific merchants.

The two networks have different structures, but both point at the same thing - acquirers who aren't keeping their merchant chargeback ratios under control.

Here is a side-by-side look at how the two programs compare.

Detail	Visa (VAMP)	Mastercard (ACMP)
Program Name	Visa Acquirer Monitoring Program	Acquirer Chargeback Monitoring Program
Sub-Programs	None (consolidated)	ECP and EFM
Key Trigger	1,500+ combined TC40/TC15 events monthly	Excessive chargebacks or fraud per merchant
Excessive Threshold	2.2% VAMP ratio	Varies by sub-program
Launch / Structure	Launched April 1, 2025 (replaced VDMP and VFMP)	Ongoing, merchant-level focus

What Actually Happens After a Merchant Gets Flagged

Once a merchant crosses into the Standard or Excessive thresholds, Visa places them into the monitoring program and the clock starts ticking. The acquirer receives a formal notification, and from that point forward, the acquirer and the merchant are on a structured timeline to bring the numbers down.

The notification itself is the starting gun. A month-by-month review process follows where Visa tracks if the metrics are improving. If they are, the merchant can exit the program. If they are not, the consequences get heavier.

The most direct financial hit comes when a merchant reaches the Excessive tier. At that point, Visa applies a fine of $8 for every TC15 and TC40 data point counted in that month. That is not a flat monthly penalty - it scales with volume. A merchant processing thousands of transactions a month can accumulate a very large fine before they have resolved the root problem.

Acquirers carry responsibility here. Visa holds them accountable for their merchants' performance, so when a merchant is flagged, the acquirer has to show an active response. That usually means reaching out to the merchant, requesting a remediation plan, and tracking progress closely. Acquirers that seem to be passive or unresponsive face their own consequences from Visa.

That accountability creates direct pressure on merchants. Acquirers need the merchant to act - not just receive a notification. In practice, it will mean the acquirer sets internal deadlines, requests reporting, or places conditions on the merchant's continued access to card processing. In some situations, the acquirer may limit or suspend processing privileges entirely.

The escalation timeline varies by program tier and by whether it is VAMP or ACMP. But the general pattern is the same. Merchants who resolve the problem within the early months usually exit with fines and some remediation costs as their only damage. Merchants who remain in the Excessive category across multiple months face compounding fines and a much harder conversation with their acquirer.

The fines and the relationship pressure run in parallel, which is what makes the process high-stakes. There is no grace period where one waits for the other to resolve first.

The Levers Acquirers and Merchants Can Pull to Stay Compliant

Many merchants get flagged not because they're doing anything dishonest but because something in their process has a gap. Disputes aren't being tracked closely enough, or refunds are being handled in a way that confuses customers and gives you chargebacks. The good news is that most of these gaps are fixable.

For acquirers, it starts at onboarding. Underwriting a merchant well means understanding their business model, their expected transaction volumes, and whether their chargeback history from previous processors is clean. Catching a problem merchant before they're live is far easier than managing one who's already in a watching program.

Transaction monitoring is another layer that makes a difference. Acquirers who watch for unusual spikes in disputes or refund rates can reach out to a merchant early and work through what's going on before thresholds get crossed. This proactive contact is helpful because it gives merchants time to fix things without formal consequences.

On the merchant side, the most helpful steps are the easiest ones.

• Use clear billing descriptors so customers recognize the charge on their statement.
• Make it easy for customers to contact you directly before they go to their bank.
• Respond to disputes quickly and with the right documentation.
• Track your own chargeback and fraud ratios monthly so nothing creeps up on you.
• Review your refund policy and make sure it's visible and easy to understand.

Fraud detection tools also play a role here. Address verification, 3D Secure, and velocity checks all help cut back on fraudulent transactions before they cause chargebacks. These tools aren't foolproof, but they do lower the volume of disputes that come from unauthorized use.

Communication between acquirers and merchants matters more than most think. An acquirer who flags a trend early and works with the merchant to address it is doing something more helpful than one who waits for a program threshold to trigger. A merchant who is transparent about their dispute patterns is much easier to support through a rough patch.

The path to staying out of AMP is less about perfection and more about having systems in place to catch problems before they grow.

Staying Off the Radar Is a Team Sport

The merchants and acquirers who get through these programs best tend to have one thing in common: they don't wait for a warning letter to start paying attention. Regular review of chargeback ratios, the latest fraud tools, and open communication with your acquiring bank are habits that keep you off the radar. None of it requires a compliance team or a refined setup - just steady attention to the numbers that matter.

If you're not sure where you stand, that's a good place to start. Pull your recent dispute and fraud data, compare it against the thresholds for your relevant program, and have a conversation with your acquirer if anything looks close to the line. Acting early gives you options. Waiting until you're formally enrolled in a monitoring program means working under pressure, with fees and possible restrictions already in play.