Overview: 

Added the ability for users to review for merchant credits within the Review Representment assignment, which allows users to reduce the remaining dispute amount for any credits identified.

Additionally, added the ability for users to split the liability decision to write off and customer liable. 

How it works:

When users have a Review Representment assignment they are able to select the ellipse to "Accept with Partial Merchant Credit". 

Overview: 

Updated the merchant credit check date ranges to ensure that the date range is only searching for merchant credit checks from the date the last credit check was performed until current date to avoid users having to acknowledge the same credit multiple times throughout the life of the claim

How it works:

When an automatic merchant credit check identifies a credit and the user addresses the credit, any subsequent credit checks will not review the same date range and the same credit will not be presented to the user.

Overview: 

Added chargeback currency conversion for Cross Border Transactions

How it works:

When a Cross Border Transaction is in dispute and the issuer country is not the United States, QFD will submit the chargeback in USD and force the recovery currency to be USD.

Overview: 

Prior to this enhancement, if a user clicked to process a Bulk Showcase assignment they did not have the ability to cancel the selected action. Users were forced to click outside of the node to restart the Bulk Showcase assignment.

How it works:

When a user clicks to process a Bulk Showcase assignment, such as "Grant Provisional Credit" in error an option to "Cancel" exists.

Overview: 

Added a configurable setting where users can determine who can withhold provisional credit during the intake flow. Users have the ability to enable this setting for Intake/External Client Users and Back Office/Fulfillment Users.

How it works: 

When Intake/External Client Users are enabled to withhold provisional credit during intake, the users can manually withhold PC on the summary screen during the intake flow and PC will not automatically be granted.

When Back Office/Fulfillment Users are enabled to withhold provisional credit during intake, the users can manually withhold PC on the summary screen during the intake flow and PC will not automatically be granted.

Please talk to your Customer Experience Liaison to enable this feature. 

Overview: 

Added a configurable setting where users can determine if Ethoca or Verifi should be enabled/disabled. 

How it works: 

By default, Ethoca and Verif will be enabled. If these settings are disabled, Ethoca and Verifi cases will be skipped in Collaboration. 

Please talk to your Customer Experience Liaison to disable this feature. 

Overview: 

Updated the Money Transfer letter to reference the <Final Resolution> verbiage instead of utilizing the hard coded verbiage in the letter. 

Please review the Money Transfer Letter for additional information.

Overview: 

Updated the Documentation Request letter to require attachments when sent through the Communication Hub.

Overview: 

Moved the Potential Claim Abuse report to the Risk report category. For more information on the report please see the Potential Claim Abuse page. 

Overview: 

Updated the following reports to pull 100k records and extended export timeout to 300 seconds.

1. Dispute Inventory 

2. Claim 

3. QFD Assignment 

4. Reg E Compliance 

5. Reg Z Compliance

6. Employee Case Audit 

Overview: 

Resolved an issue where when the Initial Interaction decision was set to Grant, the PC verbiage in the letter was utilized to satisfy the regulatory requirements instead of sending out a separate provisional credit letter. The Confirmation letter date was not previously tracked in the regulatory report for this scenario. 

A change was made to the report to ensure that if provisional credit was granted through the initial interaction decision and communicated to the customer/member through the confirmation letter the Confirmation Letter date is utilized in the Regulatory reports for the PC Letter date. 

Overview: 

Resolved an issue where when an ACH claim was initiated the generated Written Statement of Dispute (WSUD) form was selecting the incorrect  dispute reason.

How it works: 

This fix ensures that the dispute reason selected during intake matches the selection from the generated WSUD form.

Overview: 

Resolved an issue where when QFD received a zip document from Mastercard, the system was attaching the zip file instead of unzipping the attachment and uploading the individual docs with legible names. 

How it works: 

This fix ensures that any zipped files received from the association will be unzipped and each document will have a clear name.

Overview: 

Resolved an issue where the Merchant Credit letter was dropping off one credit transaction that was processed through the Pending Tollgate Post Process.

How it works: 

This fix ensures that all credits appear as expected on the Merchant Credit letters. 

Overview: 

Resolved an issue where the deny debit date was not always appearing in a letter when PC was being reversed. 

This fix ensures the deny debit date will always display when PC has been issued.

How it works: 

Overview: 

Resolved an issue where Intake/External Client Users were able to view options from the Action Menu that was only available for back office/fulfillment  users.

How it works: 

This fix ensures that Intake/External Client Users only see options that are available to their user group which includes Resume or Refresh.

Overview: 

Resolved an issue where when batch accounting was successful the Pending Batch Accounting Assignment was not closed, resulting in the assignment retrying.

How it works: 

This fix ensures that when the Pending Batch Accounting assignment is successful the assignment is closed and not retried.

QPS-7926 - Pending Batch Accounting Assignments Left Hanging

Overview: 

Resolved a letter merging issue where when a merchant credit was applied to a dispute and a second credit was applied separately the letter merged showing an incorrect dispute amount. 

How it works: 

This fix ensures that if multiple credits are being applied to a dispute at different times a letter will go out for each adjustment to ensure the dispute amount is always accurate. If multiple credits are applied at the same time only one letter will be generated for the adjustment.

Overview: 

Resolved an issue where  Out of Timeframe was showing as an available denial reason for Reg Z Fraud Claims. 

How it works: 

This fix ensures that claims protected by Reg Z will not have the denial option of Out of Timeframe. 

Out of Timeframe is still a valid denial reason for Reg Z Convenience Check and Balance Transfer claims. 

Overview: 

Resolved an issue the intake question "Is the dispute in regards to a "No Show" charge? was duplicated.

How it works: 

This fix ensures that the question is not duplicated and once the question is answered the subsequent questions appear as expected. 

Overview: 

Resolved an issue where users were unable to dispute more than the posted transaction amount for an ATM deposit claim.

How it works: 

This fix ensures that users can dispute more than the transaction amount for an ATM Deposit claim and the recovery amount will properly reflect the dispute amount. 

Overview: 

Resolved an issue where attachment types were not limited when attaching documents via an RTSI call. 

How it works: 

Prior to this change, QFD allowed users to attach PNG images which would result in a failed RTSI call. This fix ensures that the attachment types are limited and if the RTSI call failed due to the document attachment a message would display "Only TIFF, JPEG and PDF file types are allowed and each file must be less than 10MB." 

Overview: 

Resolved an issue where when a single dispute claim was reclassified the option for Incorrect Amount was not an available option.   

How it works: 

This fix ensures that the option is available for reclassification and provides a disclosure for users to adjust the dispute amount through the Adjust dispute Amount option in the Actions Menu.

Overview: 

Resolved an issue where during manual enrichment of an ACH claim, the Company ID property field was set to an incorrect field type. 

How it works: 

This fix ensures that the Company ID field during manual enrichment is a text field, allowing users to enter a value.

Overview: 

Resolved an issue where when a user added a large attachment to the letter and the letter did not generate the letter was not treated as a failure even though the letter was not sent. 

How it works: 

This fix ensures that if a user attempts to add a large attachment an error message will display stating the attachment exceeds the size limit. If the letter is not generated due to the large attachment the failure error message displays that the letter was not generated due to exceeding the max page count.

Overview: 

Resolved an issue where if the Client Address did not have any details in Address 2 or Address 3 field the letter would generate with a line break for these fields 

How it works: 

This fix ensures that if a user has no Address 2/Address 3 information configured there will not be a line break for these fields when the letter is generated.

Overview: 

Resolved an issue where when Quavo DRE was enabled all funds disbursement assignments were routed to a user workbasket instead of a DRE workbasket.

How it works: 

This fix ensures that if configured for DRE to work assignments Visa funds disbursement assignments will route to a DRE workbasket and Alt Network funds disbursement are routed to a user workbasket.

Overview: 

Resolved an issue where credits issued for claims were appearing in the disputable transaction list as well as the identified merchant credit list.

How it works: 

This fix ensures that the any credits issued by QFD for a claim will not appear as a disputable transaction or a selectable merchant credit.

Overview: 

Resolved an issue with Jack Henry Block and reissue that caused manual reviews. 

How it works: 

This fix ensures that when using Jack Henry the locator fields is evaluate4d as a string and cards are blocked as expected with no error displayed to the user and no manual assignments created to address the block and reissue.

Overview: 

Resolved an issue where ProcessClaimAccounting was not picking up pending assignment when another assignment with the same flow name exists on the dispute object and is in an errored state.

How it works: 

This fix ensures that accounting is fired per the SLA timing even if there is a Provisional Credit assignment in the failure queue. 

Overview: 

Resolved an issue where when a claim was reopened and then re-denied and deny justifications are enabled the deny justifications were not contained in the letter. 

How it works: 

This fix ensures that when a reopen request is reviewed and redenied, deny justifications will not appear blank on the letter.

Overview: 

Resolved an issue when completing the questionnaire for Wrong Amount Posted chargebacks where the amount validation was incorrect resulting in the users unable to pursue a chargeback for Visa or Mastercard claims. 

How it works: 

This fix ensures the valid amount can be greater than the dispute amount and users are able to pursue chargebacks as usually. This fix was hotfixed to clients environments with QFD 23.01.

Overview: 

Resolved an issue where when a intake user attempted to withdraw a paid claim through the External Case Status widget the Withdrawn letter was not being generated. 

How it works: 

This fix ensures that when a user withdraws a paid dispute through the External Case Status Widget the Withdrawn letter generates as expected. 

Overview: 

Resolved an issue where the validation for Merchandise Return Date was incorrectly set to not be before the merchandise was received. This validation error caused users to be unable to process chargebacks if the return date did not fit within the validation set. Additionally, when a claim was reclassified from Merchandise to Service the merchandise returned date was still being required.

How it works: 

This fix ensures that the validation was removed from the field and if a claim was reclassified to a service dispute the merchandise returned question was not asked or required. 

Overview: 

Resolved an issue where QFD was setting the incorrect Goal/Deadline time on Pending Deny Dispute task for a withdrawal request, which resulted in the system denying a dispute a day before the true deadline date.

How it works: 

This fix ensures that when a case is withdrawn, the pending deny debit date task is set accurately and the debit is performed as expected on the date indicated in the letter. 

Overview: 

Resolved an issue where the Work Queue Inventory report was not loading results. 

Overview: 

Resolved an issue where the Visa Merchant Credit checks could cause enrichment failures due to its placement within the enrichment flow. This fix moved the Visa Merchant Credit Check flow to the end of the enrichment flow to ensure it does not cause issues with enrichment.

Overview: 

Resolved an issue where the question "Does this related to your card?" was not presented to users, resulting in the inability to initiate ACH claims.

Overview: 

Resolved an issue where when a LOB letter send process fails, the retry count was not incremented due to the activity status not being cleared.

How it Works: 

This fix ensures that if a Lob letter send process fails, the assignment is routed down the failure path and the activity status is cleared.

Overview: 

Resolved an issue where when a user had overridden the customer contact date to a weekend/holiday and the client was configured to not count weekends/holidays as day 0, the Set Reg PC property was incorrectly counting the weekend/holiday as day 0, resulting in PC being issued a day early. 

How it Works: 

This fix ensures that when configured to not count weekends/holidays as day 0, and the customer contact date is overridden, the configuration is upheld and weekends/holidays do not count as day 0.

Overview: 

Resolved an issue where when a claim was partially denied for No Error, and deny justifications were utilized, after the letter weas submitted the deny justifications appeared blank in the generated letter.

How it Works: 

This fix ensures that deny justifications are not cleared after the letter is submitted and the letter appears with the deny justification as expected. 

Overview: 

Text

How it works: 

Text