An arbitration chargeback is the final chargeback available to the issuer. When filing an arbitration chargeback, the issuer must provide a reason code and, where applicable, new information and/or documentation.
The recovery options available for chargeback are also available for arbitration chargebacks. Additionally, the following reason codes are available and may be used, depending on the 2nd presentment reason code.
- 4901 - Required Documentation Not Received to Support Second Presentment
- 4902 - Documentation Received was Illegible
- 4903 - Unrelated Documents or Partial Scan
- 4905 - Invalid Acquirer Reference Data
- 4908 - Invalid Acquirer Reference Data
20.1 Mandates
Arbitration chargeback will be phased out with 20.1 mandates and pre-arbitration will be available. The transition is controlled by the setting in QVO_FW_FB_Claims MandatesRelease20_1EffectiveDateTime and, by default, will take effect at 4am GMT on 7/17/2020.
When an arbitration chargeback is pursued in the MC Review Representment flow, this flow is executed to complete the action.
If the Mastercom API is enabled...
- A Pending Execute ArbChargeback Service assignment is generated and displayed while the system completes the activity.
- If the activity fails, the system will retry every 15 minutes, for up to 3 times.
- If the activity continues to fail, an Execute Arb Chargeback Failed assignment is generated and prompts a user to retry the system activity, or complete the action in an external system.
If the Mastercom API is NOT enabled, an Execute Arb Chargeback assignment is generated and prompts a user to complete the action in an external system.
When an arbitration chargeback is successfully submitted, the MC Arb Chargeback Response is executed.
| Rule(s) | MCExecuteArbChargeback |