# Received prevention alert

Webhooks enable to preemptively identify and resolve potential issues, thereby preventing the generation of alert.


  Duplicate webhook events can occur. Implement idempotency on your end to avoid processing the same event twice.

Endpoint: POST CardPreventAlert
Version: 1.0.0
Security: MerchantID

## Header parameters:

  - `merchant` (string, required)
    Unique public key provided upon registration and must be shared for identification purposes.
    Example: "wh_pk_7b197...ba108f842"

  - `signature` (string, required)
    Request signature that allows verification of merchant authenticity on the payment gateway server.
    Example: "M2E3OTkyNzcz...xMmExODI4"

  - `solidgate-event-id` (string, required)
    Unique event identifier.
    Example: "e1765cf7-70f7-4e56-8fb2-bd88744a94d1"

  - `solidgate-event-created-at` (string, required)
    Event creation time in ISO 8601 format with milliseconds.
    Example: "2025-06-05T12:34:56.789Z"

  - `solidgate-event-type` (string, required)
    Event type, indicating the specific event that occurred.
    Example: "card_gate.prevention_alert.received"

## Request fields (application/json):

  - `order` (object)
    Information about the order, including identifiers, timestamps, amounts, status, and customer details.

  - `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.

  - `order.created_at` (string)
    Datetime when the order was created.

  - `order.amount` (integer)
    Order amount in the smallest currency unit.


  For instance, 1020 means 10 EUR and 20 cents.

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

  - `order.status` (string)
    Status of the requested order.
    Enum: "processing", "settle_pending", "approved", "declined", "refunded"

  - `alert` (object)
    Information about chargeback alerts, including identifiers, amounts, currency, provider details, alert types, and outcomes.

  - `alert.id` (string)
    Unique identifier assigned to each alert.

  - `alert.amount` (integer)
    Amount specified in the alert.

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

  - `alert.provider_name` (string)
    Name of provider that sent alerts.
    Enum: "ethoca", "verifi"

  - `alert.alert_date` (string)
    Datetime when the alert was raised on the provider's side.

  - `alert.created_at` (string)
    Datetime when the alert was created in the system.

  - `alert.updated_at` (string)
    Datetime when the alert was updated in the system.

  - `alert.alert_type` (string)
    Type of alert. 


  Each alert type denotes a specific event or action in the chargeback flow.
    Enum: "inquiry", "init-refund", "resolved", "prevented"

  - `alert.outcome` (string)
    Specific response statuses for webhook alerts.


  Upon receiving a webhook alert, the primary task is to promptly provide a valid response using one of the specified outcomes. Only the initial response to the alert is accepted, with the exception when the initial status was set to pending. Once a response is submitted to the provider, subsequent modifications are not permitted.
    Enum: "reversed", "previously-reversed", "duplicate", "decline", "error", "reverse-error", "not-found", "acknowledged", "pending", "shipped"


## Response 2XX fields