Skip to end of banner
Go to start of banner

Visa RTSI

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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
  1. Work with the client on engagement with Visa and project kickoff details.
  2. Represent client for Visa implementation project.
  3. Work with client to obtain Visa RTSI matching criteria (transacting card number and acquirer reference number) or implement suitable workaround.
  4. Procure Visa test data, enable RTSI in MTE2 region and create matching sample data in test environment
  5. Work with Visa for production go live routines
Client Responsibilities
  1. Work with Visa account representative to procure Visa RTSI.
  2. Pay any associated fees for use of Visa RTSI.
  3. Provide test and production credentials to Quavo.
  4. Work with any card processors as necessary to enable use of Visa RTSI.
  5. Work with internal accounting teams to understand any impact to settlement.
  6. Provide production examples of matching criteria for Visa RTSI (transacting card number and acquirer reference number) or suitable workaround within four weeks of phase kickoff.
Third Party ResponsibilitiesVisa - onboard client to RTSI

What does a timeline look like for implementing this addon?


Weeks to completion/Responsibility mapping
PartyKickoff123456789101112
Quavo12 32 32 32 32 42 42 42 45555
Client
1 4 5 61 4 5 61 4 5 61 4 5 633





How is pricing determined?

MetricDescription
Enrichment of Disputed TransactionA fee is assessed for successful capture of extended data for an eligible disputed transaction.
Fraud ReportFor 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.

  • No labels