Brazil, Australia, Zurich, Yokohama
Standalone Application
This application provides comprehensive content and tools for managing card disputes in accordance with Mastercard guidelines. It includes a structured questionnaire for intake of dispute-related information organized across various dispute categories as defined by Mastercard, while embedding auto-updated rules to streamline and optimize your disputes process.
- Provides a questionnaire for dispute intake as per Mastercard guidelines
- Runs chargeback eligibility rules based on the Mastercard Chargeback Guide
- Changed
- The Mastercard chargeback eligibility checks now follow Mastercard's Q4 2026 rules for reason codes 4837 (No Cardholder Authorization), 4849 (Questionable Merchant Activity), 4853 (Credit Posted as a Purchase), 4870 (Chip Liability Shift), and 4871 (Chip/PIN Liability Shift). The reasons shown to agents when a dispute isn't eligible have been reworded to match.
- For Colombian disputes under reason codes 4870 and 4871, eligibility now depends on the agent's answer to the new intake question about a payment reversion claim filed under Colombian law. It no longer relies on country and currency codes.
- Under reason code 4837, the rules for emergency cash, Maestro chip, PIN or device verification, and the 120-day filing window have been updated. Two of its fraud type checks now read the fraud type the agent enters at dispute intake.
- Under reason code 4853, a dispute is now flagged when the disputed amount is more than twice the transaction amount. Before, it was flagged whenever the amount wasn't exactly twice.
- Fixed
- Under reason codes 4837 and 4849, the fraud report check was backwards: it acted on disputes that had a fraud report instead of those missing one. The check is now correct.
- Removed
- Three eligibility checks no longer apply under Mastercard's Q4 2026 rules and have been removed: the "coercion claim not substantiated" check (4849), one check under 4837, and the chip liability shift check under 4871.
Not applicable for this application version. For more information, please see
Application Runtime Policy
- Permissions and roles:
- System administrator (admin) is required for the installation