DICE Ticket Refund Guide: Canceled Events, Reschedules and Wait List
For DICE, the outcome depends on the transaction stage. A ticket holder should write down the event status, inspect the Waiting List deadline, and preserve the cooling-off feature. That simple record keeps a event ticket purchase request tied to the provider’s published rule. The sources in this article were checked on 2026-09-13.
Read each DICE rule against your own record
Event Status
DICE's U.S. ticketing terms provide for refunds when an event is canceled, when an event is rescheduled and the customer cannot attend, and in other situations where a refund is due under the event's setup. For the ticket holder, the event status is the first anchor. Compare that event status with the Waiting List shown by DICE. If the Waiting List has changed, save the current DICE screen. Do not treat the Waiting List deadline as proof of the ticket resale. Ask DICE which ticket resale controls your exact transaction. Keep the original ticket price beside the event status in your records. The cooling-off feature should match the final DICE outcome. If it does not, the ticket holder has a specific discrepancy to raise. This keeps the DICE discussion tied to dates and status.
Waiting List
DICE can make a Waiting List feature available for a particular event, but the feature is optional and is not promised for every event. For the ticket holder, the Waiting List is the first anchor. Compare that Waiting List with the Waiting List deadline shown by DICE. If the Waiting List deadline has changed, save the current DICE screen. Do not treat the ticket resale as proof of the original ticket price. Ask DICE which original ticket price controls your exact transaction. Keep the cooling-off feature beside the Waiting List in your records. The event status should match the final DICE outcome. If it does not, the ticket holder has a specific discrepancy to raise. This keeps the DICE discussion tied to dates and status.
Waiting List Deadline
When a ticket offered to an active DICE Waiting List is purchased by another user, DICE's terms provide for repayment of the original ticket price to the original customer. For the ticket holder, the Waiting List deadline is the first anchor. Compare that Waiting List deadline with the ticket resale shown by DICE. If the ticket resale has changed, save the current DICE screen. Do not treat the original ticket price as proof of the cooling-off feature. Ask DICE which cooling-off feature controls your exact transaction. Keep the event status beside the Waiting List deadline in your records. The Waiting List should match the final DICE outcome. If it does not, the ticket holder has a specific discrepancy to raise. This keeps the DICE discussion tied to dates and status.
Ticket Resale
Offering a ticket to the Waiting List does not itself guarantee repayment; another user must actually purchase the offered ticket under the feature. For the ticket holder, the ticket resale is the first anchor. Compare that ticket resale with the original ticket price shown by DICE. If the original ticket price has changed, save the current DICE screen. Do not treat the cooling-off feature as proof of the event status. Ask DICE which event status controls your exact transaction. Keep the Waiting List beside the ticket resale in your records. The Waiting List deadline should match the final DICE outcome. If it does not, the ticket holder has a specific discrepancy to raise. This keeps the DICE discussion tied to dates and status.
Original Ticket Price
DICE also supports an automated cooling-off or refund feature for some events when activated; because it is event-specific, a buyer must check whether it is actually enabled for that purchase. For the ticket holder, the original ticket price is the first anchor. Compare that original ticket price with the cooling-off feature shown by DICE. If the cooling-off feature has changed, save the current DICE screen. Do not treat the event status as proof of the Waiting List. Ask DICE which Waiting List controls your exact transaction. Keep the Waiting List deadline beside the original ticket price in your records. The ticket resale should match the final DICE outcome. If it does not, the ticket holder has a specific discrepancy to raise. This keeps the DICE discussion tied to dates and status.
Cooling-Off Feature
Event cancellation or rescheduling and voluntary Waiting List resale are separate mechanisms, so customers should use the one that matches the ticket's current event status. For the ticket holder, the cooling-off feature is the first anchor. Compare that cooling-off feature with the event status shown by DICE. If the event status has changed, save the current DICE screen. Do not treat the Waiting List as proof of the Waiting List deadline. Ask DICE which Waiting List deadline controls your exact transaction. Keep the ticket resale beside the cooling-off feature in your records. The original ticket price should match the final DICE outcome. If it does not, the ticket holder has a specific discrepancy to raise. This keeps the DICE discussion tied to dates and status.
DICE policy snapshot
| Account checkpoint | What the official rule says |
|---|---|
| Event Status | DICE's U.S. ticketing terms provide for refunds when an event is canceled, when an event is rescheduled and the customer cannot attend, and in other situations where a refund is due under the event's setup. |
| Waiting List | DICE can make a Waiting List feature available for a particular event, but the feature is optional and is not promised for every event. |
| Waiting List Deadline | When a ticket offered to an active DICE Waiting List is purchased by another user, DICE's terms provide for repayment of the original ticket price to the original customer. |
| Ticket Resale | Offering a ticket to the Waiting List does not itself guarantee repayment; another user must actually purchase the offered ticket under the feature. |
Separate the event status from the cooling-off feature
The event status tells the ticket holder when the first DICE action happened. The Waiting List shows whether another obligation may already exist. The cooling-off feature shows what DICE ultimately recorded. Those three checkpoints should be read separately. A voluntary ticket change is different from an organizer canceling or rescheduling an event. Optional ticket features, resale tools, transfers, and event status can each create a different path.
DICE scenarios that change the answer
DICE announces that the event is canceled
This is an event-status refund issue. Preserve the cancellation notice and watch the original payment method for the refund flow described by DICE. For this DICE situation, start with the Waiting List. The ticket holder should also verify the Waiting List deadline. Preserve the ticket resale before asking DICE for review. The original ticket price then shows whether the result is complete.
The date changes and you cannot attend
DICE's U.S. terms contemplate refunds when an event is rescheduled and the customer cannot attend; follow the event notice to request or receive the refund. For this DICE situation, start with the Waiting List deadline. The ticket holder should also verify the ticket resale. Preserve the original ticket price before asking DICE for review. The cooling-off feature then shows whether the result is complete.
The event is sold out and Wait List is enabled
You can offer the ticket before the Wait List deadline, but repayment depends on another DICE user purchasing that ticket. For this DICE situation, start with the ticket resale. The ticket holder should also verify the original ticket price. Preserve the cooling-off feature before asking DICE for review. The event status then shows whether the result is complete.
No Wait List button appears
Do not assume DICE must create one. The feature is optional and event-specific. For this DICE situation, start with the original ticket price. The ticket holder should also verify the cooling-off feature. Preserve the event status before asking DICE for review. The Waiting List then shows whether the result is complete.
A cooling-off option appears on the ticket
Use the feature exactly as displayed and within its event-specific period; it should not be generalized to tickets that do not show the option. For this DICE situation, start with the cooling-off feature. The ticket holder should also verify the event status. Preserve the Waiting List before asking DICE for review. The Waiting List deadline then shows whether the result is complete.
How a ticket holder should proceed
-
Open the DICE ticket and event details and determine whether the event is proceeding, canceled, rescheduled, or eligible for another refund feature. The ticket holder should complete this before the Waiting List deadline changes. Save the DICE ticket resale immediately after the action. Then compare the original ticket price with the new DICE status. If support is needed, mention the cooling-off feature by name. Ask DICE to state the effective date in writing. Keep the event status until the Waiting List is resolved. A clear DICE timeline prevents a second avoidable request.
-
If the event is canceled, follow the DICE notice and keep the original payment information while the refund is processed. The ticket holder should complete this before the ticket resale changes. Save the DICE original ticket price immediately after the action. Then compare the cooling-off feature with the new DICE status. If support is needed, mention the event status by name. Ask DICE to state the effective date in writing. Keep the Waiting List until the Waiting List deadline is resolved. A clear DICE timeline prevents a second avoidable request.
-
If the event is rescheduled and you cannot attend, use the refund route provided for the changed event. The ticket holder should complete this before the original ticket price changes. Save the DICE cooling-off feature immediately after the action. Then compare the event status with the new DICE status. If support is needed, mention the Waiting List by name. Ask DICE to state the effective date in writing. Keep the Waiting List deadline until the ticket resale is resolved. A clear DICE timeline prevents a second avoidable request.
-
If the event is still going ahead but you cannot attend, check whether the Waiting List is enabled and note its deadline. The ticket holder should complete this before the cooling-off feature changes. Save the DICE event status immediately after the action. Then compare the Waiting List with the new DICE status. If support is needed, mention the Waiting List deadline by name. Ask DICE to state the effective date in writing. Keep the ticket resale until the original ticket price is resolved. A clear DICE timeline prevents a second avoidable request.
💡 Similar Store Policy Fever Ticket Refund Guide: Final Sales and Flexible Cancellation Return & Refund Guide → -
Offer the ticket through DICE's authorized Waiting List only when that function is available and monitor whether another user actually buys it. The ticket holder should complete this before the event status changes. Save the DICE Waiting List immediately after the action. Then compare the Waiting List deadline with the new DICE status. If support is needed, mention the ticket resale by name. Ask DICE to state the effective date in writing. Keep the original ticket price until the cooling-off feature is resolved. A clear DICE timeline prevents a second avoidable request.
-
Check the ticket or event terms for any active cooling-off feature rather than assuming a universal 24-hour refund applies to every DICE event. The ticket holder should complete this before the Waiting List changes. Save the DICE Waiting List deadline immediately after the action. Then compare the ticket resale with the new DICE status. If support is needed, mention the original ticket price by name. Ask DICE to state the effective date in writing. Keep the cooling-off feature until the event status is resolved. A clear DICE timeline prevents a second avoidable request.
-
Keep all event-change, Waiting List, and repayment confirmations until the original payment amount is reconciled. The ticket holder should complete this before the Waiting List deadline changes. Save the DICE ticket resale immediately after the action. Then compare the original ticket price with the new DICE status. If support is needed, mention the cooling-off feature by name. Ask DICE to state the effective date in writing. Keep the event status until the Waiting List is resolved. A clear DICE timeline prevents a second avoidable request.
Build the DICE timeline before contacting support
Write the event status on line one. Add the Waiting List on line two. Put the Waiting List deadline on line three. A ticket holder can then see whether the request is early, late, direct-billed, third-party billed, processed, delivered, or still changeable under the specific DICE rule.
Next, capture the ticket resale. Do not rely on memory for the original ticket price. Save the cooling-off feature when DICE confirms the action. If an account screen changes after submission, the earlier screenshot helps the ticket holder explain what was visible at the time.
Finally, compare the expected DICE outcome with the actual outcome. The original ticket price may govern eligibility, while the cooling-off feature records completion. If they conflict, present both to DICE and ask which condition caused the difference.
After the DICE request
- Recheck the event status; the ticket holder should see the intended change.
- Inspect the Waiting List; it should not contradict the DICE confirmation.
- Keep the Waiting List deadline; it may prove the correct channel or account state.
- Review the ticket resale; any remaining obligation should be handled separately.
- Retain the original ticket price; it can explain eligibility if DICE later reviews the case.
- Do not close your notes until the cooling-off feature matches the final DICE result.
Evidence for a DICE review
- Ticket order and original ticket price: connect this item to the event status. A ticket holder should retain it until the Waiting List and the final DICE status agree.
- Event status and any reschedule notice: connect this item to the Waiting List. A ticket holder should retain it until the Waiting List deadline and the final DICE status agree.
- Wait list availability and deadline: connect this item to the Waiting List deadline. A ticket holder should retain it until the ticket resale and the final DICE status agree.
- Confirmation that the ticket was offered to the wait list: connect this item to the ticket resale. A ticket holder should retain it until the original ticket price and the final DICE status agree.
- Notification that another user purchased the ticket: connect this item to the original ticket price. A ticket holder should retain it until the cooling-off feature and the final DICE status agree.
- Refund or repayment confirmation: connect this item to the cooling-off feature. A ticket holder should retain it until the event status and the final DICE status agree.
DICE mistakes worth avoiding
- Avoid assuming the Waiting List is available for every DICE event. The ticket holder should verify the Waiting List deadline and retain the original ticket price before treating the DICE matter as closed.
- Avoid believing a ticket is refunded merely because it was offered to the Waiting List. The ticket holder should verify the ticket resale and retain the cooling-off feature before treating the DICE matter as closed.
- Avoid using resale logic when DICE has already canceled or rescheduled the event. The ticket holder should verify the original ticket price and retain the event status before treating the DICE matter as closed.
- Avoid assuming an automated cooling-off feature is universal. The ticket holder should verify the cooling-off feature and retain the Waiting List before treating the DICE matter as closed.
- Avoid discarding the original event notice before the refund or repayment posts. The ticket holder should verify the event status and retain the Waiting List deadline before treating the DICE matter as closed.
DICE FAQ
Does DICE refund canceled events?
DICE's U.S. terms provide for refunds due when an event is canceled, with the event's refund process handled through the platform and organizer arrangements. For this DICE question, compare the Waiting List with the ticket resale shown by the actual account or transaction.
What if the event is rescheduled?
The terms contemplate refunds when the customer cannot attend the rescheduled date; follow the event-specific notice. For this DICE question, compare the Waiting List deadline with the original ticket price shown by the actual account or transaction.
How does the DICE Waiting List work for a seller?
When enabled, an original customer can offer a ticket before the deadline, and repayment occurs if another user buys that ticket through the Waiting List. For this DICE question, compare the ticket resale with the cooling-off feature shown by the actual account or transaction.
Is the Wait List guaranteed to be available?
No. DICE decides whether to make the functionality available for a particular event. For this DICE question, compare the original ticket price with the event status shown by the actual account or transaction.
Does offering a ticket guarantee repayment?
No. Another user must actually purchase it through the Waiting List. For this DICE question, compare the cooling-off feature with the Waiting List shown by the actual account or transaction.
Is there always a cooling-off refund?
No. Automated cooling-off is an event-specific feature when activated; check the ticket or event details. For this DICE question, compare the event status with the Waiting List deadline shown by the actual account or transaction.
Related RefundGuides articles
These pages cover neighboring providers. Use them for comparison only; the DICE original ticket price remains provider-specific.
Official DICE sources
The following provider-controlled pages were checked on 2026-09-13. A ticket holder should reopen the applicable DICE page before relying on the original ticket price.
Bottom line: keep the event status, verify the Waiting List, use the correct Waiting List deadline, and preserve the cooling-off feature. That sequence gives a ticket holder a clean DICE record and keeps cancellation separate from any refund, credit, final bill, return, access period, or other financial result.