# Received fraud alert

Webhooks for fraud alerts allow merchants to securely receive real-time notifications of fraud reported by card schemes.
Duplicate webhook events can occur. Implement idempotency on your end to avoid processing the same event twice.

Endpoint: POST FraudAlert
Version: 1.0.0
Security: merchant, signature

## Security:

  - `merchant` (unknown)
    apiKey in header merchant

  - `signature` (unknown)
    apiKey in header signature

## Header parameters:

  - `merchant` (string, required)

  - `signature` (string, required)

  - `solidgate-event-id` (string, required)
    Unique event identifier.

  - `solidgate-event-created-at` (string, required)
    Event creation time in UTC as ISO 8601 with milliseconds.

  - `solidgate-event-type` (string, required)
    Event type, indicating the specific event that occurred.

## Request fields (application/json):

  - `id` (integer)
    Unique fraud alert identifier.

  - `order_id` (string)
    Unique order identifier, which can be used to find the payment.
For the first payment, the identifier is defined by the merchant.For recurring subscription-based payments, it is generated by the Solidgate subscription service.

  - `created_at` (string)
    Datetime when the fraud alert was created by Solidgate.

  - `updated_at` (string)
    Datetime when the fraud alert was updated by Solidgate.

  - `fraud_amount` (integer)
    Fraud amount in the smallest currency unit.
For instance, 1020 means 10 EUR and 20 cents.

  - `fraud_currency` (string)
    Three-letter ISO-4217 currency code.

  - `fraud_amount_usd` (integer)
    Amount converted to USD, used for standardized reporting and analysis across different currencies.

  - `fraud_report_day` (string)
    Date on which the fraud was reported.

  - `fraud_type` (string)
    Type of fraud detected, categorizing the nature of the fraudulent activity.

  - `card_scheme` (string)
    Card scheme associated with the transaction (e.g., Visa, Mastercard), providing context on the payment network involved.

  - `reason_code_description` (string)
    Detailed explanation of the reason code associated with the fraud alert, offering insights into why the fraud was flagged.

## Request examples:

  - `Received fraud alert` (unknown)

## Response 2XX:

  - `2XX` (unknown)
    Return any 2XX status to confirm successful data receipt