Build a Square chargeback response pack before the deadline

When Square opens a new chargeback dispute, assemble a complete response pack automatically so nobody misses the evidence deadline. Trigger this workflow on the Square dispute webhook, which fires when a dispute is created or changes state. If I would rather not configure a webhook, run it on a schedule every few hours instead and use the Square List Disputes action to pick up disputes created since the last run.

Start with Square Get Dispute to read the disputed amount, the reason code, the current dispute state and the evidence due date, along with the ID of the payment being disputed.

Then locate the original transaction. Use Square List Payments and Square Search Orders to find the payment and the order behind it, and pull out the line items that were bought, the order totals, and any fulfillment detail such as shipment or pickup state and timestamps. If the order has a customer attached, call Square Get Customer to load the buyer's profile, then use Square Search Orders filtered to that customer to gather their prior purchase history, paying particular attention to earlier orders that completed without a dispute.

Draft a rebuttal narrative in clear business English that argues the charge was legitimate. Cite the specific order contents, the fulfillment record showing the goods or services were delivered, and any previous successful purchases by the same customer as evidence of a genuine ongoing relationship. Tailor the argument to the reason code on the dispute, since an item not received claim needs different evidence than a transaction not recognized claim.

Attach the finished narrative to the dispute using Square Create Dispute Evidence Text, so it is staged on the dispute record and ready for a person to review.

Never call Square Submit Dispute Evidence. Submitting sends the response to the cardholder's bank and cannot be reversed, so that final decision has to stay with a human reviewer. The job of this workflow is to have everything prepared and waiting, not to file it.

Finally, post a summary to the finance channel with the Slack Bot Send a Message action. Include the disputed amount, the reason code explained in plain language, the evidence due date and how many days remain, a short version of the rebuttal, and an explicit reminder that someone still needs to review the evidence in Square and submit it.

Flag any dispute where the amount at stake is smaller than the effort of contesting it. Call that out prominently at the top of the Slack message and recommend accepting the loss instead, so the team spends its time on the disputes that are actually worth fighting.