Ticket Disputes and Chargebacks
Track Stripe disputes, gather evidence, submit evidence to Stripe where available, and record local outcomes.
Article guidance
A dispute or chargeback is not the same as an ordinary refund. It means the buyer or their bank has challenged the payment through Stripe. SmartGig records dispute webhooks, links disputes to the matching ticket order where possible, and gives operators a focused page for response work.
What the Disputes page shows
- Stripe dispute ID and charge ID.
- Linked order reference and customer details where available.
- Dispute amount, currency, reason, status, opened date, and evidence due date.
- Whether evidence is needed soon.
- The latest operator response state.
- Any Stripe evidence submission snapshot recorded by SmartGig.
Response actions
- Gathering evidence: use while collecting order, ticket, policy, and communication details.
- Contacted buyer: record outreach or context that may help explain the case.
- Evidence submitted in Stripe: record that evidence was submitted outside the direct SmartGig submission flow.
- Accepted liability: record that the organisation accepts the dispute.
- Awaiting Stripe outcome: use after evidence is submitted and the team is waiting.
- Outcome recorded: record won, lost, or warning closed when the result is known.
Direct Stripe evidence submission
Where the event has the required Stripe connection and the dispute is still eligible, SmartGig can submit text evidence directly to Stripe. The form asks for a factual evidence summary, optional customer communication, optional policy notes, and an explicit confirmation before submission.