Skip to end of banner
Go to start of banner

Ethoca Alerts

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

Fully integrates Ethoca Alerts service into the Fraud/Dispute workflow.

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 Ethoca 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. Additionally, clients can enable sending alerts on transactions authorizations to stop the transaction from posting to the account.   

How long from phase kickoff can this be implemented?

This requires the issuer have an agreement with Ethoca 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 Ethoca, this can be implemented within a month.

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 Ethoca and requested service details.
  2. Work with client to obtain Ethoca matching criteria (transacting card number and acquirer reference number) or implement suitable workaround.
  3. Enable Ethoca Alerts addon in client test environment.
Client Responsibilities
  1. Work with Ethoca account representative to procure the Ethoca Alerts API.
  2. Pay any associated fees for use of the Ethoca Alerts API.
  3. Provide test and production credentials to Quavo within one month of phase kickoff.
Third Party ResponsibilitiesEthoca - onboard client to the Ethoca Alerts API

What does a timeline look like for implementing this addon?


Weeks to completion/Responsibility mapping
PartyKickoff123456789101112
Quavo
11112 32 32 32 3



Client
11113333



How is pricing determined?

MetricDescription
Participating transactionA fee is assessed for each fee where QFD utilizes the API to determine that a transaction is supported by Ethoca Alerts

What success criteria should be met prior to going live?

In a test environment, a transaction should be submitted to Ethoca.  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.

Any best practices for implementation or things to know after going live?

  • This service typically runs quite well and reduces human intervention in the disputes process significantly. 
  • Watch the volume of items pending Ethoca response to make sure they are within acceptable thresholds.
  • Enable sending authorization alerts to Ethoca to avoid a transaction in dispute from posting to the account.
  • No labels