# Received PayPal dispute

Webhooks delivers critical insights into each PayPal dispute and its lifecycle, enabling businesses to manage disputes effectively and enhance customer satisfaction.


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

Endpoint: POST PayPalDispute
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: "alt_gate.paypal_dispute.received"

## Request fields (application/json):

  - `dispute_id` (string)
    Unique dispute 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.

  - `subscription_product_id` (string)
    Unique product identifier of the subscription.


   It corresponds to the product_id parameter in subscriptions.

  - `subscription_service_id` (string)
    Unique subscription identifier.


   It corresponds to the subscription_id parameter in subscriptions.

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

  - `updated_at` (string)
    Datetime when the dispute was updated.

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

  - `dispute_amount` (integer)
    Dispute amount.

  - `dispute_currency` (string)
    Three-letter ISO-4217 currency code of the dispute.

  - `dispute_life_cycle_stage` (string)
    Stage in the dispute lifecycle.
    Enum: "INQUIRY", "CHARGEBACK", "PRE_ARBITRATION", "ARBITRATION"

  - `dispute_channel` (string)
    Indicates the channel by which PayPal dispute has been received.
    Enum: "INTERNAL", "EXTERNAL", "ALERT"

  - `dispute_create_time` (string)
    Datetime when the dispute was created.

  - `dispute_update_time` (string)
    Datetime when the dispute was updated.

  - `dispute_outcome` (string)
    Outcome of the dispute.
    Enum: "RESOLVED_BUYER_FAVOUR", "RESOLVED_SELLER_FAVOUR", "RESOLVED_WITH_PAYOUT", "CANCELED_BY_BUYER", "NONE"

  - `reason` (string)
    Reason for the received dispute.
    Enum: "MERCHANDISE_OR_SERVICE_NOT_RECEIVED", "MERCHANDISE_OR_SERVICE_NOT_AS_DESCRIBED", "UNAUTHORISED", "CREDIT_NOT_PROCESSED", "DUPLICATE_TRANSACTION", "INCORRECT_AMOUNT", "PAYMENT_BY_OTHER_MEANS", "CANCELED_RECURRING_BILLING", "PROBLEM_WITH_REMITTANCE", "OTHER"

  - `status` (string)
    Status of the PayPal dispute.
    Enum: "OPEN", "WAITING_FOR_BUYER_RESPONSE", "WAITING_FOR_SELLER_RESPONSE", "UNDER_REVIEW", "RESOLVED", "OTHER"

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

  - `customer_account_id` (string)
    Unique customer identifier defined by the merchant.

  - `customer_email` (string)
    Customer's email address.

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


## Response 2XX fields