# Received dispute

Webhooks for chargebacks allow merchants to securely receive real-time notifications of chargeback events and automatically trigger actions or updates in their own systems based on those events.


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

Endpoint: POST Chargeback
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.chargeback.received"

## Request fields (application/json):

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

  - `order.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.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", "3ds_verify", "refunded", "auth_ok", "auth_failed", "settle_ok", "partial_settled", "void_ok"

  - `chargeback` (object)
    Map of chargebacks where the keys are chargeback identifiers.

  - `chargeback.id` (integer)
    Unique chargeback identifier.

  - `chargeback.dispute_date` (string)
    Date on which the chargeback was created by the issuer.

  - `chargeback.settlement_date` (string)
    Date on which the chargeback was financially settled.

  - `chargeback.amount` (integer)
    Amount that will be deducted for the chargeback on a specific order.


  This amount may vary based on the user's decision to dispute a different amount.

  - `chargeback.currency` (string)
    Three-letter ISO-4217 currency code  of the chargeback amount.

  - `chargeback.type` (string)
    Current type of the chargeback.
    Enum: "1st_chb", "2nd_chb", "arbitration"

  - `chargeback.status` (string)
    Status of the chargeback.
    Enum: "in_progress", "document_sent", "reversed", "accepted", "resolved", "resolved_reversal"

  - `chargeback.reason_group` (string)
    Reason code group.


  It could be used for the segmentation and analytic purposes.

  - `chargeback.reason_code` (string)
    Reason code for the chargeback provided by the card scheme.

  - `chargeback.reason_description` (string)
    Reason code description for the chargeback provided by the card scheme.

  - `chargeback.available_actions` (array)
    List of available actions for the chargeback in the current state.
    Enum: "enrich_evidence", "provide_evidence"

  - `chargeback_flow` (array)
    Map of chargeback flows where the keys are chargeback flow identifiers.

  - `chargeback_flow.id` (integer)
    Unique chargeback flow identifier.

  - `chargeback_flow.date` (string)
    Datetime when the chargeback flow was created.

  - `chargeback_flow.updated_date` (string)
    Datetime when the chargeback flow was updated.

  - `chargeback_flow.settlement_date` (string)
    Date on which the chargeback flow was financially settled.

  - `chargeback_flow.deadline_date` (string)
    Deadline for submitting a response to the dispute.


  This corresponds to date + n, where n is a number of calendar days set by the scheme/acquirer.

  - `chargeback_flow.amount` (integer)
    Amount involved in each stage of the chargeback process.


  For example, there could be two records in chargeback_flow one with an amount of 113.58 USD and another with an amount of 100 USD.

  - `chargeback_flow.dispute_amount` (integer)
    Specific amount disputed, typically in the smallest currency unit, that would be returned to the merchant if the dispute is resolved in their favor.


  For example, if the second chargeback was successfully disputed, the dispute_amount would be 100 USD.

  - `chargeback_flow.currency` (string)
    Three-letter ISO-4217 currency code  of the chargeback amount.

  - `chargeback_flow.type` (string)
    Type of the chargeback flow.
    Enum: same as `chargeback.type` (3 values)

  - `chargeback_flow.status` (string)
    Status of the chargeback.
    Enum: same as `chargeback.status` (6 values)

  - `chargeback_flow.represented_by` (string)
    Indicates which party has provided the defense document for dispute representment.
    Enum: "merchant", "automation"

  - `chargeback_flow.arn_code` (string)
    Acquirer Reference Number (ARN) assigned to transactions.


  Use ARN to check transaction status.

  - `chargeback_flow.rrn_code` (string)
    Retrieval Reference Number (RRN) assigned to transactions, based on the ISO 8583 standard.


## Response 2XX fields