The report provides a comprehensive overview of prevention alert patterns and their impact.

By analyzing the prevention alert data, businesses can proactively address potential issues before they escalate into disputes or chargebacks. This approach enables more effective fraud prevention and dispute resolution strategies.

Via API Prevention alerts API report is an essential tool for merchants, offering detailed information on prevention alerts. It provides insights into each alert, including unique identifiers, alert types, amounts, outcomes, and the alert generation timeline.

Prevention alert data is unloaded using the created_at parameter by default, reflecting the most recent updates to the alerts.
To create a report

  1. Make an prevention alerts API request with date range parameters date_from , date_to by the API endpoint.
  2. Receive the report URL report_url in the response.
  3. Download the report in CSV format using the report_id from the URL and authorization credentials.
It is crucial to use the same authorization credentials ( publicKey + secretKey ) to make the API request for downloading.

Since the report is prepared asynchronously, it may take some time before it is ready for download. If the report is not ready, the API reference returns the corresponding status code:

  • 200 - authentication failure. Double-check your access to the Solidgate API.
  • 204 - report is not yet ready. Wait a little longer for it to be generated.
  • 302 - redirect to a one-time S3 download report link.
  • 404 - report was not found.
  • 410 - report is unavailable, expired.

Please note that the report is only available for 30 days from its generation date. After that period, it is no longer accessible. Via Hub To create a prevention alerts report

  1. Go to Reports&Exports.
  2. In the top-right corner, click on +Create report.
  3. In the pop-up window, fill in the required details:
    • Select the Alerts report type
    • Select one or multiple channels
    • Define a date range of up to 36 days
    • Optionally, modify the auto-generated file name
  4. Click on Create.
    Once confirmed, reports are generated for each selected channel.
  5. Click on Download to save and access the report.

id string 36

Description

Unique identifier assigned to each alert generated.

Example

83b19018-cbc4-4df0-899a-dda84fd2705e

order_id string 255

Description

Order identifier defined by the merchant.

Example

923bb4e6-4a5f-41ec-81fb-28eb8a152e55

amount integer >=0

Description

Amount specified in the alert.

Example

200

currency string 3

Description

Three-letter ISO-4217 Wiki currency code.

Example

EUR

provider_name string

Description

Name of the provider that sent the alert.

Example

ethoca

alert_date string 50

Description

Datetime on which the alert was created by the provider.

Pattern: ^\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}$

Example

2025-11-25 11:01:03

alert_type string

Description

Specifies the type of alert.

  • inquiry - inquiry requests from the issuing bank, matched with merchant’s transaction data
  • init-refund - merchant is notified and a refund is processed to prevent chargeback
  • resolved - notifies about a resolved dispute, automatically crediting the cardholder
  • prevented - notification of successful dispute prevention, originating from an inquiry

Example

init-refund

outcome string

Description

Specific response statuses for alerts.

  • reversed - the transaction has been refunded after the alert
  • previously-reversed - the transaction has been refunded before the alert
  • duplicate - the alert is a duplicate and has already been processed
  • decline - the transaction for which the alert came is not successful
  • reverse-error - cannot make a refund
  • not-found - transaction not found
  • acknowledged - merchant decided not to make any refunds
  • pending - a temporary status that allows you to respond later (recommended within 24h)
  • shipped - relevant for physical goods, where goods are already shipped

Example

reversed

payment_method string

Description

Method used for the payment (google-pay, paypal-vault, etc).

Example

paypal-vault

created_at string 50

Description

Datetime when the alert was created.

Pattern: ^\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}$

Example

2025-11-25 11:11:03

updated_at string 50

Description

Datetime when the alert was last updated.

Pattern: ^\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}$

Example

2025-11-25 11:12:03

Alert example 
{
  "id": "83b19018-cbc4-4df0-899a-dda84fd2705e",
  "order_id": "923bb4e6-4a5f-41ec-81fb-28eb8a152e55",
  "amount": 200,
  "currency": "EUR",
  "provider_name": "ethoca",
  "alert_date": "2025-11-25 11:01:03",
  "alert_type": "init-refund",
  "outcome": "reversed",
  "payment_method": "paypal-vault",
  "created_at": "2025-11-25 11:11:03",
  "updated_at": "2025-11-25 11:12:03"
}