Refund and Dispute Review
How refund requests move through admin review, what each status means, and how disputes stay auditable.
Overview
Refund and dispute handling follows the actual order workflow in the platform. A customer can raise a refund request from the related order when the vendor has failed to fulfill or the booking has been marked as failed. The request is stored on the order, logged in the timeline, and sent for admin review. Admin can then approve, reject, or mark the refund as paid. That keeps the system auditable without inventing a separate off-platform process.
This flow is intentionally separate from cancellation requests. Cancellation is about stopping a booking before the event rules close; refund review is about what happens when fulfillment has already broken down and the order needs resolution.
Details
- Open the affected order and submit a refund request with a clear reason.
- Wait for admin review; the refund status will move through requested, approved, rejected, or paid.
- Check the order timeline for the latest audit entry and support updates.
- If the vendor cannot fulfill, use the booking workflow so the reason is logged before escalation.
Important Notes
- Refund requests are not the same as cancellation requests.
- The platform tracks the request and decision history so support can review the case later.
- Use the official order workflow rather than private side channels so the record stays consistent.
Was this article helpful?