Transaction Record
Capture the Square payment ID or receipt, sale date, amount, item or service, customer identity fields, invoice or estimate, and the dispute reason shown in Square.
Square seller response
Square disputes still need a clear seller story plus proof tied to the reason code: transaction details, receipt or invoice, delivery or service completion, customer messages, refund handling, and policy context. Pull the facts first so the response is short and verifiable.
Checklist
Capture the Square payment ID or receipt, sale date, amount, item or service, customer identity fields, invoice or estimate, and the dispute reason shown in Square.
For goods, collect tracking, signed proof of delivery when available, pickup confirmation, item photos, and address match. For services, collect signed contracts, appointment records, work completion notes, acceptance messages, or before/after proof.
Save emails, texts, invoices, refund requests, dispute warnings, support replies, prior successful transactions, and any proof that you tried to resolve the issue before the chargeback.
Attach terms of service, refund policy, shipping policy, estimate approvals, cancellation rules, and any posted product or service description that explains what the buyer agreed to.
Response prep
Do not dump every file you have. Start with the disputed amount, the reason, the response deadline, and the two or three facts that answer the cardholder claim.
Square guidance emphasizes evidence that is clear, verifiable, and tied to the disputed transaction. Label files in the order your written response mentions them.
TinyOps organizes your evidence and response draft. Square and the issuing bank control the actual dispute process and outcome.
Need the packet today?
Use the $49 packet for one normal dispute, or the $499 review for a larger case, a close deadline, or evidence spread across Square, email, delivery, and service records.
Official sources