---
title: "Retrieve resolution center case"
method: GET
path: "/resolution_center_cases/{id}"
tags: ["Resolution center cases"]
---

# Retrieve resolution center case

`GET /resolution_center_cases/{id}`

Retrieves the details of an existing resolution center case.

Required permissions:
 - `payment:resolution_center_case:read`

## Path parameters

- `id` string, required

## Response `200`

A successful response

- ResolutionCenterCase — A resolution center case is a dispute or support case between a user and a company, tracking the issue, status, and outcome.
  - `company` object, nullable, required — The company involved in this resolution case. Null if the company no longer exists.
    - `id` string, required — The unique identifier for the company.
    - `title` string, required — The display name of the company shown to customers.
  - `created_at` string, date-time, required — The datetime the resolution was created.
  - `customer_appealed` boolean, required — Whether the customer has filed an appeal after the initial resolution decision.
  - `customer_response_actions` ResolutionCenterCaseCustomerResponses[], required — The list of actions currently available to the customer.
  - `due_date` string, date-time, nullable, required — The deadline by which the next response is required. Null if no deadline is currently active. As a Unix timestamp.
  - `id` string, required — The unique identifier for the resolution.
  - `issue` 'forgot_to_cancel' | 'item_not_received' | 'significantly_not_as_described' | 'unauthorized_transaction' | 'product_unacceptable', required — The different types of issues a resolution can be
  - `member` object, nullable, required — The membership record associated with the disputed payment. Null if the membership no longer exists.
    - `id` string, required — The unique identifier for the extra public member.
  - `merchant_appealed` boolean, required — Whether the merchant has filed an appeal after the initial resolution decision.
  - `merchant_response_actions` ResolutionCenterCaseMerchantResponses[], required — The list of actions currently available to the merchant.
  - `payment` object, required — The payment record that is the subject of this resolution case.
    - `created_at` string, date-time, required — The datetime the payment was created.
    - `currency` 'usd' | 'sgd' | 'inr' | 'aud' | 'brl' | 'cad' | 'dkk' | 'eur' | 'nok' | 'gbp' | 'sek' | 'chf' | 'hkd' | 'huf' | 'jpy' | 'mxn' | 'myr' | 'pln' | 'czk' | 'nzd' | 'aed' | 'eth' | 'ape' | 'cop' | 'ron' | 'thb' | 'bgn' | 'idr' | 'dop' | 'php' | 'try' | 'krw' | 'twd' | 'vnd' | 'pkr' | 'clp' | 'uyu' | 'ars' | 'zar' | 'dzd' | 'tnd' | 'mad' | 'kes' | 'kwd' | 'jod' | 'all' | 'xcd' | 'amd' | 'bsd' | 'bhd' | 'bob' | 'bam' | 'khr' | 'crc' | 'xof' | 'egp' | 'etb' | 'gmd' | 'ghs' | 'gtq' | 'gyd' | 'ils' | 'jmd' | 'mop' | 'mga' | 'mur' | 'mdl' | 'mnt' | 'nad' | 'ngn' | 'mkd' | 'omr' | 'pyg' | 'pen' | 'qar' | 'rwf' | 'sar' | 'rsd' | 'lkr' | 'tzs' | 'ttd' | 'uzs' | 'rub' | 'btc' | 'cny' | 'usdt' | 'kzt' | 'awg' | 'whop_usd' | 'xau', required — The available currencies on the platform
    - `id` string, required — The unique identifier for the payment.
    - `paid_at` string, date-time, nullable, required — The time at which this payment was successfully collected. Null if the payment has not yet succeeded. As a Unix timestamp.
    - `subtotal` number, nullable, required — The payment amount before taxes and discounts are applied. In the currency specified by the currency field.
    - `total` number, required — The total amount charged to the customer for this payment, including taxes and after any discounts. In the currency specified by the currency field.
  - `platform_response_actions` ResolutionCenterCasePlatformResponses[], required — The list of actions currently available to the Whop platform for moderating this resolution.
  - `resolution_events` object[], required — The most recent 50 messages, actions, and status changes that have occurred during this resolution case.
    - `action` 'created' | 'responded' | 'accepted' | 'denied' | 'appealed' | 'withdrew' | 'requested_more_info' | 'escalated' | 'dispute_opened' | 'dispute_customer_won' | 'dispute_merchant_won', required — The different types of actions for a resolution event
    - `created_at` string, date-time, required — The datetime the resolution event was created.
    - `details` string, nullable, required — The message body or additional context provided with this resolution event. Null if no details were included.
    - `id` string, required — The unique identifier for the resolution event.
    - `reporter_type` 'merchant' | 'customer' | 'platform' | 'system', required — The different types of reporters for a resolution event
  - `status` 'merchant_response_needed' | 'customer_response_needed' | 'merchant_info_needed' | 'customer_info_needed' | 'under_platform_review' | 'customer_won' | 'merchant_won' | 'customer_withdrew', required — The statuses a resolution object can have
  - `updated_at` string, date-time, required — The datetime the resolution was last updated.
  - `user` object, required — The customer (buyer) who filed this resolution case.
    - `id` string, required — The unique identifier for the user.
    - `name` string, nullable, required — The user's display name shown on their public profile.
    - `username` string, required — The user's unique username shown on their public profile.

## Other responses

- `400` — Bad request
- `401` — Unauthorized
- `403` — Forbidden
- `404` — Not found
- `422` — Verification required
- `429` — Too many requests
- `500` — Internal server error

---

[API](https://skmtc.dev/whop/apis/whop-api.md) · [All operations](https://skmtc.dev/whop/apis/whop-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/whop/whop-api/revisions/60bbb4a6ffbc/schema)