Accept Dispute
Accepts a chargeback, conceding it to the customer instead of contesting it. The payment processor closes the dispute as lost. This is final — the dispute cannot be contested afterwards. Only a dispute whose acceptable is true can be accepted.
Autorizaciones
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.
Encabezados
A unique key that makes this request safe to retry. See Idempotent requests.
255"d9105228-4a08-46b1-8b91-42fed586d383"
Respuesta
dispute accepted
Why the customer says they are disputing, normalized across processors and card networks. other covers a processor reason Whop has not categorized yet.
fraudulent, unrecognized, declined_authorization, product_not_received, product_unacceptable, subscription_canceled, credit_not_processed, duplicate, processing_error, documentation_request, bank_cannot_process, other "other"
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.
needs_response, warning_needs_response, under_review, warning_under_review, generating_response, won, lost, prevented, warning_closed "needs_response"
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.
null

