# Operations Checklist
Source: https://paymentsandrisk.com/docs/operations/checklist

Last updated 22 October 2026.

TL;DR

-   **Daily (5-15 min)**: [Auth rate](https://paymentsandrisk.com/docs/payments/metrics/), 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.

| Check | What You're Looking For | Time |
| --- | --- | --- |
| Auth approval rate | Drop beyond your alert setting on comparable traffic | 2 min |
| Failed transactions | Patterns in decline codes | 2 min |
| Chargeback queue | New disputes to respond to | 3 min |
| Fraud queue | Flagged orders awaiting review | 5 min |
| Deposit verification | Yesterday's batch hit the bank | 2 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)

| Metric | Green | Yellow | Red |
| --- | --- | --- | --- |
| Auth rate | Stable on comparable traffic | Change beyond your investigation setting | Confirmed checkout failures or your rollback limit crossed |
| Fraud queue | Work can clear before fulfillment | Oldest cases nearing your review deadline | Cases will miss that deadline without help |
| Failed auths | Stable by issuer and transaction type | Unexplained increase in a segment | Widespread failures confirmed by logs or customer reports |

## Weekly Checks (30-45 minutes)

This is where the real patterns show up.

| Check | What You're Looking For | Time |
| --- | --- | --- |
| Chargeback ratio | Trend against your processor's written limit | 5 min |
| Dispute win rate | Tracking representment success | 5 min |
| Fraud rate by channel | Which traffic sources are risky | 10 min |
| Refund rate | Unusual spikes (product issues?) | 5 min |
| Processor communications | Any emails you missed | 5 min |
| Payout reconciliation | All expected funds received | 10 min |

### Traffic Light Thresholds (Weekly)

| Metric | Green | Yellow | Red |
| --- | --- | --- | --- |
| Chargeback ratio | Stable trend, below your processor's limit | Rising toward your limit | Warning received or limit breached |
| Mastercard fraud chargebacks / prior-month Mastercard sales count | Stable against your baseline | Rising toward the applicable EFM tests | Processor warning or applicable entry tests met; check the regional count, amount and 3DS conditions [here](https://paymentsandrisk.com/docs/chargebacks/reference/network-programs/#efm-enrollment-criteria) |
| Dispute win rate | At or above your own baseline | Falling on one reason code | Falling across reason codes |
| Refund rate | Stable against your own baseline by product and channel | Rising against that baseline | Rising 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](https://paymentsandrisk.com/docs/chargebacks/monitoring/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](https://paymentsandrisk.com/docs/chargebacks/reference/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](https://paymentsandrisk.com/docs/chargebacks/match-tmf/). See [Dispute Monitoring Programs](https://paymentsandrisk.com/docs/compliance/network-rules/dispute-monitoring/) for the full breakdown.

## Monthly Checks (1-2 hours)

| Check | What You're Looking For | Time |
| --- | --- | --- |
| Processor statement review | Fee changes, rate creep | 20 min |
| Effective rate calculation | Staying competitive | 10 min |
| Chargeback reason code breakdown | What's driving disputes | 15 min |
| Rule performance review | Rules with rising blocks, losses or blocked good orders | 20 min |
| Velocity threshold review | Still appropriate for volume? | 15 min |
| Reserve/holdback status | When funds release | 10 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](https://paymentsandrisk.com/docs/fraud/metrics/) for the definitions.

## Oh Shit Triggers

Stop what you're doing and investigate immediately:

| Trigger | What It Means | First Action |
| --- | --- | --- |
| Auth rate crosses your urgent alert on comparable traffic | Possible processor or checkout issue | Check processor status page, test a transaction |
| Chargebacks cross your count alert | Possible attack or product issue | Pull the orders, look for patterns |
| Processor emails about "review" or "risk" | They're nervous about you | Reply within 2 hours, even if just "received, investigating" |
| Payout delayed without explanation | They're holding your money | Call (don't email) and ask for risk/underwriting |
| Chargeback ratio approaches your processor's limit | Time to act before a breach | See [Reduce Chargebacks Fast](https://paymentsandrisk.com/docs/playbooks/reduce-chargebacks-fast/) |
| Multiple R10 returns (ACH) | Someone claimed unauthorized | Stop 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:**

```text
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](https://paymentsandrisk.com/docs/operations/checklist/#solo-operator-no-dedicated-payments-person) - CB count, disputes, deposits
2.  [Know oh shit triggers](https://paymentsandrisk.com/docs/operations/checklist/#oh-shit-triggers) - When to drop everything
3.  [Monthly statement review](https://paymentsandrisk.com/docs/operations/checklist/#monthly-checks-1-2-hours) - Effective rate, reason codes

**Building operations routine?**

1.  [Set up daily checks](https://paymentsandrisk.com/docs/operations/checklist/#daily-checks-5-15-minutes) - Auth rate, fraud queue, deposits
2.  [Establish weekly cadence](https://paymentsandrisk.com/docs/operations/checklist/#weekly-checks-30-45-minutes) - Ratios, win rate, reconciliation
3.  [Configure alerts](https://paymentsandrisk.com/docs/operations/alerts-configuration/) - Automate what you can

**Scaling team?**

1.  [Match checks to team size](https://paymentsandrisk.com/docs/operations/checklist/#checklist-by-team-size) - Solo vs small vs medium
2.  [Run monthly experiments](https://paymentsandrisk.com/docs/operations/checklist/#monthly-experiments) - One at a time, measure impact
3.  [Account for edge cases](https://paymentsandrisk.com/docs/operations/checklist/#where-this-breaks) - Flash sales, seasonal, international

* * *

## Related

-   [Operations Metrics](https://paymentsandrisk.com/docs/operations/metrics/) - KPIs behind these checks
-   [Processor Management](https://paymentsandrisk.com/docs/operations/processor-management/) - Handling scary emails
-   [Reduce Chargebacks Fast](https://paymentsandrisk.com/docs/playbooks/reduce-chargebacks-fast/) - When thresholds approach
-   [Chargeback Metrics](https://paymentsandrisk.com/docs/chargebacks/metrics/) - Tracking ratio and win rate
-   [Fraud Metrics](https://paymentsandrisk.com/docs/fraud/metrics/) - Fraud rate monitoring
-   [Alerts Configuration](https://paymentsandrisk.com/docs/operations/alerts-configuration/) - Setting up notifications
-   [Reading Statements](https://paymentsandrisk.com/docs/operations/reading-statements/) - Monthly statement review
-   [Who Owns What](https://paymentsandrisk.com/docs/operations/who-owns-what/) - Ownership clarity
-   [ACH Operations](https://paymentsandrisk.com/docs/operations/ach-operations/) - Bank payment checks
-   [Network Programs](https://paymentsandrisk.com/docs/chargebacks/reference/network-programs/) - Threshold monitoring
-   [Representment Workflow](https://paymentsandrisk.com/docs/operations/representment-workflow/) - Dispute response
-   [Money Held or Frozen](https://paymentsandrisk.com/docs/operations/holds-and-reserves/) - Reserve monitoring
