Respond to Square DisputesBuilding a Response That Gives You the Best Chance of Winning
In a Nutshell
Responding to a Square dispute doesn’t just mean uploading whatever paperwork you have. It’s building a case that directly addresses the specific reason the cardholder gave for filing the claim. The issuing bank is evaluating a specific allegation, and your evidence needs to answer it. Getting this right means understanding the reason code, gathering targeted documentation, and submitting a professional rebuttal letter before your seven-day window closes.
How to Respond to Square Disputes: A Merchant’s Guide
So. I’ve talked about the Square dispute process, time limits, costs, and the resources that you’d use to try and manage disputes. Now, I want to talk a bit about what you can do to actually fight a Square chargeback when disputes occasionally happen.
Here’s all the information you’ll need about evidence, rebuttal letters, deadlines, and strategy for building a response that wins.
Square Disputes
Have questions about how chargebacks work on the Square platform? Start here. This guide covers everything Square merchants need to know about disputes, including how the process works, time limits, fees, tools, and how to fight back.
Deciding When to Accept Disputes & When to Challenge Them
Before spending time on a response, evaluate whether challenging the dispute is the right move. Transaction amount, strength of your evidence, and the specific dispute reason code all factor into whether a challenge is likely to be worth the effort.
Not every dispute warrants a challenge. Sometimes accepting a claim makes better financial sense, even if you think you might be in the right. You have to think about a few different factors, including:
Transaction Amount vs. Additional Effort
For a small transaction, the time required to build a strong response may exceed the value of what you’d recover. For a significant transaction, the math almost always favors challenging.
Evidence Quality
Do you have strong, specific evidence that directly contradicts the cardholder’s claim? If your documentation is thin or tangential, a weak submission can sometimes do more harm than if you’d simply accepted the dispute. Square may decline to submit your response due to incompleteness. It also signals that you didn’t engage seriously with the allegation.
The Reason Code
Some dispute types are more winnable with the right evidence. “Item not received” is often strong territory if you have carrier confirmation with delivery tracking. Fraud disputes — where the cardholder claims the transaction was entirely unauthorized — carry a higher evidentiary bar, though.
The Customer Relationship
Does the dispute look like a misunderstanding with an otherwise reliable customer? Reaching out and trying to have a direct conversation before submitting a formal challenge can sometimes resolve the matter without going through the bank’s process at all.
Square only accepts select file formats for documentation that can be submitted as part of your response. PDF, TIFF, JPEG, and HEIC only. Other formats will not be processed.
Evidence by Dispute Reason
The issuing bank is evaluating a specific allegation. Your evidence needs to contradict that allegation directly, not just demonstrate that the transaction happened. Match your documentation to the reason code, and prioritize the evidence that most specifically refutes the cardholder’s claim.
Fraud Disputes (Unauthorized Transaction)
The cardholder claims they didn’t make this purchase. So, you’d need to prove that the cardholder did, in fact, authorize it. Examples of strong evidence that might work here includes:
- Signed receipt or cardholder authorization form
- Billing and shipping address matching the cardholder’s address on file with the issuer
- Prior purchase history from the same card at your business
- IP address logs showing the purchase originated from the cardholder’s known location
- Device fingerprint or browser data matching cardholder’s known devices
- Customer service communications with the cardholder that reference the order
- For in-person transactions: EMV chip or tap authorization data confirming card-present authentication
Non-Receipt Disputes
Here, the cardholder claims they never received what they paid for. Your task is proving that they got exactly what they paid for, delivered on time. The strongest evidence here includes:
- Carrier tracking number with delivery confirmation and status
- Signature on delivery (especially for high-value orders)
- Delivery photograph if available from the carrier
- Proof of shipment date and carrier used
- Any prior customer communication acknowledging the order or confirming receipt
- For digital goods or services: access logs, login timestamps, download records, or service completion documentation
Not as Described / Not as Expected Disputes
The cardholder claims the item or service didn’t match what was advertised. So, you need to show that the product description was accurate,
Strongest evidence:
- Archived screenshots or copies of the product listing as it appeared at the time of sale
- Product specifications provided to the customer at checkout
- Your complete return and refund policy as it appeared at the time of purchase
- Documentation of any customer service interaction about this order—particularly if the customer expressed satisfaction or did not contact you before filing
- Any communications showing the customer’s understanding of what they were purchasing
Square may follow up if the bank requests additional documentation after your initial submission. Monitor your email and Dashboard for these requests.
Common Mistakes That Hurt Dispute Outcomes
The most avoidable dispute losses come from missing the seven-day deadline, submitting evidence that doesn’t address the specific reason code, and using an emotional or accusatory tone in the rebuttal letter.
So, you think you’ve got a good case. You submit the information requested… only to get a message a few weeks later saying that the bank ruled against you. What happened?
Well, there are a few common issues that might have come up during the preparation of your Square chargeback response:
Missing the Deadline
The most consequential — and preventable — mistake. Enable SMS notifications to ensure you get a tap any time there’s a new dispute pending. Then, check your dashboard after every notification to verify the deadline for your response, in addition to the regular dashboard check-ins you should be doing anyway.
Submitting Generic Evidence
Submitting evidence that doesn’t address the reason code attached to the transaction is not going to accomplish anything. For example, submitting a delivery confirmation email as evidence, regardless of the fact that the cardholder claimed the transaction was unauthorized, signals that you didn’t engage with the specific allegation.
Wrong File Formats
Only PDF, TIFF, JPEG, and HEIC are accepted. Other formats will not be processed as part of your dispute response. So, don’t complain if your dispute gets rejected because you submitted all your evidence as part of a DOCX file.
Ignoring Follow-Up Requests
The bank may sometimes reach out and request a specific document as part of their investigation that was not included in your initial submission. Square will contact you if this happens. Failing to respond is treated as non-compliance and typically results in a loss. This further underscores the importance of setting up notifications and regularly checking up on your dashboard for new messages.