Skip to main content

Merchant Monitoring

Last Updated: 2025-02-17 Status: Complete

Effective merchant monitoring is the foundation of PayFac risk management. Real-time dashboards, intelligent alerts, and automated actions help identify and address risk before it impacts network compliance.

Quick Reference

Monitoring AreaFrequencyAlert Threshold
Chargeback ratioDaily> 0.5%
Fraud rateDaily> 0.5%
Decline rateHourly> 30%
Transaction velocityReal-time3x normal
Health scoreDaily< 70

Monitoring Architecture

Key Metrics to Monitor

Chargeback Metrics

MetricCalculationTargetCritical
Chargeback ratioChargebacks / Transactions< 0.5%> 1.0%
Chargeback countRaw count per periodContext> 100/month
Chargeback trendWeek-over-week changeDeclining+25%
Win rateRepresentments won / Total> 40%< 20%

Fraud Metrics

MetricCalculationTargetCritical
Fraud rateFraud chargebacks / Transactions< 0.5%> 1.0%
Fraud amountDollar value of fraudContext> $50K/month
3DS adoption3DS transactions / Total> 80%< 50%
Authorization fraudFraud / Authorizations< 0.1%> 0.5%

Operational Metrics

MetricCalculationTargetCritical
Decline rateDeclines / Auth attempts< 20%> 35%
Refund rateRefunds / Transactions< 5%> 15%
AVS mismatch rateAVS failures / Total< 10%> 25%
CVV mismatch rateCVV failures / Total< 5%> 15%

Volume Metrics

MetricCalculationTargetCritical
Daily volumeTransactions per dayBaseline> 3x normal
Average ticketTotal $ / Transaction countStable> 2x normal
Peak hour ratioPeak volume / Average< 3x> 5x
New customer rateFirst-time / TotalContextSudden spike

Alert Configuration

Alert Levels

Alert Thresholds by Metric

MetricWarningElevatedCritical
Chargeback ratio> 0.5%> 0.75%> 1.0%
Fraud rate> 0.5%> 0.75%> 1.0%
Decline rate> 25%> 30%> 40%
Volume spike> 2x> 3x> 5x
Health score< 80< 70< 50

Alert Actions

Alert LevelNotificationAutomated Action
WarningEmail to merchantNone
ElevatedEmail + SMS to merchant + PayFac opsIncrease monitoring
CriticalImmediate page to ops teamConsider suspension

Merchant Health Score

A composite score that aggregates multiple risk factors into a single metric.

Score Components

ComponentWeightDescription
Chargeback ratio25%Current month ratio
Chargeback trend15%30-day trend direction
Fraud rate20%Fraud as % of transactions
Operational stability15%Decline rate, refunds
Account age10%Time since onboarding
Historical performance15%6-month average

Score Calculation

Score Interpretation

Score RangeCategoryAction
90-100ExcellentStandard monitoring
80-89GoodStandard monitoring
70-79FairIncreased monitoring
60-69ConcerningMonthly review, consider reserve
50-59PoorWeekly review, increase reserve
< 50CriticalImmediate action required

Dashboard Design

Operations Dashboard

┌─────────────────────────────────────────────────────────────┐
│ PORTFOLIO OVERVIEW [Live] ⚡ │
├─────────────┬─────────────┬─────────────┬───────────────────┤
│ Merchants │ CB Ratio │ Fraud Rate │ At Risk │
│ 2,847 │ 0.42% │ 0.38% │ 23 │
│ ↑ 12 today │ ↓ 0.02% │ → stable │ ↑ 3 │
├─────────────┴─────────────┴─────────────┴───────────────────┤
│ ALERTS (12 active) │
│ ⚠️ MID-12345: CB ratio 0.95% - Critical │
│ ⚠️ MID-67890: Volume spike 4.2x - Elevated │
│ ⚠️ MID-11111: Health score 62 - Concerning │
├─────────────────────────────────────────────────────────────┤
│ TRENDING ISSUES │
│ 📈 Fraud up 15% WoW across electronics category │
│ 📉 CB down 8% after 3DS rollout │
└─────────────────────────────────────────────────────────────┘

Merchant Detail View

┌─────────────────────────────────────────────────────────────┐
│ MERCHANT: Example Store (MID-12345) │
│ Health Score: 68 ⚠️ Status: Under Review │
├─────────────────────────────────────────────────────────────┤
│ KEY METRICS (Last 30 Days) │
│ ┌───────────────────────────────────────────────────────┐ │
│ │ CB Ratio: 0.95% ████████████████████░░░░ Target: 0.5% │ │
│ │ Fraud: 0.42% ████████████░░░░░░░░░░░░ Target: 0.5% │ │
│ │ Declines: 22% ████████████████░░░░░░░░ Target: 20% │ │
│ └───────────────────────────────────────────────────────┘ │
├─────────────────────────────────────────────────────────────┤
│ CHARGEBACK TREND │
│ ▲ │
│ 1.0% │ ╱──● │
│ 0.8% │ ●───●╱ │
│ 0.6% │ ●──● │
│ 0.4% │● │
│ └────────────────────────────────▶ │
│ W1 W2 W3 W4 Now │
├─────────────────────────────────────────────────────────────┤
│ ACTIONS │
│ [Request Documentation] [Increase Reserve] [Suspend] │
└─────────────────────────────────────────────────────────────┘

Automated Actions

Action Triggers

TriggerConditionAutomated Action
CB spike> 1.5% single dayPause payouts
Fraud spike> 2% single daySuspend processing
Volume spike> 5x normalQueue for review
Health dropScore drops > 20 ptsNotify ops team
Network threshold> 90% of VAMP/ECPEscalate to management

Action Workflow

Payout Controls

Merchant StatusPayout TimingHold Amount
NormalStandard (T+2)None
WarningStandardNone
ElevatedDelayed (T+5)None
CriticalDelayed (T+10)10% reserve
SuspendedHeld100% hold

Investigation Workflow

Triggered Investigation

Investigation Checklist

StepActionDocumentation
1Review recent transactionsTransaction log
2Analyze chargeback reasonsReason code breakdown
3Check for fraud patternsFraud report
4Review customer complaintsSupport tickets
5Verify business operationsMerchant interview
6Assess remediation optionsAction plan

False Positive Management

Common False Positives

ScenarioTriggerResolution
Seasonal spikeVolume exceeds thresholdAdjust baseline seasonally
New product launchSudden volume increasePre-notify before launch
Batch processingSingle large transactionConfigure batch alerts
Legitimate high-ticketAverage ticket spikeCategory-appropriate thresholds

Tuning Recommendations

MetricAdjustment Approach
VolumeUse rolling 90-day baseline
Ticket sizeIndustry-specific thresholds
Decline rateAccount for new customer rate
SeasonalApply seasonal adjustment factors

References

Share: