This tutorial will tell you how to upload a PDF of a custom-created dispute response to DisputeFlow.
DisputeFlow offers two options for building dispute responses. You can use guided workflows in the builder to create and submit your response. Or, you can use an alternate platform — like Microsoft Word or Google Doc — to create the response package and then upload it to DisputeFlow for submission.
If you choose to upload your own package, there are a few things to remember:
1. DisputeFlow accepts PDFs. Be sure to save your file appropriately before uploading.
2. The maximum file size is 8MB. This is due to limitations in your processor’s portal. We want to be sure to upload as small a package as possible.
3. When you upload your PDF, it will be automatically sent to your processor. You can’t undo this action, so be sure you have the correct file uploaded before submitting.
4. After submission, it can often take 24-36 hours for the dispute response to be displayed in your processor's portal.
5. Make sure you include all the required information and compelling evidence in your package. This includes, but is not limited to:
-
A cover letter explaining your case
-
Information about the transaction being disputed
-
Information about the order and the customer who placed it
-
Proof of service or delivery
-
Customer service notes
-
Terms and conditions
-
Images of your website
When you’ve created the most compelling case possible, you’ll need to upload it to DisputeFlow.
Visit the dispute report and click on the New tab.
Locate the case you want to fight. Click the actions menu beside the dispute and click "Upload dispute response".
Next, drag and drop your file into DisputeFlow and click Upload.
You’ll notice a confirmation message in the upper right corner.
After you submit the file, the dispute will move from the New tab on the dispute data report to the Pending tab.
If you’d rather use the DisputeFlow builder to create responses, there are several other user tutorials that can walk you through the process.
Comments
0 comments
Article is closed for comments.