...

120 days from the Network Processing Date of the Presentment of the recurring Transaction under dispute.

Conditions

The Issuer must meet all the following conditions :

• May be used even if the Transaction was Authorized.
• Amount to be charged back is the full Transaction amount.
• Before filing this Chargeback, the Issuer must manually enter the fraud Transaction into the WFIS or electronically transmit it into the GNS Fraud Repository.
• For Final Chargeback - This Chargeback is only applicable if the First Chargeback was either a fraud type or one of the following:
  • 4512 - Multiple Processing
  • 4516 - Request for Support Not Fulfilled
  • 4517 - Request for Support Illegible/Incomplete
  • 4754 - Local Regulations/Legal Dispute

Dependencies

• Cardmember Documentation or Issuer Declaration that supports the Chargeback

Validations

...

• Card Acceptor High Risk Indicator = S, I, F, T or X

...

Card Data Input Mode, position 7 = 9

...

• Program Indicator in 892-893 of First Pres 1240 msg = 08

...

Card present, position 6 = X

...

• Card present, position 6 = X
• Card Acceptor High Risk Indicator = F

...

High Risk S/Es listed under the following categories are not eligible for Excluded Transactions under this ISO code:

a. Risk indicators of “I”, “S”, “X”

b. Gambling MCCs 7801, 7802, 7995

...

• Card Acceptor High Risk Indicator = I, S or X or
• MCC = 7801, 7802, 7995

...

exist for Chargebacks processed under this ISO Code:

1. Either of the following may apply:
   1. The Chargeback is limited to Transaction(s) submitted by the Recurring Billing S/E after the notification of the revocation of the Cardmember’s consent to process Recurring Billing Transactions on the Card, or
   2. The Chargeback is limited to the amount of Goods not received or Services unused after the Cardmember revoked their consent, and
      1. The Cardmember made a reasonable attempt to notify the Recurring Billing S/E that the Cardmember has revoked their consent to process Recurring Billing Transactions from that S/E on their Card, or
      2. If local laws or regulations prohibit requiring the Cardmember to contact the Recurring Billing S/E, then the Cardmember’s Issuer should make a reasonable attempt to notify the Recurring Billing S/E on behalf of the Cardmember.

Dependencies

As applicable, the Issuer must provide the following for Chargebacks processed under this ISO code:

1. The Cardmember Documentation or Issuer Declaration that demonstrates:
   1. That the Cardmember made a reasonable attempt to notify the Recurring Billing S/E that the Cardmember revoked their consent to process 
      Recurring Billing Transactions from that S/E on their Card, or
   2. If local laws or regulations prohibit requiring the Cardmember to contact the Recurring Billing S/E, that the Cardmember’s Issuer made a 
      reasonable attempt to notify the Recurring Billing S/E on behalf of the Cardmember.

Validations

Related Questionnaires

Fraud Questionnaire

...