Collaboration

QFD supports collaboration with card merchants via Ethoca. These integrations allow issuers to attempt recovery from the merchant before initiating a chargeback with the card association. Merchant collaboration currently only supports card transactions.

Workflow

Following the enrichment step, a case is created with all enabled collaboration networks. If a refund has been promised by a merchant via any of the configured networks, all cases are closed, and the dispute moves to Pend for Merchant Credit to wait for the credit to post to the account.

New Collaboration Case

Before a case is created with the network, it is evaluated for eligibility. No eligibility service is available for Ethoca, but transaction details are evaluated by the system to ensure that cases are only created for eligible disputes. Additionally, the Ethoca service is called one hour after creating the case and the status is evaluated to determine if an alert was sent to the merchant. If an alert was not sent, the merchant is considered to be ineligible and the collaboration attempt ends.

Waiting for a Response

While pending for case status, the system will call the network every 6 hours for an updated status. The dispute will stay in a pending collaboration status for 5 days while it waits for a response. If no response is received after 5 days, it will move forward in the case lifecycle, usually to Provisional Credit Review, and QFD will continue to poll the network for updates. When the final status is retrieved, the case is closed and the outcome is recorded in the Recovery Action History. As noted above, if a refund is promised, the dispute will move to the Pend for Merchant Credit flow to wait for the credit to post to the account. To close the collaboration case and move to the next step in the workflow, select the "Cancel Collaboration" option from the Other Actions menu in the Collaboration step.

Ethoca Alerts

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.

Retrieve Credentials

Get login credential to the sandbox.ethocaweb.com portal (prod: ethocaweb)
From the upper right corner, select “Change API Password”
Select the API User
Click “Generate Password”
Copy and store off the password

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.

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.