---
title: Request for Evidence Webhook
slug: request-for-evidence-webhook
docTags: 
createdAt: 2026-06-01T13:20:13.766Z
---

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) to provide the evidence Forter is requesting.

***

## 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

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 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

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

***

## Responding with Data Points

`requestedEvidenceTypes` names the evidence Forter needs, not the format to send it in. Many requested evidence
types can be satisfied either by uploading a file or by sending the equivalent structured data points to
`/v3/disputes/evidence/datapoints`. Either format satisfies the request, whether it is sent through the
[Evidence API](https://docs.forter.com/evidence-api) or added in the Forter Portal. Once a requested evidence
type is provided in either format, Forter stops requesting it, and it is left out of later Evidence Reminder
notifications for that claim.

The following requested evidence types can be satisfied with data points:

| **Requested Evidence Type**    | **Data Point Key**        | **Shape**                                                                     |
| ------------------------------ | ------------------------- | ----------------------------------------------------------------------------- |
| `PROOF_OF_REFUND`              | `proofsOfRefund`          | `[{ refundTransactionId, refundAmount?, refundCurrency?, refundDate?, ... }]` |
| `PROOF_OF_DELIVERY`            | `proofsOfDelivery`        | `[{ trackingNumber, carrier?, date?, deliveryStatus?, ... }]`                 |
| `CUSTOMER_CORRESPONDENCE`      | `customerCorrespondences` | `[{ contactId, contactReason?, contactDescription?, contactDateTime? }]`      |
| `PROOF_OF_ORDER_REPLACEMENT`   | `proofsOfReplacement`     | `[{ replacementId, replacementDate?, replacementItems?, ... }]`               |
| `CREDIT_BALANCE`               | `proofsOfCreditBalance`   | `[{ appliedDate, amount?, currency? }]`                                       |
| `PROOF_OF_POSSESSION_OR_USAGE` | `proofsOfUsage`           | `[{ usageTimestamp }]`                                                        |
| `BUYER_REVIEW_SURVEY`          | `buyerReviewSurveys`      | `[{ overallRating, reviewItems?, reviewText? }]`                              |
| `PURCHASE_HELD_IN_CUSTOMS`     | `itemsHeldInCustoms`      | `string[]`                                                                    |
| `ITEM_DESCRIPTION`             | `itemDescriptions`        | `string[]`                                                                    |
| `RECURRING_BILLING_AGREEMENT`  | `subscriptionDetails`     | `[{ isRecurringCharge, billingAgreementPolicy? }]`                            |

All of these types also remain valid as file uploads. Requested evidence types that are not listed above can
only be satisfied by uploading a file. For full field definitions and examples, see the
[Evidence Glossary](https://docs.forter.com/evidence-glossary).