When A Dispute Happens, Everything Else Should Too
An alert, a chargeback or a customer calling their bank is the moment you learn something important about that order. Automations make the rest of your stack react — cancel the subscription, hold the shipment, block the card, open the ticket, fire the Klaviyo flow — in seconds, with no code.
Triggers
Destinations
Platform fee
Start With What Merchants Actually Automate
Each recipe is a prefilled trigger, conditions and action. Create it, review it, save it.
Cancel the subscription when an alert hits
A dispute alert means the customer is done. Cancel their subscription in Loop, Recharge, Seal, Skio, Appstle, Checkout Champ, Sticky, or Apptics so the next rebill never becomes another chargeback.
Hold the shipment when an alert hits
Puts the matched Shopify order on a fraud hold the moment an alert lands, so nothing ships while you decide. Reversible from the order in Shopify; orders that already shipped quietly skip.
Cancel the Shopify order when an alert is refunded
Your refund rules refunded the alert — this also cancels the matched Shopify order if it has not shipped yet. Shipped orders and alerts that were not refunded are left alone.
Block the card behind confirmed fraud
An Ethoca confirmed-fraud alert means the card is stolen. Add it to your blocklist so every new order on that card gets cancelled before it ships.
Open a support ticket for every alert
Your agents see the dispute before the customer writes in. The ticket carries the order, amount, card, and what happened; if the customer already has an open ticket, it gets a note instead.
Get a Slack ping for every alert
A summary of every dispute alert lands in the channel you pick, with the amount, card, and customer.
Push every alert to Klaviyo
Every Ethoca, CDRN, and RDR alert lands as a metric on the customer profile, ready to trigger your Klaviyo flows.
Get an email for every alert
A summary of every dispute alert lands in your inbox, with the amount, card, and customer.
Send every alert to your stack
POST every Ethoca, CDRN, and RDR alert as JSON to any URL you control.
Get an email when a flow needs your attention
A flow action is waiting on your review or failed to run. You get the flow, customer, action, and why, so you can approve, deny, or retry it from your inbox.
Open a support ticket when a flow needs your attention
A flow action is parked for review or failed. A ticket on the customer lands in your helpdesk with the flow, the action, and why, so whoever is on support can pick it up.
Open a support ticket when a customer calls their bank
The customer is on the phone with their bank about your charge right now. Your agents get a ticket with the order and amount so they can reach out before it becomes a chargeback.
Triggers From Every Stage Of The Dispute
Most tools only know about the chargeback. Disputely knows the moment a customer opens your charge in their banking app or calls their bank — because Resolve is in the room. Those are triggers too.
Resolve
Customer calls their bank
A cardholder is on the phone with their bank asking about one of your charges.
Customer checks their banking app
A cardholder taps into one of your charges inside their banking app.
Any Resolve lookup
Any lookup on your transactions: calls, banking app, transaction data, or Mastercom.
Alerts
Ethoca alert received
Ethoca flags a transaction before it becomes a chargeback.
CDRN alert received
Verifi CDRN flags a dispute in progress.
RDR refund processed
A dispute was auto resolved through Rapid Dispute Resolution.
Any alert received
Any Ethoca, CDRN, or RDR alert for this account.
Chargebacks
Chargeback received
A cardholder filed a chargeback with their bank and the processor opened a dispute.
Chargeback won
The bank ruled in your favor and the disputed amount comes back to you.
Chargeback lost
The bank sided with the cardholder and the disputed amount is gone.
Any chargeback decision
The bank ruled on a chargeback, won or lost.
Flows
Customer completes a flow
A customer finishes one of your flows, whatever the outcome.
Customer takes a save offer
A customer accepted a coupon or save offer instead of a refund.
Customer gets a refund
A flow ended with a refund going back to the customer.
Actions In The Tools You Already Run
Connected from the dashboard once; available in every automation after that.
Klaviyo
Sends an event
- Send an event
Slack
Posts a message
- Post a message to a channel
Emails your team
- Email your team
Webhook
POSTs JSON
- Send the event as JSON
Shopify
Orders
- Hold the shipment
- Cancel the order
Blocklist
Blocks cards
- Block the card
Loop Subscriptions
Subscriptions
- Cancel the subscription
Seal Subscriptions
Subscriptions
- Cancel the subscription
Skio
Subscriptions
- Cancel the subscription
Recharge
Subscriptions
- Cancel the subscription
Stay AI
Subscriptions
- Cancel the subscription
Kaching Subscriptions
Subscriptions
- Cancel the subscription
Appstle Subscriptions
Subscriptions
- Cancel the subscription
Checkout Champ
Subscriptions
- Cancel the subscription
Sticky.io
Subscriptions
- Cancel the subscription
Apptics
Subscriptions
- Cancel the subscription
Gorgias
Support tickets
- Open a ticket
Commslayer
Support tickets
- Open a conversation
Kustomer
Support tickets
- Open a conversation
Zendesk
Support tickets
- Open a ticket
Three Steps, No Code
Pick the moment
A bank call, an Ethoca alert, a lost chargeback, a flow refund. Narrow it with conditions on amount, card brand, order age, reason code or customer history.
Choose the actions
One or many: cancel the subscription and open a ticket and post to Slack. Each action only activates once its destination is connected.
Watch it run
Every run is logged with what fired and why. Per-customer cooldowns stop the same moment firing twice unless you want it to.
Curated Questions
Still have Questions?
Contact SupportLet The Alert Do The Work
Connect your stack, pick a recipe, and the next alert cancels the subscription, holds the shipment and tells your team — before you have read the email.