Respond to Alerts in Chargeback Management

In Kount 360, after you have activated your organization, you can generate API keys to send data securely to Equifax. Only users with the Owner role permissions can generate, delete, or edit API keys.

API keys are organized under each client on the API Keys page. Expand the client to view your API keys, the descriptions, and when client details were created.

After you have provisioned your API credentials in the portal, retrieve a temporary bearer token to authenticate calls to the Kount 360 API. Provide the API key in an HTTP POST to a specific login.equifax.com URL.

With a successful exchange, the returned JSON provides a special bearer token, which is the access_token property. The exchange also provides an expiration date, the expires_in property, provided in seconds until expiration. The API to retrieve the bearer token depends on if you are calling the sandbox or production environment.

The values are:

Sandbox

Auth Server URL:

https://login-uat.equifax.com/as/token

API Service Host:

https://api-sandbox.kount.com

Production

Auth Server URL:

https://login.equifax.com/as/token

API Service Host:

https://api.kount.com

After obtaining the bearer token, use it to authenticate requests to the Kount 360 API. Include the token in the Authorization header of your HTTP API request, prefixed with Bearer {bearer token}.

To prevent authentication issues, refresh the token before it expires. Tokens issued by login.equifax.com expire after 20 minutes, but client credentials remain valid unless revoked. Minimize calls to the /token endpoint by implementing token expiration handling in your customer applications. Always check if a token has expired before requesting a new one, as excessive calls to the /token endpoint could result in rate limiting.

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:

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

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

Current API Reference

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

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

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.

   {
    "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"
        }
    ]
}