Chargeback Management: Evidence, Deadlines and Operational Responsibilities

The time a cardholder has to raise a dispute is different from the merchant's time to respond. There may also be different deadlines at later stages. Do not take a long cardholder filing window and use it as your evidence-preparation period.

Stripe describes its response window as usually 7–21 days depending on the card network, and tells merchants to respond before the deadline shown for the dispute. [1] Adyen's table gives different periods by scheme, stage and location: its Visa footnote states nine days for disputes on locally processed US and Canadian payments opened from 21 July 2025, and eighteen days for the other cases it describes. [2] These are provider-scoped examples, not a universal response calendar.

Copy the actual case deadline and timezone into the team's work queue, retain its source and set an earlier internal approval time. If the notice and portal appear inconsistent, escalate promptly to the provider and plan against the earlier displayed time until it is clarified. Do not invent an extension or assume that emailing support stops the clock.

A request for information, a formal chargeback and a later escalation are not interchangeable. The provider's current case status determines which actions are open. Establish whether a submission is required, whether the case is automatically handled under an enrolled programme, and whether an earlier action has already committed the response.

Check notification routing as part of ordinary operations. Someone needs to see new cases when a colleague is absent, a mailbox filter changes or the store is paused. Where your integration receives dispute events, test that they create an assigned task rather than merely a log entry. Stripe documents email, Dashboard and event notifications for disputes. [1]

Read the cardholder's allegation and any available issuer documents before choosing evidence. If you agree that the merchant failed to supply what was promised, escalate the customer remedy through the applicable provider process. If the records support a challenge, document the specific point in dispute. A valid payment authorisation by itself does not answer a complaint that the service was cancelled or the goods were never delivered.

Build the response around the fact that would resolve the claim. For a non-delivery complaint, connect the purchased item to the fulfilment and delivery record. For a cancelled subscription, establish the consent, cancellation request and disputed renewal chronology. For a refund complaint, connect the original payment to the actual credit status, amount and reference.

Mastercard's merchant guidance emphasises that evidence should address the chargeback reason code. Adyen likewise publishes different defence requirements by dispute type and warns that meeting them does not guarantee a win. [7][3] The preparation table below is a starting point for gathering records; the case-specific requirements still govern what can be submitted.

Explain how each attachment relates to the disputed payment. An IP address, a signed delivery record or a screenshot may support a particular fact, but none should be described as automatically defeating every claim. If a record contradicts the merchant's explanation, resolve that discrepancy honestly. Do not fill a gap with reconstructed consent, edited timestamps or a policy that was introduced after the purchase.

Use the provider's deadline to work backwards. Suppose a fictional case requires submission by 12 November at 17:00 UTC. The merchant might set evidence collection for 11 November at 09:00 UTC, independent review for 13:00 UTC that day, and submission verification for 12 November at 12:00 UTC. Those times are an internal planning example, not network rules or permission to wait that long in another case.

Support supplies the relevant customer conversation; fulfilment supplies the order and delivery trail; product or engineering supplies the necessary service records; finance reconciles payment and refund entries. The case owner assembles the chronology, and a reviewer checks that it answers the claim. Each handoff should identify missing information early enough to act on it.

The backup owner needs the same access and authority to progress the case. Test the handoff before there is a real deadline. A shared inbox is a notification channel, not proof that somebody has accepted responsibility or that an evidence file was actually sent.

A useful packet lets a reviewer understand the transaction without access to your internal systems. Open with a short chronology containing the order and payment references, what was purchased, the disputed issue and the records supporting your answer. Use legible screenshots or exports showing the relevant historical terms and events.

Stripe's evidence guidance favours concise, relevant material and documents the formatting constraints for submission. [4] Verify the file types, size and page limits applicable to your provider and dispute type rather than reusing one upload specification everywhere. An external link is not a reliable substitute for evidence the submission channel requires you to include.

For Stripe's documented Dashboard response, submission is a single opportunity: the response and files cannot subsequently be edited or supplemented. [1] Shopify describes a different preparation workflow: saved evidence can remain editable before its due date, with automatic submission then; choosing its early-submit action ends further editing. [5] Confirm the behaviour for the actual account and stage. Distinguish saving a draft, approving it internally and submitting it externally.

Collect the evidence needed to explain the transaction, and limit who can view it. An unrestricted support folder should not become a repository of full payment-card details, identity documents or unrelated customer correspondence. Keep access to originals controlled and prepare the necessary submission copies through the approved process.

PCI SSC states that merchants cannot retain card verification codes after authorisation, even when encrypted or when the customer has agreed. [6] A record of a provider's verification result is different from retaining the code itself. Do not ask staff to create a security-code archive for future disputes.

Record the provenance of the evidence: source system, event time, export time, relevant timezone and person responsible for the extraction. Explain whether a screenshot shows the terms at purchase or the current site. If a piece of evidence includes third-party information or sensitive content, get the appropriate privacy or specialist review before disclosure. More data can make a submission harder to evaluate while creating avoidable exposure; relevance and accuracy matter more than volume.

When a customer says they have withdrawn a dispute, obtain the relevant information and continue following the provider's instructions until the case status confirms what happened. Shopify advises merchants to submit evidence of a customer's request to cancel the dispute; that conversation is not itself the issuer's decision. [5]

Check refund status before taking another money-moving action. Stripe says a refund outside its dispute process cannot be issued while the dispute is open. [8] Do not promise a separate refund or send money through another channel without reconciling what the dispute process has already done. If part of the sale has already been refunded, show that credit and the remaining amount explicitly.

Finance should record disputed principal, fees, prior credits and any later reversal separately. An outcome marked won and a posted bank receipt are different events to reconcile. Keep the provider references with the case and trace the adjustments into the payout report. Never treat the same returned amount as both a refund recovery and a dispute recovery.

Suppose ten challenged cases have reached a final outcome. Six wins concern $50 payments, and four losses concern $500 payments. The case win rate is 60%: six out of ten. The disputed principal associated with wins is $300 out of $2,300, approximately 13.0%. A case-count success rate alone hides where most of the value was lost.

Assume another twelve cases, totalling $1,800, remain open. Keep them outside both resolved-case denominators and report their age and next deadlines separately. The $300 figure is gross principal associated with won cases in this example, not net profit or proof that a payout has arrived; fees, staff effort and ledger adjustments require their own accounting.

Use the same closed cohort when comparing periods. Also track missed deadlines, accepted cases, outstanding evidence requests and recurring causes. These management measures are not the card networks' monitoring ratios. Ask the provider which programme metrics and thresholds apply to the account, and retain their definitions instead of relabelling an internal recovery percentage as a scheme compliance measure.