Skip to content
INDEPENDENT FINANCIAL EDUCATION Clear explanations. Better questions.
EasyLoanWorld Your guide to financial clarity
Explore guides
Menu
FINANCIAL GUIDE Business Finance

Card Payment Disputed? Your First Response in Stripe or Square

Prepare a Stripe or Square card-dispute response that addresses the actual claim, matches evidence to the transaction, and keeps submission deadlines and cash-flow effects visible.

A brown cardboard parcel with an empty white label on a white surface.
Illustrative stock photograph. Photo by Mediamodifier on Unsplash.

Estimated reading time: 8 minutes

Card payment disputes require a response to the specific claim and current case instructions. Compare the Stripe and Square steps below.

For U.S. merchants. This guide covers ordinary card-payment disputes. It excludes ACH, Afterpay, Cash App, compliance cases and litigation.

Follow current case instructions.

Card payment disputes in Stripe

In Dashboard, open the dispute. Check its deadline and claim. An inquiry precedes a formal dispute: submit evidence; if it escalates, respond again. For formal disputes, choose Accept dispute to leave the refund uncontested or Counter dispute to challenge. Assemble evidence addressing the claim before submitting: you can’t edit or add files afterward. Submission starts review; the cardholder’s bank decides.

Square

Open Orders & payments > Disputes and select the case’s information request form. Read the claim, amount and exact documentation deadline. Select No and submit to return funds, or select Yes, answer the questions and attach the requested documents to challenge. Square may request more information; the cardholder’s bank decides. Submission is not a decision. Once decided, Square cannot continue challenging on your behalf.

Example: match the claim to the evidence

Suppose an invented case says the customer did not receive goods from order 482. The first task is to match that case to the correct payment and order. An unrelated delivery confirmation or a long collection of general business policies doesn’t answer what happened to this order.

Illustrative evidence map for a goods-not-received claim
Question Potential record Check before including it
Which purchase is disputed? Order 482’s invoice or receipt and payment record The amount, date and transaction identifier match the case.
What was actually fulfilled? The available delivery or completion record The record belongs to the same order and shows the relevant date and destination or service.
What did the parties say? Relevant messages about delivery, delay, replacement or refund The dates and statements support the explanation you are giving; unresolved issues remain visible.

This is an evidence-organizing example, not a claim that those records exist or will win a dispute. Proof of delivery doesn’t, by itself, answer every other dispute reason, such as whether the payment was authorized. Build a different evidence list if the actual claim is different.

Square’s document guide explains the distinction between fraud and non-fraud claims and gives examples of supporting documents. Use the provider’s requirements for the specific case rather than treating this table as a universal attachment list.

Review card payment disputes before submission

  1. Match the case. Check the case reference, transaction, amount, customer claim and current stage. Keep an inquiry and a later formal dispute separately identified.
  2. Copy the actual deadline. Record the date, time and time zone shown, if supplied. Resolve an unclear deadline promptly; don’t substitute a generic response window.
  3. Write a concise explanation. State what the records show about the claim and refer to the relevant attachment. Don’t fill gaps with assumptions about the customer.
  4. Check the files. Open each attachment, confirm that it’s legible and complete, and check the current accepted formats, size limits and evidence fields.
  5. Review once more, then retain proof. Keep a private copy of the submitted response, files and confirmation. Check for status updates and any further provider request.

For Stripe, prepare the evidence itself in the accepted submission format: its guide says the reviewing bank won’t open outside links to obtain more information. A tracking URL alone is therefore not a substitute for the relevant record in the response. Assemble the complete response before the final submission.

A saved draft, an uploaded file and a submitted response are different states. Verify what the case dashboard actually confirms. “Under review” doesn’t mean the bank has decided in your favor.

Card payment disputes: match the amount and the item

Use a new fictional variation of order 482. Assume an invoice lists two goods priced at $150 and $90, totaling $240, while the case concerns nonreceipt of the $90 item. No tax, delivery charge or other adjustment is included in this exercise.

A delivery record for the $150 item doesn’t establish delivery of the second item. The $240 invoice reconciles the order price, but pricing evidence alone can’t answer whether the disputed $90 item arrived.

Separate the order total, disputed amount and fulfilled components on the evidence map. If the actual claim concerns only part of an order, submitting an unlabeled whole-order record can obscure which portion the response addresses.

For this hypothetical packet, a precise description could say that the invoice lists two items, File 2 records delivery of the first, and no delivery evidence for the second has been located. Don’t turn that gap into a claim that delivery was proven.

Those facts are invented. They don’t decide whether a real merchant should challenge or accept a dispute, and they don’t predict the bank’s decision. Follow the actual case reason and requested evidence.

Card payment disputes: build a short factual sequence

Arrange the relevant records by event: purchase, promised fulfillment, shipment or service, actual completion, customer communication and any refund or replacement. Use the dates shown by the records, and distinguish a promised event from a completed one.

For an independent example, an email promising Friday delivery and a Monday dispatch record describe different facts. Neither should be summarized simply as “delivered Friday.” Retain the actual delivery evidence if it exists.

When records conflict, state the conflict and investigate it. A warehouse entry, carrier scan and customer message can concern different stages. Don’t choose the most favorable timestamp without checking what it represents.

Keep the explanation focused on the claim. A goods-not-received response needs evidence about fulfillment of the disputed goods. An authorization dispute needs a different analysis; delivery alone doesn’t answer every reason code.

Use restrained language about the customer. A disagreement or absent record isn’t evidence of fraud. State what the documents support instead of supplying a motive or filling an unknown event with an accusation.

Make each attachment readable without an outside search

Give the private working packet an index with file number, descriptive filename, relevant date, transaction reference and the point it supports. Use page references when a file contains several unrelated entries.

Open the exact file intended for upload and inspect it. A filename saying “delivery proof” doesn’t establish that the contents are legible, complete or associated with the disputed order.

Include necessary context so a screenshot’s meaning can be understood. A cropped dollar amount without its transaction or date can be ambiguous. At the same time, avoid exposing unrelated customer records or unnecessary sensitive information.

Follow the current provider’s accepted formats, size limits and evidence fields. These practical suggestions don’t override case instructions or create a universal list of documents that guarantees success.

For Stripe, the outside-link limitation described above means the response itself needs the relevant evidence in accepted form. A website that you can open isn’t evidence the bank will retrieve additional material from it.

Keep submission status separate from the cash forecast

For a standalone fictional cash illustration, assume a $240 dispute hold has already reduced $1,000 to $760 of available business funds. Assume $900 of unrelated obligations are due before any decision and there’s no other cash.

The payment-date gap is $140. An intended challenge or expected favorable outcome can’t be added as a confirmed $240 receipt. This example doesn’t quote provider fees or predict when any hold will end.

If a later record independently confirms the entire $240 has been released and is spendable, available funds become $1,000 under these no-other-movement assumptions. Paying $900 would then leave $100. That’s a different dated scenario.

Record actual debits, holds, releases and fees separately, using the provider’s definitions. Don’t subtract a hold twice from an available-balance figure that already reflects it. A dashboard case status and bank cash availability are different checks.

Review the final response against the live case

Before submitting, confirm case identity, current stage, disputed amount, reason and displayed deadline. An earlier inquiry response isn’t the later formal-dispute response if escalation requires another submission.

For Stripe, complete the evidence review before its final submission because the guide states that files can’t be edited or added afterward. For Square, watch for any further information request and use its current case instructions.

If a refund or replacement already occurred, include the actual relevant record and ask how it relates to the case. Don’t assume a separate refund automatically closes a dispute or that an intended refund has been completed.

After submission, retain the response, attachment versions and confirmation. Then distinguish submitted, under review and decided states. The completed preparation task is a documented response to the actual claim; the outcome still belongs to the cardholder’s bank.

For card payment disputes, keep the final attachment set distinct from the working folder. A response referencing File 3 should include the reviewed File 3, not an earlier draft or unrelated order record with the same name. Retain the submitted versions so any later explanation can be compared with what the bank actually received through the provider.

Related reading

For a related question, read Square Reserve Released? Check the Transfer Step and Business ACH Debits: Report Quickly, Then Check Controls.