Operations
On this page
- Daily (5-15 min): Auth rate, fraud queue, chargeback queue, deposits
- Weekly (30-45 min): CB ratio trend, win rate, processor emails, reconciliation
- Monthly (1-2 hr): Statement review, effective rate, rule performance
- Oh shit: Auth drops 10%+, 5+ CBs/day, processor "review" email β act immediately
- Scale by volume: under $500K/yr = weekly CB count check only; over $2M/yr = real-time monitoring
The unglamorous work that keeps money flowing and losses contained.
Pick Your Modeβ
- Check your chargeback ratio (stay under 0.65%)
- Respond to any disputes due in the next 7 days
- Verify yesterday's deposits hit your bank
- Scan for any processor emails you missed
See the full checklist for daily, weekly, and monthly routines.
Under $100K/month: Check your chargeback count weekly and verify deposits hit your bank. That's your entire ops routine. Skip the Sandbox Training section below.
$100Kβ$1M/month: Add weekly chargeback ratio tracking, monthly statement reviews, and a basic representment process. Time investment: 30β60 minutes/week.
Over $1M/month: You need real-time monitoring, a dedicated dispute workflow, and someone who owns payment operations. See Who Owns What.
Over $10M/month: Full-time ops team, multi-processor monitoring, incident response playbooks, and quarterly vendor reviews. See Scaling Milestones.
| Task | Frequency | Time | Who | Link |
|---|---|---|---|---|
| Check fraud queue | Daily | 5 min | Fraud/Ops | Checklist |
| Review new disputes | Daily | 5 min | Ops | Representment |
| Verify deposits | Daily | 2 min | Finance | Reading Statements |
| CB ratio monitoring | Weekly | 10 min | Ops | Metrics |
| Processor emails | Weekly | 5 min | Ops | Processor Mgmt |
| Statement review / reconciliation | Monthly | 30 min | Finance | Reading Statements |
| Rule performance | Monthly | 20 min | Fraud | Checklist |
Sandbox Training for Operators (onboarding new team members with test environments)
Your team needs hands-on experience before touching production.
Why Sandbox Mattersβ
| Scenario | Production Risk | Sandbox Solution |
|---|---|---|
| New employee onboarding | Process real customer cards wrong | Learn workflows without risk |
| Testing new rules | Block legitimate customers | Validate before deploying |
| Incident response drills | Scramble during actual attack | Practice until it's muscle memory |
| Process changes | Break live checkout | Verify before rollout |
Training Checklist by Weekβ
- Log into processor dashboard
- Find transaction search
- Locate chargeback notifications
- Generate basic reports
- Process test transaction end-to-end
- Process a test refund
- Void a test transaction
- Respond to a test chargeback
- Investigate a test decline
- Batch close procedure
- Set up test alerts
- Review test chargeback ratio report
- Identify a test fraud pattern
- Generate reconciliation export
- Compare settlement to expected
- Run through fraud attack drill
- Practice emergency rule deployment
- Test backup payment path
- Document learnings
Test Card Numbers (Common)β
| Network | Test Number | Use For |
|---|---|---|
| Visa | 4111 1111 1111 1111 | Success |
| Visa | 4000 0000 0000 0002 | Decline |
| Mastercard | 5555 5555 5555 4444 | Success |
| Mastercard | 5105 1051 0510 5100 | Decline |
Note: Always check your processor's documentation for their specific test cards.
Next Stepsβ
- Operations Checklist - Daily/weekly routines
- Processor Management - Working with processor
- Reading Statements - Understand fees
- Representment Workflow - Step-by-step
- Chargebacks Overview - Full guide
- Time Frames - Don't miss deadlines
Start with The Guide, Pathway 4: Running Payments Daily, a beginner-friendly 19-minute walkthrough covering daily tasks, reading statements, and when to get help. This page is the full deep dive.
See Alsoβ
- Network Programs - VAMP, ECM thresholds
- Fraud Metrics - Measuring fraud performance
- Chargeback Metrics - Tracking dispute rates
- Payments Metrics - Transaction health
- Benchmarks - Industry comparisons
- Time Frames - Response deadlines
- 3D Secure - Authentication setup
- Buying Payments - Processor selection