As a system, when a Visa Incorrect Amount dispute has satisfied all dependencies, it should route to submit an auto chargeback instead of routing for a user to review.

1. When a Visa Incorrect Amount dispute is initiated and the dispute meets all dependencies it is routed to submit an auto chargeback without routing to user review.
2. When a Visa Incorrect Amount dispute is initiated the system verifies the correct amount fields should not be 0.00.
3. When a Visa Incorrect Amount dispute is initiate the system verifies the correct amount field should not be greater than the transaction amount.

Resolved an issue where when a Visa Incorrect Amount dispute satisfied all dependencies, it was incorrectly routing to a user for review. This fix ensures that if dependencies are met the chargeback can be performed automatically.

When a transaction is disputed due to Merchant Recurring and the Customer contacted the merchant to perform the cancellation using a Web Form, the answered captured for "Please provide the web form/application name you used to cancel" must be transmitted as part of the Request Message to Visa.

1. QFD is able to submit Visa Disputes under the dispute Reason Merchant Recurring.
2. When the customer indicates that the recurring payment cancellation request has been submitted using a Web Form, the information related to the name of the form/application used is transmitted to the association.
   1. ContactMerchantDetailsApplicationName tag is mapped on the Request message

Resolves a issue where Visa recurring chargebacks are failing due to a incorrect tag being passed in the request message.

When a Claim that contains "ExpectedReceiveDate" populated during Intake is reclassified, QFD should run validations on this field only when the dispute reason requires the data to transmit the Chargeback. 

1. Expected Receive Date validations are only ran when the data is a required dependency to submit the chargeback.
2. When a claim was initially filed as Cancelled Merchandise or Merchandise Not Received and later reclassified to a dispute reason that does not require Expected Receive Date, the chargeback can be submitted. 

Resolve a issue where it is incorrectly evaluating a dependency.