If you accept Discover cards, treat disputes differently — 3 practical steps (respond to retrievals in 20 days)
Quick, practical takeaways from our Discover chargeback guide you can use right now:
- Assume Discover is the issuer and the network — use DNDS as your single dispute hub and retain full transaction evidence for at least 540 days (and up to 2 years if you want to cover Good Faith Investigations). Capture order timestamps, delivery promises, tracking logs, and any customer communications so you can assemble an evidence packet fast.
- Treat retrieval requests as mission-critical: you have 20 calendar days to submit evidence (chargeback responses are 5 days). If you miss a retrieval request you auto-lose and cannot fight some fraud codes (AA, UA01, UA02, UA05, UA06). Automate DNDS alerts, prepare a templated evidence packet, and assign a fast owner to prevent misses.
- Use Discover’s mitigation tools but balance friction: enable Enhanced Decisioning to pass richer auth data, roll out ProtectBuy (3DS) with exemption rules to limit checkout friction, and subscribe to Fraud Alerts (Standard or Premium) with a clear playbook to cancel shipments or issue refunds immediately when flagged. Full article for reference: https://www.chargeback.io/blog/discover-chargeback-guide-for-merchants What processes or templates have you put in place to hit Discover’s 20-day retrieval window reliably, and which tools gave you the best ROI in reducing disputes?
Posted Feb 26, 2026, 8:00 AM UTC
10