How to Monitor VAMP and Payment Performance in Threshold Defense™

Card networks measure merchants continuously, whether or not the merchant is watching. Threshold Defense™ helps merchants review the activity those measurements are built from — fraud reports, disputes, settled volume, approvals, and declines — in one monitoring workflow. This reference explains what to review, how the data areas relate, and where internal monitoring ends and official network measurement begins.

What Threshold Defense™ Helps Merchants Monitor

Threshold Defense™ helps merchants review fraud, dispute, volume, approval, and decline information together, across merchant IDs, processor relationships, gateway relationships, regions, and business lines. Reviewing these together matters because monitoring programs such as the Visa Acquirer Monitoring Program measure combined activity against transaction volume — a merchant that watches only its processor's chargeback report can drift toward program attention without seeing it coming.

Before You Review Payment Performance

Decide the review cadence up front. The measurements move monthly, so a monthly review with a mid-month check is a reasonable baseline for most merchants.

Review Settled Transaction Volume

Start with the denominator. Review settled Visa card-not-present volume and overall settled transaction counts for each merchant account. Volume is the base of every ratio, so a drop in settled volume can worsen ratios without any new risk activity — seasonal dips, paused campaigns, and processor migrations all change ratio math.

Review Fraud and Dispute Activity

Review reported-fraud activity and dispute activity together. On the Visa network these are different records: the TC40 fraud report records a fraud claim, and the TC15 dispute records a dispute. Count-based measurement means every record matters equally regardless of amount. Include pre-dispute resolutions and chargeback reason codes in the review — the reason-code mix often shows which business practice is generating the activity.

Compare TC40 and TC15 Trends

Compare TC40 fraud reports and TC15 disputes as separate trends. The two records represent different events and do not always move together: reported fraud can climb while chargebacks stay flat, and vice versa. A merchant that tracks only one of the two sees only part of the activity that network monitoring counts.

Review Approval and Decline Activity

Threshold health is not only about disputes. Review the payment approval rate and payment decline responses for each account. A falling approval rate can indicate rising issuer caution, upstream fraud controls reacting to your traffic, or technical problems in the payment flow — and decline trends often move before dispute trends do.

Compare Merchant Accounts and Processors

Break every data area down by merchant ID, processor, gateway, region, and business line. Concentration is diagnostic: one MID or one region driving the numbers points to a specific cause, while an even rise across accounts suggests something broader in the product or traffic mix.

Investigate Sudden Changes

Investigate any sudden movement before interpreting it. Check whether volume, traffic, or product mix changed at the same time, whether one account or channel explains the shift, and whether a payment-flow change lines up with a decline spike. A ratio that moved because the denominator fell is a different problem from one that moved because disputes rose.

Build a Consistent Monitoring Routine

Review the same measures, on the same cadence, for every account: settled volume, fraud-report counts, dispute counts, the combined trend against volume, approval rate, and decline mix. Record the monthly readings so direction is visible across quarters. Consistency is what turns monitoring into early warning — for current thresholds and regional details, keep the current Visa Acquirer Monitoring Program guide and the 2026 VAMP monitoring checklist in the routine.

Questions to Ask Your Acquirer or Processor

• Which monitoring measurements do you track for our accounts, and how often?
• How does our reported fraud and dispute activity compare with the applicable program levels?
• Are any of our merchant IDs approaching a monitoring program level?
• Which exclusions or timing rules currently apply to how our activity is counted?
• What remediation steps would you expect if our activity kept rising?

Important VAMP Limitations

VAMP thresholds and exclusions can change, and current figures are intentionally not repeated in this article — use the linked program guide for current details, and confirm current status with your acquirer, processor, or Visa representative. Treat internal monitoring as directional early warning, not an official determination.

When to Contact Payment Defender Support

If combined fraud-and-dispute activity is trending toward program levels, an acquirer or processor has flagged an account, or monitoring shows a trend you cannot trace to a cause, contact Payment Defender Support with the merchant account, the time period, and the trend you are seeing. To work the fraud-report side of the picture in detail, review fraud activity in Fraud Signal™.