# Event ticket chargeback — case-file worksheet

This is an organizer's working record, not a bank response form or legal conclusion. Follow the actual notice from your ticketing platform or payment processor and seek qualified advice when needed.

| Case field | Enter the verified value |
|---|---|
| Event and date | |
| Payment / order / ticket identifiers | |
| Processor or platform handling the dispute | |
| Dispute reference and reason stated in the notice | |
| Amount and currency in the notice | |
| **Exact response deadline and time zone** | |
| Organizer case owner and backup | |
| Platform contact / escalation channel | |
| Current event and ticket status | |
| Decision owner: accept or challenge | |

## Build a dated timeline

| When | What happened | Source record | Contradiction or gap |
|---|---|---|---|
| Purchase | Checkout, amount, ticket type and terms shown | Order/payment record | |
| Delivery | Confirmation and ticket delivery | Sent email or platform log | |
| Change | Cancellation, postponement, transfer, refund request or event update | Notice and buyer correspondence | |
| Event | Event delivery and ticket check-in state, if relevant | Event/scan record | |
| Dispute | Formal processor notice and reason | Notice/case ID | |

## Evidence checklist, tailored to the actual reason

| Potential evidence | Available? | Verified fact it supports | Submitted file/field |
|---|---|---|---|
| Purchase and payment details | | The charge and order match | |
| Event listing / ticket description at purchase | | What was offered | |
| Applicable terms and refund policy shown to the buyer | | What policy applied, if relevant | |
| Confirmation and ticket delivery record | | Delivery to the recorded address | |
| Transfer and check-in record | | Whether a ticket was transferred or scanned | |
| Buyer messages and organizer replies | | What was requested, promised and answered | |
| Refund/credit record | | Whether and when money was returned | |
| Event-change notices and actual event status | | Whether the service changed or occurred | |

Do not assert a ticket was used because a QR was issued. A scan proves a recorded scan, not necessarily who held the card. Do not conceal a cancellation, refund promise or missing record. Include only relevant personal data in the processor's authorized channel.

## Decision and closeout

Decision: [accept / challenge / refer to platform]  Owner: [ ]  Reason: [ ]  Supporting records complete: [ ]  Submitted by: [ ]  Date/time: [ ]

After submission: [processor status and date]  Issuer outcome: [ ]  Accounting/payout adjustment owner: [ ]  Customer follow-up owner: [ ]

Before sending, verify the actual platform's deadline, category, file formats and final-submission rules. A prepared case file does not guarantee that the issuing bank will decide in the organizer's favor.