Product insights
Product insights
Use alert types, outcome types, and dispute data to reconcile transactions, report chargeback responses, and track resolution status

Alert Webhook helps merchants reconcile transactions by processing alert outcomes and responses. The process ensures accurate matching of alerts to transactions, supporting dispute resolution.


Alert flow

Chargebackhit delivers chargeback Glossary
Chargeback notifications are messages informing the merchant that a chargeback has occurred or is about to occur.
alerts
to the merchant before a claim is made, giving them a chance to avoid it. The alerts inform the merchant that a chargeback is pending but not yet filed. In this case, the merchant can take independent actions to avoid the chargeback, such as a voluntary refund, and pass this information to the issuer.

By bundling all the alerts on the market, Chargebackhit can help merchants with one of the first stages of the dispute-resolution process. This helps resolve issues without spending time analyzing disputes and also reduces chargeback costs.

Alerts are issued either by issuers or card schemes and originate from customers who have initiated a chargeback. Here is a simplified overview of the process for all types of alerts:

Alert processing flow from cardholder to merchant resolution
  1. Cardholder contacts the issuing bank to dispute a purchase.
  2. Issuer returns notifications to the providers directly or through card schemes.
  3. Providers notify Chargebackhit of the upcoming dispute.
  4. Chargebackhit sends a request to the merchant and notifies the merchant of the incoming chargeback. Depending on the alert type, the merchant then decides to refund the customer, stop order fulfillment, update order details, or dispute the transaction.
  5. Merchant takes the necessary actions, such as matching the alert to a database transaction or issuing a refund.
  6. Merchant communicates the action taken to Chargebackhit.
  7. Once Chargebackhit receives the response, it responds to the issuer according to the alert type. Assuming the merchant wants to avoid a chargeback, they refund the purchase and stop order fulfillment.
  8. Issuer receives the information and under certain conditions, can stop the chargeback process.
  9. Cardholder gets information or a response from the issuing bank indicating that the money can be returned shortly, or they receive additional real-time information about the transaction. This information can also help stop the chargeback process.

Alert products

Chargebackhit provides alert Webhook notifications. Its products include:

Cardholder Dispute Resolution Network’s (CDRN) patented closed-loop process integrates directly with issuers. It helps merchants and issuers resolve disputed payments while minimizing chargebacks and cardholder dissatisfaction. CDRN receives immediate notifications from issuing banks about cardholder issues.

Verifi CDRN alerts freeze the chargeback process for 72 hours.

Before a dispute can be registered, Visa requires issuing banks to make an Order Insight inquiry into the transaction. Order Insight sends the transaction data from the merchant as it is gathered in real time. This data contains delivery confirmations, purchasing device IDs, and even customer support interactions that link a cardholder to the purchase. Order Insight prevents disputes and

            </span>
            <span>
                <span class="tooltip_title">Glossary</span>
                <br />
                <span class="tooltip_text__boldGrey">Friendly fraud occurs when a cardholder disputes a legitimate transaction with their bank instead of contacting the merchant directly.</span>
            </span>
        </span>
</span>friendly fraud</span>

by aiding cardholder recognition.

Consumer Clarity displays additional transaction data to cardholders in real time on their online statement. It helps issuers verify if a cardholder made a purchase in real time. Verification can happen through a contact center or a mobile device, such as Order Insight.
When a fraudulent transaction is confirmed, issuers send a fraud alert called a TC40 statement. TC40 tracks stolen card numbers and other identifiers for fraudulent transactions. The Visa product also includes dispute notifications for already-issued chargebacks, which you can receive more quickly than from the acquirers.
Before becoming chargebacks, disputes not declined through Consumer Clarity requests are routed through the issuer’s network and Mastercard’s alert network, including Mastercard Collaboration. Merchants should check these alerts through their payment processor gateway. Refund alerts do not affect merchant accounts as negatively as chargebacks. Typically, merchants refund, stop shipping, or cancel subscriptions.
If a dispute survives an Order Insight request, Visa offers a pre-dispute phase where transaction details are sent to the merchant for automated review. The merchant can define conditions that, if met, trigger an automatic refund through Visa Response Online (VROL). Rapid Dispute Resolution (RDR) provides an immediate refund to the cardholder.
The key value of Compelling evidence 3.0 in the Chargebackhit system is to help merchants prevent disputes. It provides supporting evidence for disputed transactions, which can lead to a more favorable outcome.
PayPal pre-dispute alerts help merchants prevent chargebacks and simplify dispute resolution. PayPal alerts apply only to external dispute cases when customers dispute charges through their bank or card issuer, rather than through PayPal’s internal dispute system.

Alert types

Alert types represent the notifications merchants receive when a potential chargeback is detected but not yet filed. They help proactively address the issue and avoid the formal chargeback process. Each alert type serves a specific purpose, whether providing detailed transaction information to cardholders, facilitating voluntary refunds, or reconciling disputes.

Alert typeDescriptionOutcome
inquiryProvides order information to help cardholders identify purchases and build trust and transparency in the ecosystem.Default outcome acknowledged

order , customer , transactions , products , merchant information in the alert webhook
init-refundMatches the alert to the original transaction and updates its status, typically resulting in a refund.Enum outcome reversed , previously-reversed , decline , reverse-error , not-found , acknowledged , pending , shipped

order information in the alert webhook

If this alert type includes an Acquirer Reference Number (ARN), the decline outcome is not applicable.
fraud-notification
dispute-notification
resolved
prevented
Reconcile to the original transaction.Default outcome acknowledged

order information in the alert webhook and order_id is important for reconciliation alert to the original transaction

Outcome types

There are several outcome types associated with alerts. Each outcome type provides a status update about the related transaction, allowing merchants to track the progress and resolution of disputes.

Outcome typeDescription
reversedThe transaction has a refund following the alert.

This outcome occurs when Chargebackhit successfully matches an alert with a successful sale transaction, resulting in a refund of the transaction.
previously-reversedThe transaction has a refund from before the alert.

This outcome occurs when the transaction already has a refund prior to the alert.
duplicateThe transaction has a refund due to a duplicate alert.

This outcome occurs when the alert matches a transaction that a previous alert already refunded.
declineThe related transaction is not successful.

This occurs when the bank declines the transaction before the alert.

For init-refund alerts that include ARNs, the decline action is not applicable. The ARN signals that the transaction has already settled, so declining a refund at this stage is not a valid step. In such cases, there is the following message to the decline action attempt: “Alert with ARN refers to a settled transaction. Please verify the outcome flag.”
errorA processing error occurs, requiring additional communication.
reverse-errorUnable to process a refund.

This outcome occurs when the bank declines an attempt to refund.
not-foundChargebackhit cannot find the transaction.

This outcome occurs when an alert cannot be matched with any existing transaction.
acknowledgedThe default response for the alert is that the transaction requires no action.
pendingA temporary status that allows for a response at a later time, recommended within 24 hours, through the update outcome API method.
shippedThis outcome applies to physical goods that have already shipped.

Interaction

TypeProductsActions
inquiry
  • Order Insight
  • Compelling evidence 3.0
  • Consumer Clarity

Alerts that require a response and transmission of additional data.
  • Matching
  • Response with the data
  • Timeout to prevent
prevented
  • Order Insight
  • Compelling evidence 3.0
  • Consumer Clarity

Successful prevention of disputes.
  • Matching and providing a response
init-refund
  • CDRN
  • Ethoca

Alerts that require a response and refund.
  • Matching
  • Refund the transaction or resolve with the cardholder
resolved
  • RDR
  • PayPal

Post-factum notification about the pre-dispute.
  • Matching and providing a response
fraud-notification
  • Verifi Inform

Notifies about the confirmed fraud cases.
  • Matching and providing a response
dispute-notification
  • Verifi Inform

Notifies about disputes.
  • Matching and providing a response
Use the Guide
Understand how Chargebackhit matches prevention alerts to transactions in real-time using prioritized algorithms and transaction data.
matching algorithm
to match alerts to transactions. It applies prioritized identifiers and flexible criteria for real-time accuracy.

Looking for help? Contact us
Stay informed with Changelog