dispute.*Sent when a chargeback or payment dispute changes state. There are four events, and they do not all carry the same fields: dispute.opened is raised from the order when the dispute arrives, while dispute.won, dispute.lost and dispute.closed are raised from the resolved dispute record.
dispute.closed fires alongside dispute.won or dispute.lost with an identical payload, so you can subscribe to it alone if you only care that a dispute has finished and not which way it went. Subscribing to both dispute.closed and the outcome events means two deliveries per resolution.
dispute.opened
data
order_idstring· uuidThe order ID associated with the dispute.
player_usernamestringPlayer in-game name.
player_uuidstring· uuidMinecraft UUID, if known.
total_amountnumberAmount under dispute.
currencystringISO 4217 currency code, taken from the store’s currency.
dispute_idstringPayment provider’s dispute ID.
reasonstringDispute reason as reported by the payment provider.
dispute.won, dispute.lost, dispute.closed
data
order_idstring· uuidThe order ID associated with the dispute.
dispute_idstringPayment provider’s dispute ID.
providerstringGateway that reported the dispute, e.g.
stripe or paypal.amountnumberAmount that was under dispute.
currencystringISO 4217 currency code recorded on the dispute.
reasonstringDispute reason as reported by the payment provider.
outcomestringwon or lost. Present on all three events, which is how you read the result from dispute.closed.These fire exactly once, on the first sync or provider webhook that resolves an open dispute.