Representment (dispute evidence)
Submitting targeted proof through your payment provider to contest a chargeback and try to recover the disputed money.
See it
What it is
When a chargeback lands, representment is how the merchant fights back. The evidence goes through the processor or acquirer to show that the transaction was valid, fulfilled, and consistent with the specific dispute reason.
Use it when the order record gives you relevant proof, such as delivery confirmation, usage logs, cancellation terms, a receipt, customer messages, or authentication results. Build the packet around the reason code rather than dumping every document you have.
Gotcha: the response deadline is short and missing it usually means losing by default. Evidence rules and later escalation steps vary by network and dispute type, and submitting a packet does not guarantee a win. Do not also refund an already disputed charge unless your processor explicitly tells you how that case will be handled.
Ask AI for it
Build a reason-code-driven representment workflow with the Stripe Disputes API. On charge.dispute.created, store the amount, reason code, evidence_details.due_by, order, and customer, then open an evidence task with the cutoff shown prominently. Assemble relevant proof from receipts, delivery or usage logs, authentication results, accepted terms, cancellation records, and customer messages, preserve the original files, preview the packet, and submit evidence with stripe.disputes.update idempotently. Track submitted, won, lost, and escalated outcomes and block refunds while the dispute is open.