Kick off Adyen chargeback defense the moment a dispute lands
When Adyen flags a retrieval request or chargeback, we alert your disputes channel in Slack and open a Linear issue with the evidence checklist your finance team needs to collect.
Adyen
Slack Bot
LinearFinanceOperationsNotifications & AlertsWhen Adyen sends a chargeback or dispute webhook, immediately kick off dispute defense so the finance team can respond before the deadline.
Trigger: an incoming webhook from Adyen carrying one of the dispute event codes NOTIFICATION_OF_CHARGEBACK (defendable dispute incoming), REQUEST_FOR_INFORMATION (retrieval request), or CHARGEBACK (funds pulled). The payload includes the pspReference, merchantReference, amount, reason code, and dispute response deadline — use those fields directly; there is no separate Adyen 'get dispute' lookup needed.
Step 1 — Draft and post a Slack alert. Using Slack Bot Send a Message, post to the #disputes channel with: the merchantReference (customer reference), the disputed amount and currency, the reason code, which Adyen event fired, and the number of days remaining until the response deadline (calculated from today vs. the deadline in the payload). Format the message so the reason and days-remaining stand out.
Step 2 — Create a Linear issue in the Payments team. Using Linear Create Issue, file an issue titled with the merchantReference and reason, with a description that repeats the merchantReference, pspReference, amount, reason code, event type, and response deadline, and includes a checklist of the evidence finance needs to collect: order confirmation, proof of delivery or fulfillment, and any customer communications tied to the transaction.
Step 3 — Prioritize by deadline. If the response deadline is within three business days from today, set the Linear issue priority to Urgent (priority = 1). Otherwise leave it at Normal (priority = 3). Compute business days by excluding weekends.
Reply in the workflow with a short confirmation summarizing what was posted and the Linear issue that was created, so the run history is easy to skim.
Additional information
What does this prompt do?
- Watches for retrieval requests, incoming chargeback notifications, and finalized chargebacks coming out of Adyen
- Posts a Slack alert to your disputes channel with the customer reference, disputed amount, reason, and days remaining to respond
- Opens a Linear issue in your Payments team with the dispute details plus an evidence checklist (order confirmation, delivery proof, customer communications)
- Marks the Linear issue Urgent when the response deadline is within three business days so tight timelines get worked first
What do I need to use this?
- An Adyen account with dispute notifications turned on
- A Slack workspace with a channel for dispute alerts (for example #disputes)
- A Linear workspace with a Payments team where the defense issues should live
How can I customize it?
- Point the Slack alert at a different channel or add people to @-mention
- Route the Linear issue to a different team, add labels, or assign a specific owner
- Adjust the deadline window that triggers Urgent priority (default is three business days)
Frequently asked questions
Which Adyen events kick this off?
Do I need a paid Slack plan?
What goes into the Linear issue?
How does it decide when a dispute is Urgent?
Can I send the alert somewhere other than #disputes?
Related templates
Stop scrambling on every Adyen chargeback.
Turn every dispute notification into a coordinated Slack alert and Linear task the moment it arrives, so evidence gets collected before the clock runs out.