Responding to Ethoca or Verifi Alerts with the Alerts Actions API

June 16, 2026 22:19

When you receive an Alert notification for Ethoca or Verifi, you can send your response back to Ethoca or Verifi with the Alert Action API. Initiate a new HTTP call to the Alerts Actions endpoint for the appropriate environment:

Alerts Actions API URL

Sandbox API endpoint

https://api-sandbox.kount.com/kff/alerts/actions

Production API endpoint

https://api.kount.com/kff/alerts/actions

HTTP Method

Method: POST

Current API Reference

Example Request Payload

This example shows a request payload for submitting alert actions to Ethoca and Verifi. Include one action object for each alert response.

   {
    "actions": [
        {
            "id": "bebf622e-3706-4e21-8707-e2beadb7e5e7",
            "statusCode": "REFUNDED"
        }
    ]
}

This table describes the fields that can be included in each action object.

Field	Required	Notes
id	Required	Equifax unique identifier provided in the Alert.
status code	Required	Status code to return with the action for alerts (see table for valid codes).

Valid status codes are listed in the Valid Status Code Values table. Each status code represents a complete alert outcome. Unlike the legacy Alerts Actions API, the current version does not require a separate action value to indicate the alert disposition.

Status Code	Description
REFUNDED	Full Refund Issued: A full refund was issued on this transaction or voided the transaction prior to settlement.
PARTIALLY_REFUNDED	Refund Previously Issued: The transaction was refunded prior to receiving the alert.
NOT_REFUNDED	No Refund Issued: Did not issue a refund; allow to advance to a chargeback.
PREVIOUSLY_REFUNDED	Refund Previously Issued: The transaction was refunded prior to receiving the alert.
DUPLICATE	Duplicate Alert: The transaction has already received another alert from another provider.
DISPUTE_RECEIVED	Already a Chargeback: A chargeback was issued on this transaction prior to receiving the alert.
TRANSACTION_DECLINED	Declined Transaction/Failed Authorization: The transaction was declined; no refund was required.
TRANSACTION_HAS_3DS	3DS Authentication: This transaction was authenticated by 3D Secure; no refund was required.
TRANSACTION_NOT_FOUND	Not Found: The transaction could not be found in CRM or gateway.
REFUND_FAILED	Unable to Issue Refund: The refund was declined for this transaction.

sidebar. Legacy API Reference

This section describes the request payload, request fields, and status codes used by the legacy Alerts Actions API. Only existing integrations can continue using the legacy API. All new integrations must use the current Alerts Actions API.

Request Payload

This example shows a request payload for submitting alert actions through the legacy Alerts Actions API.

   {
    "actions": [
        {
            "id": "bebf622e-3706-4e21-8707-e2beadb7e5e7",
            "action": "resolved",
            "alertSystem": "Ethoca",
            "alertType": "ETHOCA_FRAUD",
            "refunded": "refunded",
            "amount": 30.00,
            "currency": "USD",
            "date": "2021-06-01",
            "statusCode": "stopped",
            "comments": "Previosly refunded in Verifi"
        },
        {
            "id": "bebf622e-3706-4e21-8707-e2beadb7e5e7",
            "action": "resolved",
            "alertSystem": "CDRN",
            "alertType": "DISPUTE",
            "statusCode": "100"
        }
    ]
}

This table describes the request fields used when submitting alert actions through the legacy Alerts Actions API. The Verifi and Ethoca columns identify provider-specific values. The Notes column provides additional implementation requirements.

Field	Verifi	Ethoca	Notes
id	Request ID from the Alert	Request ID from the Alert	Required — Equifax unique identifier provided in the Alert
action	Dispute Alerts: resolved, declined Cancel Alerts: cancelled, declined	resolved	Required
alertSystem	CDRN	Ethoca	Optional
alertType	DISPUTE, CANCEL,	ETHOCA_FRAUD, ETHOCA_DISPUTE	Optional
refunded	N/A	refunded, not refunded, not settled	Optional — required for Ethoca
amount	Amount refunded	Amount refunded	Optional — full amount will be used if amount not provided
currency	Currency of amount refunded	Currency of amount refunded	Optional — full amount will be used if amount not provided
date	date of the refund or cancelation in the format YYYY-MM-DD	Date of the refund or cancellation in the format YYYY-MM-DD	Optional
status code	Status code to return with the Action for Verifi Alerts (see table for valid codes)	ETHOCA_FRAUD: stopped, partially_stopped, previously_cancelled, missed, notfound, account_suspended, in_progress, shipper_contacted, other ETHOCA_DISPUTE: resolved, previously_refunded, unresolved_dispute, notfound, other	Required
comments	N/A	For alerts with "other" action. 200 characters available for comments.	Optional for Ethoca alerts

The legacy Alerts Actions API uses numeric status codes in combination with action values to identify the outcome of an alert. Use the status codes in this table when submitting responses through the legacy Alerts Actions API.

Status Code	Action	Description
100	RESOLVED	Case Resolved, Credit and Cancellation processed
101	RESOLVED	Case Resolved, Partial Credit & Cancellation processed
102	RESOLVED	Case Resolved, Authorization Cancelled
951	RESOLVED	Transaction Previously credited for Case Amount, no balance remaining
130	CANCELLED	Cancellation processed
900	DECLINED	Unmatched Case - General/Other
901	DECLINED	Unmatched Case - Merchant not Participating
902	DECLINED	Unmatched Case - Unable to locate Original Transaction
940	DECLINED	Duplicate Request
950	DECLINED	Merchant account closed, unable to process Credit
952	DECLINED	Transaction Previously received a Chargeback, no balance remaining
953	DECLINED	Request is outside of eligibility timeframe
954	DECLINED	Transaction 3D Secure authenticated successfully (Verified by Visa/MasterCard SecureCode)
955	DECLINED	Could not honor cancel request
956	DECLINED	Matched, unable to stop order fulfillment
957	DECLINED	Matched, Proceed with Chargeback for resolution

Was this article helpful?

0 out of 0 found this helpful