Page Properties | ||||
---|---|---|---|---|
| ||||
|
Uses Visa RTSI to enrich Fraud/Dispute data and automatically process Recovery steps.
Benefits of using this Addon
Eliminates the need to manually key in additional transaction data, key chargebacks, check for representments, etc.
What does it replace?
With enhanced data, QFD is able to apply an advanced chargeback eligibility review process. With automated submission of chargebacks, checks for representment, large amounts of manual work and the possibility of human error is reduced significantly.
What phase is this recommended in?
This is recommended in the initial phase for larger clients. For smaller ones, it can be a second phase with an initial manual phase.
How long from phase kickoff can this be implemented?
Generally this takes about 3-5 months from project kickoff with Visa.
Who is responsible for what to implement this addon? What information is required to implement this addon?
Quavo Responsibilities |
|
---|---|
Client Responsibilities |
|
Third Party Responsibilities | Visa - onboard client to RTSI |
What does a timeline look like for implementing this addon?
Weeks to completion/Responsibility mapping | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Party | Kickoff | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
Quavo | 1 | 2 3 | 2 3 | 2 3 | 2 3 | 2 4 | 2 4 | 2 4 | 2 4 | 5 | 5 | 5 | 5 |
Client | 1 4 5 6 | 1 4 5 6 | 1 4 5 6 | 1 4 5 6 | 3 | 3 |
How is pricing determined?
Metric | Description |
---|---|
Enrichment of Disputed Transaction | A fee is assessed for successful capture of extended data for an eligible disputed transaction. |
Fraud Report | For any submitted fraud report, a fee is assessed. |
Recovery Action | For a recovery action (submitted chargeback, retrieval of representment, submission of pre arbitration, etc..), a fee applies for each individual action. For dependent actions such as case creation, associated transaction review, document retrieval, Quavo fees do not apply |
What success criteria should be met prior to going live?
Credentials should be obtained for MTF and Production, with test data being requested and made available in MTF.
While test data may not match between the test system of record and Mastercom, a case should be managed through enrichment, fraud reporting, case creation, chargeback and the representment queue prior to going live.
Any best practices for implementation or things to know after going live?
Start a project with Visa as soon as possible (even before finalizing with QFD if necessary) to onboard to RTSI. This process has taken a while in the past, but has since been streamlined. It still remains the largest barrier to implementing this addon.