Skip to end of banner
Go to start of banner

Verifi

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 8 Current »

Verifi Implementation Playbook

Benefits of using this Addon

Eliminates the need to process Chargebacks when Merchant doesn't settle transaction or issues Merchant Refunds.

What does it replace?

This replaces the traditionally lengthy and expensive chargeback process for merchants who have agreements with Verifi to review submissions.

What phase is this recommended in?

This is recommended in the first phase that the acquirer reference number (ARN) and transacting card number are available to send.  Typically, this coincides with using the Mastercom API or Visa RTSI.

How long from phase kickoff can this be implemented?

This requires the issuer have an agreement with Verifi to utilize the service and is largely dependent on that process.  Ideally, this work is completed before phase kickoff.  From the time of an agreement between the issuer and Verifi, this can be implemented within a month.

What success criteria should be met prior to going live?

In a test environment, a transaction should be submitted to Verifi.  A response that the merchant will provide a credit or not provide a credit should be tested to ensure that the appropriate automated tasks are completed with these responses.

Engage with Verifi

  1. Contact your Verifi account manager and let them know you're ready to configure your API account.  If you don't have a Verifi account manager, your Quavo Client Experience representative can coordinate this for you.

  2. Schedule a kickoff call with Verifi.

  3. During the kickoff call, request:

    1. An Issuer ID and credentials for the Verifi test API

    2. 3 or 4 ineligible merchant descriptors to be used for testing

  • No labels