Skip to main content

Operations

TL;DR
  • 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

Popular

If You Only Have 2 Hours This Week
  1. Check your chargeback ratio (stay under 0.65%)
  2. Respond to any disputes due in the next 7 days
  3. Verify yesterday's deposits hit your bank
  4. Scan for any processor emails you missed

See the full checklist for daily, weekly, and monthly routines.


Operations at a Glance
TaskFrequencyTimeWhoLink
Check fraud queueDaily5 minFraud/OpsChecklist
Review new disputesDaily5 minOpsRepresentment
Verify depositsDaily2 minFinanceReading Statements
CB ratio monitoringWeekly10 minOpsMetrics
Processor emailsWeekly5 minOpsProcessor Mgmt
Statement reviewMonthly30 minFinanceReading Statements
Rule performanceMonthly20 minFraudChecklist

Core Operations Guides

Sandbox Training for Operators

Your team needs hands-on experience before touching production.

Why Sandbox Matters

ScenarioProduction RiskSandbox Solution
New employee onboardingProcess real customer cards wrongLearn workflows without risk
Testing new rulesBlock legitimate customersValidate before deploying
Incident response drillsScramble during actual attackPractice until it's muscle memory
Process changesBreak live checkoutVerify before rollout

Training Checklist by Week

Week 1: Basic Operations
  • Log into processor dashboard
  • Find transaction search
  • Locate chargeback notifications
  • Generate basic reports
  • Process test transaction end-to-end
Week 2: Exception Handling
  • Process a test refund
  • Void a test transaction
  • Respond to a test chargeback
  • Investigate a test decline
  • Batch close procedure
Week 3: Monitoring
  • Set up test alerts
  • Review test chargeback ratio report
  • Identify a test fraud pattern
  • Generate reconciliation export
  • Compare settlement to expected
Week 4: Incident Response
  • Run through fraud attack drill
  • Practice emergency rule deployment
  • Test backup payment path
  • Document learnings

Test Card Numbers (Common)

NetworkTest NumberUse For
Visa4111 1111 1111 1111Success
Visa4000 0000 0000 0002Decline
Mastercard5555 5555 5555 4444Success
Mastercard5105 1051 0510 5100Decline

Note: Always check your processor's documentation for their specific test cards.


Quick Links

Next Steps

Just getting started?
  1. Operations Checklist - Daily/weekly routines
  2. Processor Management - Working with processor
  3. Reading Statements - Understand fees
Handling disputes?
  1. Representment Workflow - Step-by-step
  2. Chargebacks Overview - Full guide
  3. Time Frames - Don't miss deadlines

See Also