Skip to main content
POST
Accept Dispute

Autorisaties

Authorization
string
header
vereist

An Account API key, an App API key, an account access token, an account-scoped user token, or a user OAuth token. Prepend the key or token with Bearer, for example Bearer ***************************. See Auth & API keys for how to get each one.

Scopes

payment:dispute

Headers

Api-Version-Date
string

Pins the request to a dated API version.

Voorbeeld:

"2026-11-17"

Idempotency-Key
string

A unique key that makes this request safe to retry. See Idempotent requests.

Maximum string length: 255
Voorbeeld:

"d9105228-4a08-46b1-8b91-42fed586d383"

Padparameters

id
string
vereist

The dispute ID (dspt_ tag).

Respons

dispute accepted

acceptable
boolean
vereist

Whether the dispute can be conceded to the customer with POST /disputes/{id}/accept. True only for a chargeback still awaiting a response, before evidence_due_at, whose payment processor supports accepting disputes. Inquiries are never acceptable.

Voorbeeld:

true

account_id
string | null
vereist

The account the dispute was filed against, prefixed biz_.

Voorbeeld:

"biz_xxxxxxxxxxxxxx"

amount
number
vereist

The disputed amount, in whole units of currency.

Voorbeeld:

150

buyer
object
vereist

The customer who filed the dispute.

created_at
string
vereist

When the dispute was opened, as an ISO 8601 timestamp.

Voorbeeld:

"2026-01-01T12:00:00.000Z"

currency
string
vereist

Three-letter ISO currency code of the disputed amount.

Voorbeeld:

"usd"

evidence
object
vereist

The evidence packet sent to the processor to contest the dispute.

evidence_due_at
string | null
vereist

The deadline to submit evidence, as an ISO 8601 timestamp. null when the network already auto-resolved the dispute (Visa RDR) with no evidence round, or when the processor hasn't reported a deadline for this dispute.

Voorbeeld:

"2026-01-01T12:00:00.000Z"

evidence_editable
boolean
vereist

Whether evidence can still be changed and submitted.

Voorbeeld:

true

evidence_locked_reason
enum<string> | null
vereist

Why evidence can no longer be edited. null while evidence_editable is true.

Beschikbare opties:
submitted,
response_window_closed,
not_contestable,
null
Voorbeeld:

"submitted"

evidence_submitted_at
string | null
vereist

When the evidence was submitted to the processor, as an ISO 8601 timestamp.

Voorbeeld:

null

fee
object | null
vereist

The dispute fee charged to the account, in the currency it was collected in. null when fee_charged is false.

fee_charged
boolean
vereist

Whether Whop charged the account a dispute fee for this one. false when the payment was fully refunded before the dispute was opened, for a Visa RDR resolution, and for an inquiry.

Voorbeeld:

true

id
string
vereist

Dispute ID, prefixed dspt_.

Voorbeeld:

"dspt_xxxxxxxxxxxxxx"

inquiry
boolean
vereist

Whether this is a pre-dispute inquiry rather than a formal chargeback. Inquiries follow the same lifecycle but move no funds unless one escalates.

Voorbeeld:

false

issuer_comments
object[]
vereist
line_items
object[]
vereist
payment
object
vereist

The payment being disputed.

product_id
string | null
vereist

The product the disputed payment was for, prefixed prod_.

Voorbeeld:

"prod_xxxxxxxxxxxxxx"

reason
enum<string>
vereist

Why the customer says they are disputing, normalized across processors and card networks. other covers a processor reason Whop has not categorized yet.

Beschikbare opties:
fraudulent,
unrecognized,
declined_authorization,
product_not_received,
product_unacceptable,
subscription_canceled,
credit_not_processed,
duplicate,
processing_error,
documentation_request,
bank_cannot_process,
other
Voorbeeld:

"other"

reason_code
string | null
vereist

The raw card-network or processor reason code, such as 10.4. Informational only — reason is not derived from it.

Voorbeeld:

"13.1"

status
enum<string>
vereist

needs_response awaits evidence (after a processor refused a filing, submission_failure_reason says why); generating_response has evidence with the processor, not yet accepted; under_review is with the processor; won/lost are the rulings; prevented settles like lost. warning_ statuses are the inquiry tiers. Past evidence_due_at an open one reports under_review.

Beschikbare opties:
needs_response,
warning_needs_response,
under_review,
warning_under_review,
generating_response,
won,
lost,
prevented,
warning_closed
Voorbeeld:

"needs_response"

submission_failure_reason
string | null
vereist

Why the payment processor refused the last filing, in plain English, while the dispute is back in needs_response. Fix what it names and submit again. Only on retrieve: dispute.updated reports the move back to needs_response, then read this here.

Voorbeeld:

null

updated_at
string
vereist

When the dispute was last changed, as an ISO 8601 timestamp.

Voorbeeld:

"2026-01-01T12:00:00.000Z"

variant_id
string | null
vereist

The variant the disputed payment was made on, prefixed plan_.

Voorbeeld:

"plan_xxxxxxxxxxxxxx"