National merchant dispute guidance

How Long Does a Merchant Have to Respond to a Chargeback?

A merchant does not have one universal response period for every chargeback. The deadline depends on the payment network, dispute stage, acquirer or processor workflow, and case details. Stripe's current merchant guidance describes a usual window of 7 to 21 days depending on the card network, but the date displayed in the merchant's actual dispute notice or provider portal is the deadline to follow.

Direct answer

Use the case-specific due date, not a generic countdown

Provider documentation may offer a typical range, but a merchant should begin with the exact deadline shown for the live dispute. Card-network rules include multiple stages and condition-specific time frames, and a provider may set an earlier operational cutoff so it can review and transmit a response.

Act immediately: if the notice, portal, email, and API show different dates, ask the acquirer or processor which date controls and work to the earliest displayed cutoff while the question is resolved.

Why deadlines vary

Four details shape the response window

Payment network

Each network operates its own dispute rules and stages. A time period used for one network should not be copied to another without confirming the case.

Dispute stage

An inquiry, initial chargeback, pre-arbitration step, or other case status can have a different action and deadline. Confirm what response the notice actually requests.

Provider cutoff

Acquirers, processors, and payment platforms receive network messages and submit merchant evidence. Their portal deadline is often the practical merchant cutoff.

Case eligibility

Some disputes cannot be challenged or may already be past due. The case record should show whether the merchant can accept, respond, or take another available action.

First-day workflow

What to do when a dispute arrives

Capture the notice

Record the case ID, disputed transaction, reason or condition, amount, network, response options, due date, and the time zone associated with the cutoff. Save the original notification.

Assign an owner

Route the case to a person who can retrieve order, fulfillment, refund, policy, and customer-communication records. Name a backup so absences do not consume the response window.

Choose accept or challenge

Review the claim and available records early. If the merchant challenges it, build a concise response that addresses the stated reason rather than uploading every document available.

Submit before the final day

Allow time for file conversion, portal errors, internal approval, and provider questions. Confirm that the case status changes or that a submission receipt is available.

Deadline sources

Where to verify the controlling date

Provider dispute portal

Open the individual case and look for the evidence due date, respond-by date, or countdown. Check whether the displayed value includes a time of day and time zone.

Dispute notice

Compare the portal with the email, letter, or downloadable notice. Keep the notice because it documents what the merchant received and when.

Provider API

For automated workflows, monitor the provider's due-date and status fields. Alert on new cases and approaching deadlines, and test for missed webhook deliveries.

Acquirer or processor support

Escalate discrepancies promptly. Ask which stage applies, which date controls, whether a response is permitted, and how successful submission will be confirmed.

Operational controls

Build a workflow that protects short windows

Centralize notifications

Maintain current dispute contacts and send portal, email, and webhook alerts to a monitored queue rather than one person's inbox.

Keep evidence findable

Link transactions to order confirmations, delivery or service records, refund activity, policies accepted at purchase, and relevant customer communications.

Set internal targets

Create review and approval checkpoints ahead of the external cutoff. Use escalation rules for cases that lack an owner or required records.

Track completion

Record whether the case was accepted or challenged, when the response was submitted, what evidence was included, and the confirmation supplied by the provider.

Common questions

Merchant response-deadline FAQ

Do merchants always receive 7 to 21 days?

No. That is a typical range in Stripe's current card-dispute guidance, not a universal entitlement. Use the deadline shown for the merchant's actual case.

Is the network deadline the same as the provider deadline?

Not necessarily. A provider may require evidence earlier so it can process and transmit the response. Follow the provider's live case instructions.

What happens if the deadline is missed?

The merchant can lose the opportunity to challenge the dispute through that response stage. Confirm the status with the provider rather than assuming a late upload will be accepted.

Can evidence be edited after submission?

Provider rules vary. Stripe's current guidance says its merchant response is final after submission, so merchants should review the complete packet before sending it.

Last editorial review: August 11, 2026. Sources reviewed: current Stripe merchant dispute documentation and Mastercard's May 19, 2026 merchant chargeback guide. Network and provider procedures can change.

Next step

Map ownership before the next dispute arrives

Payments Max can help organize notification routing, evidence sources, provider questions, and operational review steps for merchant disputes.

Contact Payments Max

To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.

CONTACT US