---
title: "Retrieve a dispute"
method: GET
path: "/disputes/{disputeId}"
tags: ["Disputes"]
---

# Retrieve a dispute

`GET /disputes/{disputeId}`

This is used to fetch a dispute by its unique Id

## Path parameters

- `disputeId` string, required

## Response `200`

Successfully retrieved the given Dispute

- Dispute
  - `id` string — The ID of the dispute
  - `amount` integer — The amount that is being disputed and the merchant is liable for
  - `currency` string — The ISO currency code
  - `status` 'Open' | 'Cancelled' | 'Accepted' | 'Challenged' | 'Lost' | 'Won' | 'Expired'
  - `category` 'Fraudulent' | 'Authorization' | 'ProcessingError' | 'CardholderDispute' | 'General' — Disputes are grouped into a specific category based on their `reason.code`. These define the overlapping reason across various card schemes (who each have their own codes)
  - `reason` DisputeReason
    - `code` string — The reason code provided by the card scheme
    - `description` string — Description of the `code`
  - `respondBy` integer — The deadline by which the evidence needs responding by. Note that you cannot attach evidence or challenge the dispute once this date has passed. The dispute will move to `Expired`.
  - `recommendedEvidence` string[] — The evidence **strongly** recommended for the best chance to challenge and win the dispute. Note that this is based on the underlying `reason.code` of the Dispute and is subject to change should further types of evidence be added or no longer supported. Leverage this field to select the best forms of evidence should you choose to challenge the dispute.
  - `paymentSession` DisputePaymentSession — Details of the payment session linked to the dispute.
    - `id` string — The ID of the payment session the dispute relates to.
    - `paymentType` 'Standard' | 'Unscheduled' | 'MOTO' | 'Recurring'
    - `paymentMethod` object
      - `card` object — Details of the card used
        - `scheme` 'Visa' | 'Mastercard' | 'Amex'
        - `last4` string — The last 4 digits of the card used
  - `evidence` DisputeEvidence, nullable — The text/file evidence you have attached to the dispute.
    - `text` DisputeEvidenceTextEntries, nullable — Contains any evidence in text format
      - `billingAddress` string, nullable — Billing address provided by the customer on the original transaction. We will automatically append this if it was provided.
      - `shippingAddress` string, nullable — Shipping address the product or service were shipped to. Note we recommend also attaching any supporting files you have that confirm shipment to the same address. We will automatically append this if it was provided, however you can amend it if the address after taking payment with Ryft.
      - `duplicateTransaction` string, nullable — Relevant when category is `Duplicate`. Use this to attach an explanation detailing why the transaction in dispute is unique and not in fact a duplicate of a previous transaction.
      - `uncategorised` string, nullable — Any miscellanous text evidence you have attached.
    - `files` DisputeEvidenceFiles, nullable — Contains any evidence in file format
      - `proofOfDelivery` DisputeEvidenceFile, nullable — Details pointing to an uploaded file containing the relevant evidence
        - `id` string — The ID of the uploaded file
      - `customerSignature` DisputeEvidenceFile, nullable — Details pointing to an uploaded file containing the relevant evidence
        - `id` string — The ID of the uploaded file
      - `receipt` DisputeEvidenceFile, nullable — Details pointing to an uploaded file containing the relevant evidence
        - `id` string — The ID of the uploaded file
      - `shippingConfirmation` DisputeEvidenceFile, nullable — Details pointing to an uploaded file containing the relevant evidence
        - `id` string — The ID of the uploaded file
      - `customerCommunication` DisputeEvidenceFile, nullable — Details pointing to an uploaded file containing the relevant evidence
        - `id` string — The ID of the uploaded file
      - `refundPolicy` DisputeEvidenceFile, nullable — Details pointing to an uploaded file containing the relevant evidence
        - `id` string — The ID of the uploaded file
      - `recurringPaymentAgreement` DisputeEvidenceFile, nullable — Details pointing to an uploaded file containing the relevant evidence
        - `id` string — The ID of the uploaded file
      - `uncategorised` DisputeEvidenceFile, nullable — Details pointing to an uploaded file containing the relevant evidence
        - `id` string — The ID of the uploaded file
  - `customer` DisputeCustomer, nullable — Details of the customer who is making the dispute
    - `email` string, nullable — The email that was used for the disputed payment
    - `id` string, nullable — The Ryft ID of the customer
    - `createdTimestamp` integer, nullable — The epoch timestamp (seconds) when the customer was first recorded/created
  - `subAccount` DisputeSubAccount, nullable — If this dispute is for a payment under a sub account, then this contains details of that account
    - `id` string — The Ryft ID of the sub account
  - `createdTimestamp` integer — The epoch timestamp (seconds) when the dispute was created
  - `lastUpdatedTimestamp` integer — The epoch timestamp (seconds) when the dispute was last updated

## Other responses

- `404` — The given resource could not be found
- `500` — An unexpected error occurred when executing this request

---

[API](https://skmtc.net/ryftpay/apis/ryft-payment-api.md) · [All operations](https://skmtc.net/ryftpay/apis/ryft-payment-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/ryftpay/ryft-payment-api/versions/a042f64d4305/schema)