Webhook Sengketa
Payload yang dikirim ke endpoint webhook Anda saat sengketa dibuat atau diperbarui. Tangani setiap event untuk merespons sengketa dan merekonsiliasi catatan Anda.
Peristiwa Webhook Sengketa
Sebuah sengketa memancarkan peristiwa di setiap tahap siklus hidupnya:dispute.lost dengan is_resolved_by_rdr: true. Hal ini diharapkan — pengembalian dana dikeluarkan secara otomatis untuk mencegah chargeback formal.dispute.*. Pengembalian dana untuk Ethoca alert memicu event refund.succeeded standar, dan pembatalan subscription yang tertaut memicu event subscription seperti biasa. Deflection tidak memicu event apa pun.Menangani Event Sengketa
Saatdispute.opened terpicu, jumlah yang disengketakan langsung ditahan. Gunakan event tersebut untuk memperbarui catatan Anda dan, jika Anda bermaksud menentangnya, kumpulkan bukti di dashboard.
Status dan Tahap Sengketa
Objek sengketa melaporkan progresnya melalui dua field:Terkait
Managing Disputes
Handle Payment Failures
Skema Payload Webhook
The amount involved in the dispute, represented as a string to accommodate precision.
Brand id this dispute belongs to
The unique identifier of the business involved in the dispute.
The timestamp of when the dispute was created, in UTC.
The currency of the disputed amount, represented as an ISO 4217 currency code.
The customer who filed the dispute
The unique identifier of the dispute.
The current stage of the dispute process.
pre_dispute, dispute, pre_arbitration The current status of the dispute.
dispute_opened, dispute_expired, dispute_accepted, dispute_cancelled, dispute_challenged, dispute_won, dispute_lost The unique identifier of the payment associated with the dispute.
Which processor handled the underlying payment. stripe / adyen for
BYOP routes (the merchant's own payment connector); dodo for
everything Dodo processed itself.
stripe, adyen, dodo Whether the dispute was resolved by Rapid Dispute Resolution
Reason for the dispute
Remarks