Start with the request form
Square's dispute flow gives the reason, amount, deadline, and documentation request. Build the packet around that request instead of sending a generic file dump.
What this page is for
Use this before challenging a Square payment dispute where the buyer claims fraud, non-receipt, goods or services not as described, duplicate charge, incorrect amount, or a refund/credit issue. This page helps organize evidence only. It is not legal advice, not Square submission, not processor representation, and not a win guarantee.
Keep it factual and concise
Square guidance emphasizes relevant, clear evidence. Use dates, order IDs, receipt details, and attachment labels that map directly to the buyer's claim.
Separate fraud and non-fraud proof
Fraud disputes need authorization and customer-link records. Non-fraud disputes usually need delivery, service completion, policy, refund, or support records.
Square chargeback response packet template
Dispute snapshot
Record the Square dispute ID or dashboard reference, payment ID, customer name, amount, reason, response deadline, buyer claim, business location, and where the response must be submitted.
Merchant position
Write one short paragraph stating why the charge was valid, what was delivered or performed, whether any refund or cancellation occurred, and which evidence proves the point.
Transaction and authorization context
Attach the receipt, invoice, order record, signed authorization if available, customer profile, billing/shipping context, device or account history, and prior relationship records that are relevant to the reason.
Delivery, pickup, or service proof
For shipped goods, include carrier tracking, delivery scan, shipment address, fulfillment timeline, and packing record. For pickup or services, include appointment, completion, signed acceptance, message, photo, or work-order records.
Policy and customer communication
Attach the refund, cancellation, shipping, service, or return terms visible at purchase time, plus the support thread showing what the customer asked for and how the business responded.
Response statement and evidence index
Close with a concise response letter and numbered evidence index. Each attachment should support one factual claim so the issuing bank can scan the packet quickly.
Copyable Square response skeleton
Common Square response gaps
- Missing Square dispute deadline or reason-code context before building the response.
- Submitting a receipt without delivery, pickup, service-completion, or authorization proof.
- Using current policies instead of the terms that applied when the customer paid.
- Uploading blurry screenshots, oversized files, or attachments that are not clearly tied to the disputed transaction.
- Including sensitive card data or unrelated customer information that does not answer the claim.