Request for Evidence Webhook

the request for evidence webhook notifies merchants—via a forter‑signed webhook—when we recommend uploading evidence for a specific claim, including which evidence types to send it is to be coupled with our # to provide the evidence forter is requesting notification types there are two notification types when subscribing to the webhook request for evidence informs merchants on all actionable claims that require evidence, with indication of which evidence type is required evidence reminder provides merchants with a reminder request for evidence when there are 5 days (120 hours) left before the claim due date and the recommendation status remains “pending evidence” key webhook fields each request for evidence will be associated with a corresponding claim, so you know which evidence is required for which representment forter will provide the requested evidence and the key identifiers below to enable seamless automation within your system field name description format example processorcasenumber the processor case id that the payment processor assigns to each claim string cb 43433343219 processorcasenumber the unique identifier associated with the processor charge string 0073000000000096401767 orderid the id of of the order that the evidence is linked to string o6996685178152213554 processorname the processor which the chargeback orginated from string adyen claimid forter's unique id for each claim can be used to find the claim in the portal string 123456789 webhook schema { "timestamp" "2025 01 01t12 00 00z", "uniquemessageid" "notif 123", "processorcasenumber" "ext123", "processorchargeid" "ch123", "orderid" "1 123", "claimid" 123, "processorname" "stripe", "issuedate" "2025 01 01", "duedate" "2025 01 03", "hoursleftuntildisputed" 48, "claimtype" "chargeback", "reasoncode" "10 1", "reasoncategory" "fraud", "cardtype" "visa", "amountclaimcurrency" 100 00, "claimcurrency" "usd", "requestedevidencetypes" \["invoice", "proof of delivery"] }