Chargebackhit API helps merchants reconcile transactions by processing complex outcomes and responses. It ensures accurate matching of alerts to transactions, simplifying dispute resolution.
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 type | Description | Outcome |
|---|---|---|
| inquiry | Provides 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 webhook
|
| init-refund | Matches 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 webhook
|
|
fraud-notification
dispute-notification resolved prevented |
Reconcile to the original transaction. | Default outcome
acknowledged
order
information in the 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 type | Description |
|---|---|
| reversed | The transaction has been refunded following the alert. This outcome occurs when an alert is successfully matched with a successful sale transaction, leading to a refund of the transaction. |
| previously-reversed | The transaction has been refunded before the alert. This outcome is determined when the transaction has already been refunded prior to the alert. |
| duplicate | The transaction has been refunded due to a duplicate alert. This outcome occurs when the alert is matched with a previously refunded transaction due to an alert received earlier. |
| decline | The related transaction was not successful. This occurs when the transaction was declined before the alert. |
| error | The processing error has occurred requiring additional communication. |
| reverse-error | Unable to process a refund. This outcome occurs when an attempt to refund has failed due to a decline by the bank. |
| not-found | The transaction has not been found. This outcome occurs when an alert cannot be matched with any existing transaction. |
| acknowledged | The default response for the alert is that no action is required with the transaction. |
| pending | A temporary status that allows for a response at a later time, recommended within 24 hours, through the update outcome API method. |
| shipped | This outcome applies to physical goods that have already been shipped. |