Welcome to the DisputeFlow user tutorials. This guide will explain the transaction information section of the response builder.
First, click the arrow in the right hand corner to expand the transaction information section.
You’ll notice that DisputeFlow auto-populates several fields based on information included in the dispute notice. These fields are read-only and don’t need to be edited.
There are several other fields that you’ll want to complete. Take a moment to look up the transaction in your CRM or order management system. Then, come back to DisputeFlow and enter the information in the appropriate fields.
If you’ve refunded the transaction, indicate the action that was taken. In the next fields, add the refund amount and the date you credited the cardholder’s account.
Next, provide the transaction amount and the transaction date. This information is valuable when reviewing your case, especially if the transaction amount differs from the dispute amount.
You’ll also want to include the transaction ID and the issuer’s authorization response code.
Lastly, include information about the identity verification tools you used during checkout — specifically AVS, CVV/CVC, and 3D Secure. If you don’t currently use these tools, we strongly recommend you reconsider. Response codes from these tools are some of the most compelling pieces of evidence and have a direct impact on your win probability. Other similarly important fields are marked with a star.
Some of the data provided in the transaction information section will be auto-populated in your smart response.
When you are finished with the transaction information section, mark it complete.
If you don’t have useful information to include in this section, you can hide it from the response. However, this section is typically very important and influential to your win probability.
You can also rearrange the section order so the most compelling information is towards the beginning of your package.
When you are done, move on to the next section or click Next Step if the dispute response is finished.
Comments
0 comments
Article is closed for comments.