Skip to main content

Operations Checklist

TL;DR
  • Daily (5-15 min): Auth rate, failed transactions, chargeback queue, fraud queue, deposits
  • Weekly (30-45 min): Chargeback ratio trend, win rate, fraud rate by channel, refunds, processor emails
  • Monthly (1-2 hr): Statement review, effective rate, reason code breakdown, rule performance
  • Oh shit triggers: Checkout failures, approval or dispute spikes beyond your set alerts, processor "review" email, unexplained payout delay
  • Scale: Solo operators just check CB count weekly and respond to disputes before expiry

If you process under 100 orders a day, the daily check is a 5-minute dashboard glance. It's the weekly rhythm that matters, not the daily noise.

Minimum Viable Version

Solo operators: Check your chargeback count weekly, respond to disputes before they expire, and verify deposits hit your bank. Everything else can wait until you're bigger.

Daily Checks (5-15 minutes)​

Skip these if you're under 100 orders/day. Look at the weekly pattern instead.

CheckWhat You're Looking ForTime
Auth approval rateDrop beyond your alert setting on comparable traffic2 min
Failed transactionsPatterns in decline codes2 min
Chargeback queueNew disputes to respond to3 min
Fraud queueFlagged orders awaiting review5 min
Deposit verificationYesterday's batch hit the bank2 min

Sample size matters: if you only had 20 orders yesterday, one decline moves your rate 5%. That isn't a signal. Look at the weekly pattern.

Traffic Light Thresholds (Daily)​

MetricGreenYellowRed
Auth rateStable on comparable trafficChange beyond your investigation settingConfirmed checkout failures or your rollback limit crossed
Fraud queueWork can clear before fulfillmentOldest cases nearing your review deadlineCases will miss that deadline without help
Failed authsStable by issuer and transaction typeUnexplained increase in a segmentWidespread failures confirmed by logs or customer reports

Weekly Checks (30-45 minutes)​

This is where the real patterns show up.

CheckWhat You're Looking ForTime
Chargeback ratioTrend against your processor's written limit5 min
Dispute win rateTracking representment success5 min
Fraud rate by channelWhich traffic sources are risky10 min
Refund rateUnusual spikes (product issues?)5 min
Processor communicationsAny emails you missed5 min
Payout reconciliationAll expected funds received10 min

Traffic Light Thresholds (Weekly)​

MetricGreenYellowRed
Chargeback ratioStable trend, below your processor's limitRising toward your limitWarning received or limit breached
Mastercard fraud chargebacks / prior-month Mastercard sales countStable against your baselineRising toward the applicable EFM testsProcessor warning or applicable entry tests met; check the regional count, amount and 3DS conditions here
Dispute win rateAt or above your own baselineFalling on one reason codeFalling across reason codes
Refund rateStable against your own baseline by product and channelRising against that baselineRising while chargebacks rise
Use Your Processor's Written Limit

Set your chargeback alerts against that limit, with time to respond. Ask: "What's my limit, how's it calculated, and when will you contact me?" See Thresholds. Network programs have separate ratio and count tests:

  • Visa VAMP (effective April 2025): combines fraud reports and disputes, with exclusions. Merchant tests depend on region and acquirer status. Check Network Programs for the full conditions.
  • Mastercard ECM enforcement starts at 100-299 chargebacks and a 1.50-2.99% ratio, in the same month

Don't wait for program enrollment to fix a rising ratio. Once you're in a monitoring program, you face monthly fines, mandatory remediation plans, and potential MATCH listing. See Dispute Monitoring Programs for the full breakdown.

Monthly Checks (1-2 hours)​

CheckWhat You're Looking ForTime
Processor statement reviewFee changes, rate creep20 min
Effective rate calculationStaying competitive10 min
Chargeback reason code breakdownWhat's driving disputes15 min
Rule performance reviewRules with rising blocks, losses or blocked good orders20 min
Velocity threshold reviewStill appropriate for volume?15 min
Reserve/holdback statusWhen funds release10 min

Rule Performance Red Flags​

Review rules when their share of attempts or total blocks changes on comparable traffic. Check the orders and confirmed outcomes before tightening or removing anything. Set a review trigger that catches changes your team can investigate, and use Fraud Metrics for the definitions.

Oh Shit Triggers​

Stop what you're doing and investigate immediately:

TriggerWhat It MeansFirst Action
Auth rate crosses your urgent alert on comparable trafficPossible processor or checkout issueCheck processor status page, test a transaction
Chargebacks cross your count alertPossible attack or product issuePull the orders, look for patterns
Processor emails about "review" or "risk"They're nervous about youReply within 2 hours, even if just "received, investigating"
Payout delayed without explanationThey're holding your moneyCall (don't email) and ask for risk/underwriting
Chargeback ratio approaches your processor's limitTime to act before a breachSee Reduce Chargebacks Fast
Multiple R10 returns (ACH)Someone claimed unauthorizedStop debiting that customer, investigate immediately

Checklist by Team Size​

Solo Operator (No Dedicated Payments Person)​

Daily: Glance at dashboard for anything obviously wrong. 2 minutes.

Weekly:

  • Check chargeback count (not ratio, just count)
  • Respond to any open disputes
  • Verify week's deposits
  • Read any processor emails

Monthly:

  • Calculate effective rate from statement
  • Review chargeback reasons
  • Check if reserve is releasing on schedule

Small Team (1-2 People Touch Payments)​

Daily:

  • Review fraud queue
  • Check for new disputes
  • Verify deposits

Weekly:

  • Full metrics review (chargebacks, fraud, auth rate)
  • Processor communication review
  • Reconciliation check

Monthly:

  • Statement deep dive
  • Rule performance review
  • Threshold adjustments

Medium Team (Dedicated Fraud/Payments Person)​

Add to the above:

Daily:

  • Auth rate monitoring with alerts
  • Fraud queue SLA tracking
  • Shift handoff notes

Weekly:

  • Cross-functional sync (fraud + support + finance)
  • Vendor performance review
  • Channel-level fraud breakdown

Monthly:

  • Vendor contract review
  • Threshold tuning session
  • Competitive rate check

Monthly Experiments​

Pick one experiment each month. Don't do more than one at a time (you can't measure what worked).

Experiment ideas:

  • Tighten one fraud rule, measure CB impact for 30 days
  • Change refund policy for one product category, measure dispute rate
  • Test new billing descriptor wording, compare recognition rates
  • Add delivery photos to representment packets, measure win rate change
  • Change retry timing for declined recurring payments, measure recovery rate

Template:

Month: ___________
Experiment: ___________
Hypothesis: ___________
Metric: ___________
Result: ___________
Keep/Kill: ___________

Where This Breaks​

Flash sales and promotions: your normal thresholds will throw false positives. Either adjust them beforehand or have someone ready to approve flagged orders fast, because they won't wait.

Seasonal businesses: Weekly patterns are useless if you do 80% of volume in Q4. Build seasonal baselines.

New product launches: Expect elevated chargebacks 30-45 days after launch as customers receive products and decide they're not happy.

International expansion: Time zones mess with daily monitoring. A "spike" at 3am your time is somebody's normal business hours.

Next Steps​

Solo operator?

  1. Use minimum viable checklist - CB count, disputes, deposits
  2. Know oh shit triggers - When to drop everything
  3. Monthly statement review - Effective rate, reason codes

Building operations routine?

  1. Set up daily checks - Auth rate, fraud queue, deposits
  2. Establish weekly cadence - Ratios, win rate, reconciliation
  3. Configure alerts - Automate what you can

Scaling team?

  1. Match checks to team size - Solo vs small vs medium
  2. Run monthly experiments - One at a time, measure impact
  3. Account for edge cases - Flash sales, seasonal, international

Something wrong on this page? Email matt at paymentsandrisk.com and say what needs fixing.