Representment Workflow
TL;DR
- Workflow: Receive → Analyze reason code → Decide → Gather evidence → Respond → Monitor
- Deadlines are critical: Visa 30 days, Mastercard 45 days, Amex 20 days
- Decision matrix: strong evidence + any amount = represent; weak evidence + low amount = accept
- See What proof each network accepts for what evidence you need
- Target: over 40% win rate, over 95% on-time submission, under 15 days average response time
A systematic approach to responding to chargebacks and maximizing win rates.
SMB Shortcut: Under 10 Chargebacks/Month
If you're handling fewer than 10 chargebacks per month, you don't need a formal workflow. Here's the fast version:
- Receive notification - Check email daily for chargeback alerts (set a filter)
- Quick decision (2 minutes): Is it under $50 with weak evidence? Accept it. Is it over $50 or do you have delivery proof? Fight it.
- Gather what you have (10 minutes): Order confirmation, shipping tracking screenshot, any customer emails. Don't spend more than 15 minutes.
- Upload to processor portal (5 minutes): Compile into one PDF, upload, submit.
- Move on - Check outcome in 30-60 days. Don't obsess.
Total time per chargeback: 15-20 minutes. If you're spending longer, your evidence collection process needs work - see compelling evidence.
For the detailed workflow below, use it when you're handling 10+ chargebacks/month or when you need to systematically improve your win rate.
Overview
Key principle: Every step has a deadline. Track them religiously.
Step 1: Receive and Log Chargeback
Immediate Actions
| Action | Timeline |
|---|---|
| Log receipt date | Same day |
| Calculate response deadline | Same day |
| Assign to analyst | Within 24 hours |
| Begin evidence search | Within 24 hours |
Information to Record
| Field | Source |
|---|---|
| Case number | Network/processor notification |
| Reason code | Chargeback details |
| Amount | Chargeback details |
| Transaction date | Original transaction |
| ARN | Chargeback details |
| Response deadline | Calculate from receipt |
Calculate Deadline
| Network | Standard Window |
|---|---|
| Visa | 30 calendar days from chargeback |
| Mastercard | 45 calendar days from chargeback |
| Amex | 20 calendar days from notification |
| Discover | 30 calendar days from chargeback |
Step 2: Analyze Reason Code
Determine Requirements
For each reason code, identify:
- What is alleged? - Fraud, non-receipt, quality, etc.
- What evidence defeats it? - Per network rules
- What are the exclusions? - When representment isn't allowed
- What is realistic win rate? - Based on evidence available
Reason Code Categories
| Category | Typical Evidence Needed |
|---|---|
| Fraud (10.x, 48xx) | 3DS, AVS, delivery proof, prior transactions |
| Authorization (11.x) | Valid authorization record |
| Processing Error (12.x) | Correct transaction data |
| Consumer Dispute (13.x) | Delivery proof, terms, refund record |
Check for Auto-Lose Conditions
Don't waste resources if:
- Past response deadline
- Duplicate case (already represented)
- Valid chargeback per rules
- No possible evidence exists
- Exclusion applies
Step 3: Make Represent Decision
Decision Matrix
| Evidence Quality | Amount | Decision |
|---|---|---|
| Strong | Any | Represent |
| Medium | High (over $100) | Represent |
| Medium | Low (under $100) | Case-by-case |
| Weak | High | Consider (learning) |
| Weak | Low | Accept |
| None | Any | Accept |
Factors to Consider
| Factor | Impact |
|---|---|
| Evidence strength | Primary factor |
| Transaction amount | ROI consideration |
| Win rate history | Expectation setting |
| Customer relationship | Future value |
| Analyst capacity | Resource allocation |
Document Decision
Record:
- Decision (represent/accept)
- Rationale
- Expected win probability
- Assigned analyst
Step 4: Gather Evidence
Evidence Checklist by Type
For Fraud Chargebacks
☐ 3D Secure authentication data
☐ ECI value
☐ CAVV/AAV
☐ Transaction ID
☐ AVS match result
☐ CVV match result
☐ Device fingerprint data
☐ IP address and geolocation
☐ Prior undisputed transactions
☐ Customer communication
☐ Delivery confirmation
For Non-Receipt Chargebacks
☐ Tracking number
☐ Carrier delivery confirmation
☐ Signature (if obtained)
☐ Photo proof (if available)
☐ Delivery address vs. billing
☐ Customer correspondence
☐ Download logs (digital goods)
☐ Access timestamps (services)
For Quality/Not-As-Described
☐ Product listing as displayed
☐ Terms and conditions
☐ Customer acceptance record
☐ Inspection report (if applicable)
☐ Return refusal documentation
☐ Customer communications
☐ Quality specifications
For Cancelled Recurring
☐ Original consent documentation
☐ Terms with cancellation policy
☐ Cancellation request log
☐ Transaction before/after cancel date
☐ Pre-billing notifications sent
☐ Usage logs after "cancellation"
Evidence Quality Standards
| Standard | Requirement |
|---|---|
| Legible | Clear and readable |
| Complete | All relevant pages |
| Relevant | Specific to this transaction |
| Identified | Transaction reference visible |
| Masked | PAN truncated (last 4 only) |
Step 5: Prepare Response
Response Components
| Component | Purpose |
|---|---|
| Cover letter | Summary of defense |
| Evidence packet | Supporting documentation |
| Rebuttal letter | Point-by-point response |
| Message text | Required network codes |
Message Text by Network
Mastercard (DE 72)
| Defense | Message Text |
|---|---|
| Delivered | DELIVERED MMDDYY |
| Credit issued | CREDIT ISSUED MMDDYY |
| Compelling evidence | COMP EVID |
| Authenticated | AUTH MMDDYY/NNNNNN SL 1 |
Visa
Include in response:
- Representment reason
- Evidence description
- Transaction details
Document Organization
1. Cover Letter
- Case number
- Transaction details
- Summary of defense
2. Evidence Tab A: Transaction Data
- Receipt/order details
- Authorization record
3. Evidence Tab B: Delivery/Service
- Tracking
- Confirmation
4. Evidence Tab C: Customer Contact
- Communications
- Prior transactions
5. Evidence Tab D: Authentication
- 3DS data
- AVS/CVV results
Step 6: Submit Response
Submission Checklist
☐ Verify case number is correct
☐ Confirm all evidence attached
☐ Check file size limits
☐ Verify format requirements
☐ Double-check deadline
☐ Take screenshot of submission
☐ Save confirmation email/number
Submission Methods
| Network | Method |
|---|---|
| Visa | Via VROL/Verifi or processor portal |
| Mastercard | Via Mastercom or processor portal |
| Amex | Via Amex merchant portal |
| Discover | Via processor portal |
Document Submission
Record:
- Date/time submitted
- Confirmation number
- Files submitted
- Portal used
Step 7: Monitor Outcome
Track Resolution
| Status | Meaning | Action |
|---|---|---|
| Won | Chargeback reversed | Update records |
| Lost | Representment rejected | Analyze why |
| Pre-arb filed | Issuer challenges | Prepare response |
| Arbitration | Network decision | Submit evidence |
Response Timeline
| Stage | When to Expect |
|---|---|
| Initial response | 30-45 days |
| Pre-arbitration | 30 days after response |
| Arbitration | 45 days after pre-arb |
Win/Loss Analysis
For each outcome, document:
- Reason code
- Evidence submitted
- Outcome
- Network feedback (if any)
- Lessons learned
Metrics to Track
Volume Metrics
| Metric | Calculation |
|---|---|
| Chargebacks received | Count per period |
| Representment rate | Represented / Received |
| Response rate | Submitted on time / Represented |
Performance Metrics
| Metric | Calculation | Target |
|---|---|---|
| Win rate | Won / Submitted | over 40% |
| Pre-arb rate | Pre-arbs / Won | under 30% |
| Arbitration rate | Arbitrations / Pre-arbs | under 10% |
Efficiency Metrics
| Metric | Calculation | Target |
|---|---|---|
| Avg response time | Days to submit | under 15 days |
| SLA compliance | On-time / Total | over 95% |
| Evidence completeness | Docs per case | Track trend |
Common Mistakes
Process Mistakes
| Mistake | Prevention |
|---|---|
| Missed deadline | Calendar + alerts |
| Wrong case number | Double-check before submit |
| Missing evidence | Checklist review |
| Wrong reason code defense | Match evidence to code |
Evidence Mistakes
| Mistake | Prevention |
|---|---|
| Illegible documents | Quality check before submit |
| Missing pages | Complete document review |
| Wrong transaction | Verify ARN/transaction ID |
| Unmasked PAN | Always truncate to last 4 |
Strategy Mistakes
| Mistake | Prevention |
|---|---|
| Representing weak cases | Decision matrix |
| Not representing strong cases | Evidence review |
| Generic responses | Customize per reason code |
| Missing message text | Checklist per network |
Templates
Cover Letter Template
RE: Case Number [CASE#]
Transaction Date: [DATE]
Amount: [AMOUNT]
ARN: [ARN]
Dear Disputes Team,
We are submitting this representment for the above-referenced
chargeback filed under reason code [CODE].
[BRIEF SUMMARY OF DEFENSE]
Enclosed please find:
- [LIST OF EVIDENCE]
Based on the evidence provided, we respectfully request
this chargeback be reversed.
Sincerely,
[NAME/TITLE]
Next Steps
Setting up representment workflow?
- Calculate deadlines - Network-specific windows
- Create decision matrix - When to represent
- Build evidence checklists - By fraud type
Responding to a chargeback?
- Analyze reason code - What evidence defeats it
- Gather evidence - Checklist by type
- Submit response - Before deadline
Improving win rates?
- Track metrics - Win rate, response time
- Avoid common mistakes - Process, evidence, strategy
- Use templates - Cover letter format
See Also
- What proof each network accepts - Evidence requirements
- Time Frames Reference - Network deadlines
- Reason Codes - Mastercard - MC dispute codes
- Reason Codes - Visa - Visa dispute codes
- Reason Codes - Amex - Amex dispute codes
- Chargeback Lifecycle - Full dispute flow
- Winning Evidence - Documentation strategy
- Chargeback Metrics - Win rate tracking
- Friendly Fraud - First-party abuse patterns
- Fraud Classification - Identify fraud type
- Network Programs - VAMP, ECM thresholds
- Chargeback Prevention - Reducing disputes upstream