1. Home
  2. Arbiter
  3. Arbiter 2.0
  4. Dispute Categories

Dispute Categories

  • INQUIRY
  • CHARGEBACK
  • GOVERNMENT_BILLER
  • TSA_BILLER
  • REFUND
  • GOOD_FAITH
  • CO_ACQUIRED

INQUIRY

StatusesINQUIRY, ACCEPTED, DECLINED
InitiatorIssuer, Interswitch, Verve
ResponderAcquirer/Merchant
ConstraintsTransaction merchant type classification must be REGULARCard scheme must be “DISCOVER”Compatibility criteria – N/A. Where a dispute already exists on the same transaction, an INQUIRY dispute cannot be logged

CHARGEBACK

StatusesCHARGEBACK, REPRESENTMENT, PRE_ARBITRATION, PRE_ARBITRATION_II, ARBITRATION, ACCEPTED, DECLINED
InitiatorIssuer, Interswitch, Verve
ResponderAcquirer/Merchant
ConstraintsInterswitch and Verve can initiate the claim but they cannot perform any further Issuer actions i.e. decline dispute evidence, move dispute to arbitration etcTransaction merchant type classification must be REGULARTransaction timeline valid time (if applicable) has not been exceededCard scheme must not be “VISA”Compatibility criteria – Where a dispute already exists on the same transaction, a CHARGEBACK dispute can only be logged if the existing dispute is:an INQUIRY dispute that has been DECLINEDa REFUND dispute that has been DECLINED

GOVERNMENT_BILLER

StatusesACCEPTED
InitiatorInterswitch
ResponderN/A
ConstraintsTransaction merchant type classification must be GOVERNMENTCard scheme must not be “VISA”Compatibility criteria – N/A. Where a dispute already exists on the same transaction, a GOVERNMENT_BILLER dispute cannot be logged

TSA_BILLER

StatusesCHARGEBACK, ACCEPTED, DECLINED
InitiatorIssuer, Interswitch, Verve
ResponderAcquirer/Merchant, Interswitch
ConstraintsInterswitch can initiate and can respond but the responder must not be the same person as the initiatorTransaction merchant type classification must be TSACard scheme must not be “VISA”Compatibility criteria – N/A. Where a dispute already exists on the same transaction, a TSA_BILLER dispute cannot be logged

REFUND

StatusesREFUND, ACCEPTED, DECLINED
InitiatorAcquirer/Merchant
ResponderAcquirer/Merchant
ConstraintsAcquirer can initiate and respond only when transaction merchant type classification is REGULARMerchant can initiate and respond when transaction merchant type classification is REGULAR, GOVERNMENT or TSAResponder must not be the same person as the initiatorCard scheme must not be “VISA”Compatibility criteria – Where a dispute already exists on the same transaction, a REFUND dispute can only be logged if the existing dispute is:an INQUIRY dispute that has been DECLINEDa CHARGEBACK dispute that has been DECLINED

GOOD_FAITH

StatusesGOOD_FAITH, ACCEPTED, DECLINED
InitiatorIssuer, Interswitch, VerveAcquirer/Merchant
ResponderAcquirer/MerchantIssuer
ConstraintsTransaction merchant type classification must be REGULARCard scheme must not be “VISA”Compatibility criteria – Where a dispute already exists on the same transaction, a GOOD_FAITH dispute can only be logged if the existing dispute is:
an INQUIRY dispute that has been DECLINED and the initiator of the GOOD_FAITH dispute belongs to the issuer, Interswitch, or Verve domaina CHARGEBACK dispute that has been DECLINED and the initiator of the GOOD_FAITH dispute belongs to the issuer, Interswitch, or Verve domaina CHARGEBACK dispute that has been ACCEPTED and the initiator of the GOOD_FAITH dispute belongs to the acquirer or merchant domaina REFUND dispute that has been ACCEPTED and the initiator of the GOOD_FAITH dispute belongs to the acquirer or merchant domaina GOOD_FAITH dispute that has been DECLINED and the initiator of the new GOOD_FAITH dispute belongs to the same domain as the initiator of the existing dispute

CO_ACQUIRED

StatusesCHARGEBACK, REPRESENTMENT, PRE_ARBITRATION, ARBITRATION, ACCEPTED, DECLINED
InitiatorSystem
ResponderAcquirer/Merchant
ConstraintCan only be initiated as a result of a corresponding dispute logged on VROLTransaction merchant type classification must be REGULARCard scheme must be “VISA”Compatibility criteria – N/A. Where a dispute already exists on the same transaction, a CO_ACQUIRED dispute cannot be logged
Was this article helpful to you? Yes 1 No 3

How can we help?