争议 Webhook
当创建或更新争议时发送到您的 Webhook 端点的负载。处理每个事件,以响应争议并对账您的记录。
争议 Webhook 事件
争议在其生命周期的每个阶段会触发一个事件:dispute.lost 与 is_resolved_by_rdr: true。这是预期的——退款是自动发出的,以防止正式拒付。dispute.* 事件。Ethoca alert 退款会触发标准的 refund.succeeded 事件,任何关联的订阅取消都会触发常规的订阅事件。deflection 不会触发任何事件。处理争议事件
当dispute.opened 触发时,争议金额会立即被冻结。使用该事件更新您的记录;如果您打算提出申诉,请在 dashboard 中收集证据。
争议状态和阶段
争议对象通过两个字段报告其进度:相关内容
Managing Disputes
Handle Payment Failures
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