Get Dispute by ID
Retrieve a dispute by its ID. Use the include parameters to expand related objects such as payment details, evidence files, and representment sections in a single request.
Authorizations
You can use an OAuth2 JWT bearer token in the Authorization header of your API requests for supported endpoints: Authorization: Bearer <YOUR_JWT_HERE>.
These tokens are valid for 10 minutes and can be requested via the access token endpoint endpoint.
Path Parameters
Identifier of the resource in Payrails.
Query Parameters
Boolean indicating if the payment should be included in the response.
Boolean indicating if the instrument should be included in the response.
Boolean indicating if the holder reference should be included in the response.
Boolean indicating if the assigned user email and username should be included in the response.
Boolean indicating if evidences should be included in the response.
Boolean indicating if representment plan entities should be included in the response.
Boolean indicating if representment sections should be included in the response.
Boolean indicating if AI evidence classifications should be included in the response.
Response
Dispute found, and all details are included.
Unique identifier of the Dispute in Payrails.
Date and time when the Dispute was created in Payrails.
Date and time when the Dispute was last updated in Payrails.
Unique identifier of the Provider that was used to process the Dispute.
Unique identifier of the merchant-specific Provider Configuration that was used to process the Dispute. This can include the set of credentials used, the merchant account, country, vertical, etc.
Unique identifier of the Dispute in the Provider.
Stage of the dispute.
Created, FraudReport, Retrieval, Chargeback, PreArbitration, Arbitration, Unknown Amount of the Dispute. May differ from amount of Payment.
List of reasons codes used when defending a Dispute.
Email of the user currently assigned to this dispute. Only present when includeUserEmail=true and a user is assigned.
Channel the customer used to raise the dispute.
Not every provider reports a channel, and the field is only populated on
disputes received after it was introduced. It is therefore absent on many
disputes, and absence says nothing about how the dispute was raised — do not
read a missing channel as the absence of an issuer chargeback.
Provider: the customer raised the dispute with the payment provider directly, without involving their bank.Issuer: the customer went to their card issuer or bank, so the dispute is a card chargeback.Alert: the dispute arrived as a pre-chargeback alert, and no chargeback has been raised yet.Unknown: the Provider reported a channel that Payrails does not recognize.
Provider, Issuer, Alert, Unknown Status of the chargeback.
Incoming, Executed, Reversed, SecondChargeback, IssuerReponseTimeframeExpired, ArbitrationReversed Status of the defense.
NotDefendable, Undefended, ReadyToSubmit, Submitted, Failed, UnderReview, Won, Lost, Accepted, Resolved, Unknown Date and time when the Dispute defense period expires.
Date and time when the Dispute was created in the Provider. Only present if informed by Provider.
Merchant-supplied reference for the payment that originated the Dispute (e.g. an order ID). Populated from the PSP notification for Adyen, PayPal, and Checkout.com disputes, or from the linked Payment for other providers. Omitted when not available.
Unique identifier in Payrails of the Payment that originated the Dispute. Only available if the Payment was created via Payrails. When handling Disputes related to Payments created outside Payrails, this field will be omitted.
Workspace ID that the Dispute belongs to.
Unique identifier of the workflow execution that manages this Dispute's lifecycle in Payrails. Present once the dispute-management workflow has been started for the Dispute; omitted otherwise.
Human-readable description of why the dispute was raised.
Provider-specific reason code for the dispute, when supplied by the Provider.
Card-scheme reason code for the dispute, when supplied by the Provider.
Free-text comments from the issuer or provider about the dispute, keyed by source. Populated for Adyen, Nuvei, PayPal, and Klarna disputes. Not provided for Checkout.com, Stripe, or Revolut. Omitted when not available.
Indicates whether liability has shifted away from the merchant, as determined by the Provider or by 3DS authentication data. When true, the issuer bears the chargeback liability. Null if not yet determined.
List of evidences associated with this dispute.
Representment plan details for this dispute.
Ordered representment sections for this dispute.
Status of the representment plan lifecycle.
GeneratingPlan, PlanReady, StoringEvidences, LabelingEvidences, EvidencesReady, GeneratingRepresentment, RepresentmentReady, Submitted Tags attached to this dispute.
AI classifications for the evidences associated with this dispute. Only present when includeEvidenceClassifications=true.