# 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 [Evidence API](https://docs.forter.com/evidence-api "Evidence API") to provide the evidence Forter is requesting.

## [Notification Types](https://docs.forter.com/request-for-evidence-webhook#notification-types) Notification Types

_There are two notification types when subscribing to the webhook:_

1. **Request for Evidence -** Informs merchants on all actionable claims that require evidence, with indication of which evidence type is required.
2. **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](https://docs.forter.com/request-for-evidence-webhook#key-webhook-fields) 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                |
| processorChargeId       | 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 originated 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](https://docs.forter.com/request-for-evidence-webhook#webhook-schema) Webhook Schema

JS

```json
{
  "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"]
}
```