> ## Documentation Index > Fetch the complete documentation index at: https://docs.whop.com/llms.txt > Use this file to discover all available pages before exploring further. # Update evidence > Update a dispute with evidence data to attempt to win the dispute. Required permissions: - `payment:dispute` - `plan:basic:read` - `access_pass:basic:read` - `company:basic:read` - `payment:basic:read` - `member:email:read` - `member:basic:read` - `member:phone:read` ## OpenAPI ````yaml /openapi/api-v1-stable.json post /disputes/{id}/update_evidence openapi: 3.1.0 info: description: >- The Whop REST API. Please see https://docs.whop.com/developer/api/getting-started for more details. termsOfService: https://whop.com/tos-developer-api/ title: Whop API version: 1.0.0 x-api-version-date: '2026-08-21' servers: - description: Production Whop API url: https://api.whop.com/api/v1 - description: Sandbox Whop API url: https://sandbox-api.whop.com/api/v1 security: [] tags: - description: Products name: Products - description: Payments name: Payments - description: Refunds name: Refunds - description: Disputes name: Disputes - description: Dispute alerts name: Dispute alerts - description: Resolution center cases name: Resolution center cases - description: Checkout configurations name: Checkout configurations - description: Setup intents name: Setup intents - description: Payment methods name: Payment methods - description: Invoices name: Invoices - description: Promo codes name: Promo codes - description: Card transactions name: Card transactions - description: Ledger accounts name: Ledger accounts - description: Withdrawals name: Withdrawals - description: Payout methods name: Payout methods - description: Verifications name: Verifications - description: Identity profiles name: Identity profiles - description: Payout accounts name: Payout accounts - description: Topups name: Topups - description: Companies name: Companies - description: Authorized users name: Authorized users - description: Fee markups name: Fee markups - description: Members name: Members - description: Memberships name: Memberships - description: Leads name: Leads - description: Entries name: Entries - description: Shipments name: Shipments - description: Reviews name: Reviews - description: Company token transactions name: Company token transactions - description: Affiliates name: Affiliates - description: Experiences name: Experiences - description: Forums name: Forums - description: Forum posts name: Forum posts - description: Chat channels name: Chat channels - description: Support channels name: Support channels - description: Messages name: Messages - description: Reactions name: Reactions - description: Dm members name: Dm members - description: Dm channels name: Dm channels - description: Notifications name: Notifications - description: Courses name: Courses - description: Course chapters name: Course chapters - description: Course lessons name: Course lessons - description: Course students name: Course students - description: Course lesson interactions name: Course lesson interactions - description: Apps name: Apps - description: Webhooks name: Webhooks - description: App builds name: App builds - description: Access tokens name: Access tokens - description: Account links name: Account links - description: Files name: Files - description: Ai chats name: Ai chats - description: Bounties name: Bounties - description: Stats name: Stats - description: Conversions name: Conversions - description: Ad reports name: Ad reports paths: /disputes/{id}/update_evidence: post: tags: - Disputes summary: Update evidence description: |- Update a dispute with evidence data to attempt to win the dispute. Required permissions: - `payment:dispute` - `plan:basic:read` - `access_pass:basic:read` - `company:basic:read` - `payment:basic:read` - `member:email:read` - `member:basic:read` - `member:phone:read` operationId: updateEvidenceDispute parameters: - description: The unique identifier of the dispute to update. in: path name: id required: true schema: example: dspt_xxxxxxxxxxxxx type: string requestBody: content: application/json: schema: description: Parameters for UpdateDispute properties: access_activity_log: description: >- An IP access activity log showing the customer used the service. type: - string - 'null' billing_address: description: >- The billing address associated with the customer's payment method. type: - string - 'null' cancellation_policy_attachment: description: >- A file upload containing the company's cancellation policy document. properties: id: description: The ID of an existing file object. type: string required: - id title: FileInputWithId type: - object - 'null' cancellation_policy_disclosure: description: >- The company's cancellation policy text to submit as evidence. type: - string - 'null' customer_communication_attachment: description: >- A file upload containing evidence of customer communication. Must be a JPEG, PNG, GIF, or PDF. properties: id: description: The ID of an existing file object. type: string required: - id title: FileInputWithId type: - object - 'null' customer_email_address: description: >- The email address of the customer associated with the disputed payment. type: - string - 'null' customer_name: description: >- The full name of the customer associated with the disputed payment. type: - string - 'null' notes: description: >- Additional notes or context to submit as part of the dispute evidence. type: - string - 'null' product_description: description: >- A description of the product or service that was provided to the customer. type: - string - 'null' refund_policy_attachment: description: >- A file upload containing the company's refund policy document. properties: id: description: The ID of an existing file object. type: string required: - id title: FileInputWithId type: - object - 'null' refund_policy_disclosure: description: The company's refund policy text to submit as evidence. type: - string - 'null' refund_refusal_explanation: description: An explanation of why the refund request was refused. type: - string - 'null' service_date: description: >- The date when the product or service was delivered to the customer. type: - string - 'null' uncategorized_attachment: description: >- A file upload for evidence that does not fit into the other categories. properties: id: description: The ID of an existing file object. type: string required: - id title: FileInputWithId type: - object - 'null' required: [] type: object required: false responses: '200': content: application/json: schema: $ref: '#/components/schemas/Dispute' description: A successful response '400': content: application/json: example: error: code: parameter_missing message: 'Missing required parameter: amount.' param: amount type: invalid_request_error schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Bad request '401': content: application/json: example: error: message: Invalid or missing API key type: unauthorized schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Unauthorized '403': content: application/json: example: error: message: You do not have permission to access this resource type: forbidden schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Forbidden '404': content: application/json: example: error: message: Resource not found type: not_found schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Not found '422': content: application/json: example: error: null schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Verification required '429': content: application/json: example: error: null schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Too many requests '500': content: application/json: example: error: message: An unexpected error occurred type: internal_server_error schema: properties: error: properties: code: description: >- A short string indicating the specific error code, e.g. 'parameter_missing', 'parameter_invalid', 'invalid_json' type: - string - 'null' message: type: string param: description: The parameter that caused the error, if applicable type: - string - 'null' type: type: string required: - type - message type: object required: - error type: object description: Internal server error security: - bearerAuth: - payment:dispute - plan:basic:read - access_pass:basic:read - company:basic:read - payment:basic:read - member:email:read - member:basic:read - member:phone:read components: schemas: Dispute: description: >- A dispute is a chargeback or payment challenge filed against a company, including evidence and response status. properties: access_activity_log: description: >- A log of IP-based access activity for the customer on Whop, submitted as evidence in the dispute. example: 192.168.1.1 - 2024-01-15 12:00:00 UTC type: - string - 'null' amount: description: >- The disputed amount in the specified currency, formatted as a decimal. example: 6.9 type: number billing_address: description: >- The customer's billing address from their payment details, submitted as evidence in the dispute. example: 123 Main St, New York, NY 10001 type: - string - 'null' cancellation_policy_attachment: description: >- The cancellation policy document uploaded as dispute evidence. Null if no cancellation policy has been provided. properties: content_type: description: >- Uploaded file MIME type, such as image/jpeg, video/mp4, or audio/mpeg. example: image/jpeg type: - string - 'null' filename: description: >- The original filename of the uploaded attachment, including its file extension. example: document.pdf type: - string - 'null' id: description: >- Represents a unique identifier that is Base64 obfuscated. It is often used to refetch an object or as key for a cache. The ID type appears in a JSON response as a String; however, it is not intended to be human-readable. When expected as an input type, any string (such as `"VXNlci0xMA=="`) or integer (such as `4`) input value will be accepted as an ID. type: string url: description: >- A pre-optimized URL for rendering this attachment on the client. This should be used for displaying attachments in apps. example: https://media.whop.com/abc123/optimized.jpg type: - string - 'null' required: - id - filename - content_type - url type: - object - 'null' cancellation_policy_disclosure: description: >- A text disclosure describing the company's cancellation policy, submitted as dispute evidence. example: All sales are final. No refunds after 30 days. type: - string - 'null' company: description: The company that the dispute was filed against. properties: id: description: The unique identifier for the company. example: biz_xxxxxxxxxxxxxx type: string title: description: The written name of the company. type: string required: - id - title type: - object - 'null' created_at: description: The datetime the dispute was created. example: '2023-12-01T05:00:00.401Z' format: date-time type: - string - 'null' currency: $ref: '#/components/schemas/Currencies' description: The three-letter ISO currency code for the disputed amount. customer_communication_attachment: description: >- Evidence of customer communication or product usage, uploaded as a dispute attachment. Null if not provided. properties: content_type: description: >- Uploaded file MIME type, such as image/jpeg, video/mp4, or audio/mpeg. example: image/jpeg type: - string - 'null' filename: description: >- The original filename of the uploaded attachment, including its file extension. example: document.pdf type: - string - 'null' id: description: >- Represents a unique identifier that is Base64 obfuscated. It is often used to refetch an object or as key for a cache. The ID type appears in a JSON response as a String; however, it is not intended to be human-readable. When expected as an input type, any string (such as `"VXNlci0xMA=="`) or integer (such as `4`) input value will be accepted as an ID. type: string url: description: >- A pre-optimized URL for rendering this attachment on the client. This should be used for displaying attachments in apps. example: https://media.whop.com/abc123/optimized.jpg type: - string - 'null' required: - id - filename - content_type - url type: - object - 'null' customer_email_address: description: >- The customer's email address from their payment details, included in the evidence packet sent to the payment processor. Editable before submission. example: customer@example.com type: - string - 'null' customer_name: description: >- The customer's full name from their payment details, included in the evidence packet sent to the payment processor. Editable before submission. example: Jane Doe type: - string - 'null' editable: description: Whether the dispute evidence can still be edited and submitted. type: - boolean - 'null' id: description: The unique identifier for the dispute. example: dspt_xxxxxxxxxxxxx type: string needs_response_by: description: >- The deadline by which dispute evidence must be submitted. Null if no response deadline is set. example: '2023-12-01T05:00:00.401Z' format: date-time type: - string - 'null' notes: description: >- Additional freeform notes submitted by the company as part of the dispute evidence. example: Customer used the product for 3 months before disputing. type: - string - 'null' payment: description: The original payment that was disputed. properties: billing_reason: description: >- The machine-readable reason this charge was created, such as initial subscription purchase, renewal cycle, or one-time payment. oneOf: - $ref: '#/components/schemas/BillingReasons' - type: 'null' card_brand: description: >- Card network reported by the processor (e.g., 'visa', 'mastercard', 'amex'). Present only when the payment method type is 'card'. oneOf: - $ref: '#/components/schemas/CardBrands' - type: 'null' card_last4: description: >- The last four digits of the card used to make this payment. Null if the payment was not made with a card. example: '4242' type: - string - 'null' created_at: description: The datetime the payment was created. example: '2023-12-01T05:00:00.401Z' format: date-time type: string currency: $ref: '#/components/schemas/Currencies' description: >- The three-letter ISO currency code for this payment (e.g., 'usd', 'eur'). dispute_alerted_at: description: When an alert came in that this transaction will be disputed example: '2023-12-01T05:00:00.401Z' format: date-time type: - string - 'null' id: description: The unique identifier for the payment. example: pay_xxxxxxxxxxxxxx type: string member: description: The member attached to this payment. properties: id: description: The unique identifier for the company member. type: string phone: description: The phone number for the member, if available. type: - string - 'null' required: - id - phone type: - object - 'null' membership: description: The membership attached to this payment. properties: id: description: The unique identifier for the membership. example: mem_xxxxxxxxxxxxxx type: string status: $ref: '#/components/schemas/MembershipStatus' description: The state of the membership. required: - id - status type: - object - 'null' paid_at: description: >- The time at which this payment was successfully collected. Null if the payment has not yet succeeded. As a Unix timestamp. example: '2023-12-01T05:00:00.401Z' format: date-time type: - string - 'null' payment_instrument: description: >- The instrument this payment was made with, shaped for display: the method type, a buyer-facing name, the standard icon set, and the card facts when it was a card. Null when the receipt names no payment method. properties: display_name: description: >- Buyer-facing instrument name — "Visa •••• 4242" when the card surfaced, else the method's own name ("Klarna"). type: string icons: description: >- The standard icon set: square and card shapes, each in light and dark colorways. properties: square: description: The square tile (32x32). properties: dark: description: The colorway for dark surfaces. properties: svg: description: >- The vector file. Prefer this everywhere SVG renders. type: string required: - svg type: object light: description: The colorway for light surfaces. properties: svg: description: >- The vector file. Prefer this everywhere SVG renders. type: string required: - svg type: object required: - light - dark type: object required: - square type: object installment_count: description: >- Installment methods only: how many payments the charge splits into. Data, not copy — compose and translate the label client-side. example: 42 type: - integer - 'null' payment_method_type: description: >- The payment method type identifier, e.g. `card`, `klarna`, `apple_pay`. type: string required: - payment_method_type - display_name - installment_count - icons type: - object - 'null' payment_method_type: description: >- The type of payment instrument used for this payment (e.g., card, Cash App, iDEAL, Klarna, crypto). Null when the processor does not supply a type. oneOf: - $ref: '#/components/schemas/PaymentMethodTypes' - type: 'null' subtotal: description: The subtotal to show to the creator (excluding buyer fees). example: 6.9 type: - number - 'null' total: description: The total to show to the creator (excluding buyer fees). example: 6.9 type: - number - 'null' usd_total: description: The total in USD to show to the creator (excluding buyer fees). example: 6.9 type: - number - 'null' user: description: The user that made this payment. properties: email: description: >- The user's email address. Requires the member:email:read permission to access. Null if not authorized. example: john.doe@example.com type: - string - 'null' id: description: The unique identifier for the user. example: user_xxxxxxxxxxxxx type: string name: description: The user's display name shown on their public profile. example: John Doe type: - string - 'null' username: description: The user's unique username shown on their public profile. example: johndoe42 type: string required: - id - name - username - email type: - object - 'null' required: - id - total - subtotal - usd_total - currency - created_at - paid_at - dispute_alerted_at - payment_method_type - billing_reason - card_brand - card_last4 - payment_instrument - user - member - membership type: - object - 'null' plan: description: >- The plan associated with the disputed payment. Null if the dispute is not linked to a specific plan. properties: id: description: The unique identifier for the plan. example: plan_xxxxxxxxxxxxx type: string required: - id type: - object - 'null' product: description: >- The product associated with the disputed payment. Null if the dispute is not linked to a specific product. properties: id: description: The unique identifier for the product. example: prod_xxxxxxxxxxxxx type: string title: description: >- The display name of the product shown to customers on the product page and in search results. example: Pickaxe Analytics type: string required: - id - title type: - object - 'null' product_description: description: >- A description of the product or service provided, submitted as dispute evidence. example: Monthly subscription to premium analytics dashboard. type: - string - 'null' reason: description: A human-readable reason for the dispute. example: Product Not Received type: - string - 'null' reason_code: description: >- The card network reason code for the dispute. Null when the payment processor did not provide one. example: '10.4' type: - string - 'null' refund_policy_attachment: description: >- The refund policy document uploaded as dispute evidence. Null if no refund policy has been provided. properties: content_type: description: >- Uploaded file MIME type, such as image/jpeg, video/mp4, or audio/mpeg. example: image/jpeg type: - string - 'null' filename: description: >- The original filename of the uploaded attachment, including its file extension. example: document.pdf type: - string - 'null' id: description: >- Represents a unique identifier that is Base64 obfuscated. It is often used to refetch an object or as key for a cache. The ID type appears in a JSON response as a String; however, it is not intended to be human-readable. When expected as an input type, any string (such as `"VXNlci0xMA=="`) or integer (such as `4`) input value will be accepted as an ID. type: string url: description: >- A pre-optimized URL for rendering this attachment on the client. This should be used for displaying attachments in apps. example: https://media.whop.com/abc123/optimized.jpg type: - string - 'null' required: - id - filename - content_type - url type: - object - 'null' refund_policy_disclosure: description: >- A text disclosure describing the company's refund policy, submitted as dispute evidence. example: Refunds available within 14 days of purchase. type: - string - 'null' refund_refusal_explanation: description: >- An explanation from the company for why a refund was refused, submitted as dispute evidence. example: The customer exceeded the refund window by 60 days. type: - string - 'null' service_date: description: >- The date when the product or service was delivered to the customer, submitted as dispute evidence. example: '2024-01-15' type: - string - 'null' status: $ref: '#/components/schemas/DisputeStatuses' description: >- The current status of the dispute lifecycle, such as needs_response, under_review, won, or lost. uncategorized_attachment: description: >- An additional attachment that does not fit into the standard evidence categories. Null if not provided. properties: content_type: description: >- Uploaded file MIME type, such as image/jpeg, video/mp4, or audio/mpeg. example: image/jpeg type: - string - 'null' filename: description: >- The original filename of the uploaded attachment, including its file extension. example: document.pdf type: - string - 'null' id: description: >- Represents a unique identifier that is Base64 obfuscated. It is often used to refetch an object or as key for a cache. The ID type appears in a JSON response as a String; however, it is not intended to be human-readable. When expected as an input type, any string (such as `"VXNlci0xMA=="`) or integer (such as `4`) input value will be accepted as an ID. type: string url: description: >- A pre-optimized URL for rendering this attachment on the client. This should be used for displaying attachments in apps. example: https://media.whop.com/abc123/optimized.jpg type: - string - 'null' required: - id - filename - content_type - url type: - object - 'null' visa_rdr: description: >- Whether the dispute was automatically resolved through Visa Rapid Dispute Resolution (RDR). type: boolean required: - id - amount - currency - status - editable - created_at - visa_rdr - needs_response_by - reason - reason_code - plan - product - company - payment - access_activity_log - billing_address - cancellation_policy_disclosure - customer_email_address - customer_name - notes - product_description - refund_policy_disclosure - refund_refusal_explanation - service_date - cancellation_policy_attachment - customer_communication_attachment - refund_policy_attachment - uncategorized_attachment type: object Currencies: description: The available currencies on the platform enum: - 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 type: string BillingReasons: description: The reason why a specific payment was billed enum: - subscription_create - subscription_cycle - subscription_update - one_time - manual - subscription type: string CardBrands: description: Possible card brands that a payment token can have enum: - mastercard - visa - amex - discover - unionpay - jcb - diners - link - troy - visadankort - visabancontact - china_union_pay - rupay - jcbrupay - elo - maestro - tarjeta_naranja - cirrus - nspk_mir - verve - ebt - private_label - local_brand - uatp - wexcard - uzcard - meeza - hrg_store_card - girocard - fuel_card - dankort - carnet - atm_card - china_union_payuzcard - codensa - cabal - hipercard - jcblankapay - cmi - aura - unknown type: string MembershipStatus: description: The status of a membership enum: - trialing - active - past_due - completed - canceled - expired - unresolved - drafted - canceling type: string PaymentMethodTypes: description: The different types of payment methods that can be used. enum: - acss_debit - addi - affirm - afterpay_clearpay - alipay - alma - amazon_pay - apple - apple_pay - au_bank_transfer - au_becs_debit - bacs_debit - bancolombia - bancontact - bank_wire - billie - bizum - blik - boleto - bre_b - ca_bank_transfer - capchase_pay - card - card_installments_three - card_installments_six - card_installments_twelve - cashapp - claritypay - coinbase - crypto - custom - customer_balance - demo_pay - efecty - eps - eu_bank_transfer - fpx - gb_bank_transfer - giropay - google_pay - gopay - grabpay - id_bank_transfer - ideal - interac - kakao_pay - klarna - klarna_pay_now - konbini - kr_card - kr_market - kriya - kueski - link - mb_way - m_pesa - mercado_pago - mobilepay - modo - mondu - multibanco - naver_pay - nequi - netbanking - ng_bank - ng_bank_transfer - ng_card - ng_market - ng_ussd - ng_wallet - nz_bank_account - oxxo - p24 - pago_efectivo - pse - pay_by_bank - payco - paynow - paypal - paypay - payto - pix - platform_balance - promptpay - qris - rapipago - rechnung - revolut_pay - samsung_pay - satispay - scalapay - sencillito - sepa_debit - sequra - servipag - sezzle - shop_pay - shopeepay - sofort - south_korea_market - spei - splitit - sunbit - swish - tamara - twint - upi - us_bank_account - us_bank_transfer - venmo - vipps - webpay - wechat_pay - yape - zip - coinflow - unknown type: string DisputeStatuses: description: The possible statuses of a dispute enum: - warning_needs_response - warning_under_review - warning_closed - needs_response - under_review - won - lost - closed - other type: string securitySchemes: bearerAuth: bearerFormat: auth-scheme description: >- An Account API key, account-scoped JWT, App API key, or user OAuth token. Prepend the key or token with `Bearer`, for example `Bearer ***************************`. scheme: bearer type: http ````