Disputes and evidence

How Stripe and PayPal disputes reach a case, deadline reminders, building the evidence PDF, staging, submitting and accepting.

Once a Stripe or PayPal account is connected (see Stripe and PayPal), every new dispute lands in the buyer’s case. You answer it from there, with the conversation you already had as evidence.

How a dispute reaches a case

When the processor sends a dispute webhook, Rebutdesk verifies it, reads the current dispute from the processor, and then:

  1. Finds the buyer. First by the disputed payment, if Rebutdesk already knows it; then by the buyer’s ID at the processor (for example the Stripe customer); then by email. If none match, a new contact is created from the dispute’s name and email.
  2. Picks the case. The dispute joins the buyer’s most recently active case that is not closed. If there is none, a new case opens with the subject “Dispute: ”, priority high, tagged dispute and stripe or paypal.
  3. Updates the case. The case gets the dispute tag and at least high priority. A pending or resolved case goes back to open. The timeline gets an entry such as “Stripe dispute opened: $120.00, Product not received. Respond by 2026-11-12.”

Each dispute is recorded once, however many times the processor sends it. Later events update it: status, deadline, amount or stage changes add a timeline entry (“Stripe dispute is under review.”, “New response deadline …”), and an event older than the last one seen is ignored. When a dispute needs a response again, its case is reopened.

If a dispute joined the wrong case, use Merge into another case or Split into a new case on the case; disputes move with merged cases.

The Disputes page

Disputes in the sidebar lists every dispute in the workspace: those that need a response first, soonest deadline first, then the rest by last change. The sidebar link shows how many are due (“2 due”), and the inbox view Disputes lists cases tagged dispute.

Statuses shown:

Status Meaning
Needs response Waiting for your evidence or decision.
Under review Evidence was submitted, or the processor is reviewing.
Won Decided in your favor.
Lost Decided for the buyer.
Accepted You accepted the dispute.
Early warning Reserved for plugins; the built-in Stripe and PayPal channels do not use it.

Stripe statuses warning_needs_response and needs_response show as Needs response, warning_under_review and under_review as Under review, won, warning_closed and prevented as Won, and lost as Lost. Stripe inquiries show the stage “inquiry”. PayPal disputes waiting for the seller or open show as Needs response; resolved PayPal disputes show as Won for the outcomes RESOLVED_SELLER_FAVOUR, CANCELED_BY_BUYER and DENIED, Accepted for ACCEPTED, and Lost otherwise. Other PayPal statuses show as Under review, and the PayPal stage (for example inquiry or chargeback) is shown on the dispute.

Deadlines and reminders

While a dispute needs a response, the case and the Disputes page show a countdown such as “2d 4h left”. It turns amber under 72 hours, red under 24 hours, and reads “Overdue” after the deadline.

The background job (every minute) adds a reminder to the case timeline 72 hours and again 24 hours before the deadline, for example “Dispute response due in about 23 hours (2026-11-12 17:00 UTC).” A dispute first seen less than 24 hours out gets only the 24-hour reminder. Reminders appear in the timeline and in open consoles; they are not emailed.

The dispute card

On the case, each dispute has a card with the amount, status, countdown, reason, Respond by date, dispute ID, linked payment, stage and card network. For PayPal it also shows what PayPal asked for (“PayPal asked for: …”), and warns when PayPal is not taking evidence on the dispute right now.

While the dispute needs a response, the card has Prepare evidence (or Continue evidence once saved) and Preview PDF.

Building the evidence

Preparing and saving evidence needs the “Change status, assignee and tags” permission. Staging, submitting and accepting need “Submit or accept disputes” (admins by default).

The evidence form has three parts:

  • Statement to the bank. Your rebuttal, up to 20,000 characters: what was sold, when it was delivered, and why the charge is valid.
  • Stripe evidence fields or PayPal evidence fields. The processor’s own fields. The first 8 are shown; the rest are under More Stripe fields.
  • Timeline in the PDF. Tick the timeline entries to include. Messages, internal notes and dispute opened or updated entries can be picked. By default all messages with the buyer are ticked; internal notes are off unless you tick them.

Some fields start filled in from the case: the customer’s name and email on Stripe, refund IDs of refunds made on the case on PayPal, and on PayPal the first evidence type PayPal asked for.

Buttons:

  • Save draft saves the selection.
  • Preview PDF saves and opens the PDF in a new tab.
  • Stage on Stripe (Stripe only) saves the evidence on the Stripe dispute without sending it to the bank.
  • Submit to bank sends the evidence. You confirm first: you get one submission per dispute and it cannot be changed afterwards.
  • Accept dispute concedes. See below.

Versions

Evidence is saved as versions. A draft (or a failed attempt) is edited in place. Once a version is staged or submitted, further edits create a new version, so the record of what was sent stays intact. Submitting exactly what you just staged sends the same version. A submitted version cannot be submitted again, and evidence can only be sent while the dispute needs a response.

The card shows the latest version’s state: “Draft saved”, “Staged, not yet submitted”, “Submitted” or “Could not be sent” with the processor’s error. Each stage, submit or failure also adds a timeline entry, for example “Evidence version 2 submitted to Stripe.” After a successful submit the dispute shows Under review until the processor reports the outcome.

The evidence PDF

Rebutdesk renders one PDF for the dispute:

  • A cover with your company name, the processor, dispute ID, reason, amount, response deadline, customer and payment.
  • Your statement.
  • The timeline entries you chose, oldest first, each with date and time (UTC), who wrote it (the buyer, “ support” with the agent’s name, or “ assistant” for AI replies) and the kind of entry.

Limits it enforces:

  • 19 pages at most. Mastercard accepts at most 19 pages per response. Entries that do not fit are left out, latest first, and the cover says how many were left out.
  • 4,000 characters per timeline entry. Longer entries are cut.
  • Standard PDF fonts only. Characters outside the Western European character set (WinAnsi), such as Chinese, Japanese, Cyrillic or emoji, are replaced with ?. Write the statement in a Latin-script language, and check the preview when the conversation is in another script.

The file is named dispute-<dispute id>-evidence.pdf. The response headers of the preview also report the page count and how many entries were left out.

Sending to Stripe

On Stage on Stripe or Submit to bank, Rebutdesk:

  1. Uploads the PDF to Stripe as a dispute evidence file.
  2. Puts it in the evidence slot that fits the dispute reason: shipping_documentation for product not received, customer_communication for fraudulent and unrecognized, cancellation_policy for subscription canceled, refund_policy for credit not processed, duplicate_charge_documentation for duplicate, and uncategorized_file otherwise.
  3. Sends your statement as uncategorized_text, so it is readable without opening the PDF, and the Stripe evidence fields you filled in.
  4. Updates the dispute with submit set to false (stage) or true (submit).

Stripe allows evidence files of at most 4.5 MB in total. Rebutdesk does not check the PDF size before sending; if Stripe refuses it, the error appears on the card and you can deselect entries and try again.

Sending to PayPal

PayPal has no staging, so only Submit to bank is offered. The PDF is attached to one evidence item:

  • Evidence type: one of PayPal’s types (for example PROOF_OF_FULFILLMENT, PROOF_OF_REFUND, MERCHANT_RESPONSE or OTHER). PayPal accepts only some types for each reason and stage; if it answers EVIDENCE_TYPE_IS_NOT_ALLOWED, try another type.
  • Carrier, Other carrier name and Tracking number: required for the tracking types (PROOF_OF_FULFILLMENT, ONLINE_TRACKING_INFORMATION, ADDITIONAL_TRACKING_INFORMATION, PROOF_OF_DELIVERY_SIGNATURE). A carrier that is not in PayPal’s list is sent as OTHER with its name.
  • PayPal refund IDs: required for PROOF_OF_REFUND, separated by commas.
  • Notes to PayPal: up to 2,000 characters. Left empty, your statement is sent (cut to 2,000 characters).

Each file sent to PayPal must be 10 MB or less.

Accepting a dispute

Accept dispute concedes: the buyer keeps the money and you cannot contest it later. You confirm first. Rebutdesk closes the dispute on Stripe, or accepts the claim on PayPal with the note “The merchant accepted this claim.” The dispute shows Accepted and the timeline gets “Stripe dispute accepted. The buyer keeps the funds.”

Won and lost

Outcomes arrive by webhook. When Stripe or PayPal decides, the dispute’s status changes to Won or Lost (or Accepted), and the case timeline gets an entry such as “PayPal dispute was won.” PayPal webhooks can arrive minutes late, so the outcome may show up in Rebutdesk a little after it shows in PayPal.

Dispute events are also available to your own systems through the REST API and webhooks: dispute.opened, dispute.updated and dispute.evidence_submitted.

Next: AI