Skip to main content
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.
Bounded on event_created_at — when Paymend recorded the event, not when the underlying payment was posted.

Event types

Columns

Event status

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

report_payments_disputed-my_merchant-20260801_to_20260831.csv