> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paymend.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Payments disputed

> Alerts, RDRs, chargebacks and fraud reports raised against your payments.

One row per dispute event recorded during the period. A dispute event is a
signal received from a consumer or their issuing bank card scheme, via the acquirer, card scheme or
a fraud prevention provider, which has been matched to one of your payments.

```
report_payments_disputed-{merchant_name}-{period_start}_to_{period_end}.csv
```

Bounded on `event_created_at` — when Paymend recorded the event, not when the
underlying payment was posted.

## Event types

| `event_type`   | `event_program` | What it is                                                                                                       |
| -------------- | --------------- | ---------------------------------------------------------------------------------------------------------------- |
| `ALERT`        | `ETHOCA`        | Ethoca alert — the issuer has flagged the transaction, giving a window to refund before it becomes a chargeback. |
| `ALERT`        | `VERIFI_CDRN`   | Verifi CDRN alert, same purpose via a different network.                                                         |
| `RDR`          | `VERIFI_RDR`    | Rapid Dispute Resolution — the dispute was resolved automatically by Verifi. Funds are credited to the consumer. |
| `CHARGEBACK`   | *(empty)*       | A chargeback was raised. Funds are credited to the consumer.                                                     |
| `FRAUD_REPORT` | `TC40`          | A TC40 fraud report was filed by the issuer.                                                                     |

## Columns

| Column                          | Type      | Description                                                                    |
| ------------------------------- | --------- | ------------------------------------------------------------------------------ |
| `event_id`                      | string    | Unique identifier for this dispute event. Joins to the settlement report.      |
| `event_created_at`              | timestamp | When Paymend recorded the event. UTC.                                          |
| `payment_id`                    | string    | The disputed payment. Matches `event_id` in the payments created report.       |
| `payment_created_at`            | timestamp | When the disputed payment was originally processed.                            |
| `merchant_name`                 | string    | Your merchant identifier.                                                      |
| `store_id`                      | string    | Store the payment belongs to.                                                  |
| `merchant_reference`            | string    | Your own reference from the payment request.                                   |
| `authorization_code`            | string    | Authorization code of the disputed payment, populated when available.          |
| `acquirer_reference_number`     | string    | ARN of the disputed payment, populated when available.                         |
| `payment_amount`                | decimal   | Original payment amount, in major units.                                       |
| `payment_currency`              | string    | Currency of the original payment.                                              |
| `payment_descriptor`            | string    | Billing descriptor presented to the consumer.                                  |
| `consumer_first_name`           | string    | Consumer given name.                                                           |
| `consumer_last_name`            | string    | Consumer family name.                                                          |
| `consumer_email`                | string    | Consumer email address.                                                        |
| `card_brand`                    | enum      | Card brand of the disputed payment.                                            |
| `card_bin`                      | string    | First 6-8 digits of the card number.                                           |
| `card_last_4_digits`            | string    | Last four digits of the card number.                                           |
| `event_type`                    | enum      | `ALERT`, `RDR`, `CHARGEBACK`, `FRAUD_REPORT`.                                  |
| `event_status`                  | enum      | Outcome of the event — see below.                                              |
| `event_amount`                  | decimal   | Amount the scheme reported for the event. May differ from `payment_amount`.    |
| `event_currency`                | string    | Currency the scheme reported the event in. May differ from `payment_currency`. |
| `event_scheme`                  | enum      | Scheme that raised the event: `VISA`, `MASTERCARD`, `AMEX`, `DISCOVER`.        |
| `event_program`                 | enum      | Prevention network, per the table above.                                       |
| `event_reason_code`             | string    | Scheme reason code, where supplied.                                            |
| `event_reason_code_description` | string    | Human-readable form of the reason code, where supplied.                        |

### Event status

| Value             | Meaning                                                        |
| ----------------- | -------------------------------------------------------------- |
| `REFUNDED`        | The payment was refunded in response to the event.             |
| `VOIDED`          | The payment was voided before capture.                         |
| `NO_ACTION_TAKEN` | The event was recorded but no action was taken on the payment. |
| `RESOLVED`        | The dispute reached a terminal state.                          |

## One row per dispute event, not per payment

A single payment can attract several dispute events — an Ethoca alert, then a
TC40 report, then a chargeback. Each is a separate row with its own `event_id`
and its own fee.

## Reason code coverage

`event_reason_code` and `event_reason_code_description` are populated only where
the scheme supplies them, and coverage varies by program. Build downstream logic to
tolerate both fields being empty.

## Example

```csv report_payments_disputed-my_merchant-20260801_to_20260831.csv theme={null}
event_id,event_created_at,payment_id,payment_created_at,merchant_name,store_id,merchant_reference,authorization_code,acquirer_reference_number,payment_amount,payment_currency,payment_descriptor,consumer_first_name,consumer_last_name,consumer_email,card_brand,card_bin,card_last_4_digits,event_type,event_status,event_amount,event_currency,event_scheme,event_program,event_reason_code,event_reason_code_description
FRAD_9tRm2xQwLe,2026-08-03 02:11:07.412900 UTC,PAYM_7bQ2xKmR4v,2026-08-01 09:15:44 UTC,my_merchant,store_abc,ORD-88213,4419CD,74921500219000012345678,49.00,USD,8005550111acmewell,Priya,Raman,priya.raman@example.com,VISA,411111,4242,ALERT,REFUNDED,49.00,USD,VISA,ETHOCA,,FRAUD
FRAD_Xv2pQs5Bn8,2026-08-11 18:44:22.008145 UTC,PAYM_Nc9wTdLs3E,2026-08-01 11:49:03 UTC,my_merchant,store_123,ORD-88214,90210B,74921500219000012345679,129.50,USD,8005550111acmewell,Tomas,Lindqvist,t.lindqvist@example.com,MASTERCARD,555555,8081,CHARGEBACK,RESOLVED,129.50,USD,MASTERCARD,,4853,Cardholder dispute
FRAD_Wq3sHc7jTa,2026-08-14 05:09:31.663201 UTC,PAYM_Hj4zVpQa8M,2026-08-02 16:03:02 UTC,my_merchant,store_abc,,71204A,74921500219000012345680,49.00,USD,8005550111acmewell,Awa,Diallo,awa.diallo@example.com,VISA,400005,1907,RDR,RESOLVED,49.00,USD,VISA,VERIFI_RDR,10.4,Other fraud - card absent
FRAD_Lm5bNe0kUr,2026-08-22 23:57:14.220847 UTC,PAYM_Ry6kBnXu2W,2026-08-03 03:32:15 UTC,my_merchant,store_123,ORD-88219,55120E,,24.95,USD,8005550111acmewell,Hannah,Byrne,hbyrne@example.com,AMEX,371449,6003,FRAUD_REPORT,NO_ACTION_TAKEN,24.95,USD,AMEX,TC40,,Fraudulent transaction
```