--- title: Canceling and Refunding Bookings description: "Eventixa lets administrators cancel registrations and manage refunded booking states when an attendee can no longer participate. Cancellation and refunding are two separate parts of the workflow: - **Cancellation** changes the registration state and releases the applicable ticket capacity. -…" url: "https://eventixawp.com/docs/canceling-refunding-bookings/" updated: "2026-09-27" category: "Checkout & Bookings" --- # Canceling and Refunding Bookings Eventixa lets administrators cancel registrations and manage refunded booking states when an attendee can no longer participate. Cancellation and refunding are two separate parts of the workflow: - **Cancellation** changes the registration state and releases the applicable ticket capacity. - **Refunding** represents the financial outcome after money has actually been returned to the purchaser. > **Available in:** Eventixa Core > **Location:** Eventixa → Bookings → Open Booking > **Related features:** Booking Statuses, Payments, Capacity, Waitlist ## Cancellation vs Refund It is important to understand the difference between these actions. ### Cancel Booking Cancelling an eligible booking: - Changes the booking status - Makes the registration inactive - Releases applicable capacity - Affects attendee eligibility - Can trigger Waitlist handling ### Refund Booking Refunding means the financial payment has been returned to the purchaser. The actual monetary refund may need to be processed through the payment provider. Do not assume that cancelling a booking automatically returns the money. ## Open the Booking Go to: `Eventixa → Bookings` Locate the booking you want to cancel or refund. Open the booking details. Before taking action, review: - Booking reference - Event - Occurrence - Purchaser - Tickets - Attendees - Booking status - Payment status - Gateway - Total - Booking Notes ## Verify the Correct Booking Always confirm the booking before changing its state. This is especially important when a customer has: - Multiple bookings - Multiple event dates - Recurring-event registrations - Several attendees - Duplicate registrations Use the booking reference to avoid cancelling the wrong registration. ## Check Booking Status The Booking panel shows the current booking status. For example: - Completed - Pending - Cancelled - Failed - Expired - Refunded Cancellation actions depend on the current state. Not every status supports the same actions. ## Check Payment Status For paid bookings, also review the Payment panel. It can show: - Payment status - Gateway - Amount - Transaction ID For example: **Booking:** Completed **Payment:** Paid **Gateway:** Stripe This information helps determine whether a financial refund is required. ## Check the Transaction Before Refund For online payments, verify the actual transaction with the payment provider before processing a refund. Review: - Amount - Transaction ID - Customer - Gateway status Do not rely only on the booking screen when the financial transaction is uncertain. ## Cancel a Booking For an eligible booking, use the available booking-status action to cancel it. After cancellation, Eventixa updates the registration state. The booking should no longer be treated as an active registration. ## What Happens After Cancellation? Depending on the booking, cancellation can affect: - Ticket availability - Attendees - Check-in eligibility - Virtual-event access - Waitlist The booking record itself remains available for administrative history. ## Capacity Release One of the most important effects of cancellation is capacity release. For example: **Booking quantity:** 3 After cancellation, those three places can return to availability according to the applicable workflow. ## Example Ticket capacity: **100** Booked attendees before cancellation: **100** Cancelled booking quantity: **2** Without Waitlist, availability can become: **2** after the cancellation releases those places. ## Do Not Delete the Booking to Release Capacity Use the proper booking cancellation workflow instead of deleting a booking merely to free capacity. Keeping the booking record is useful for: - Refund history - Payment reconciliation - Support - Reports - Audit trail - Booking Notes ## Cancellation and Attendees Attendees belonging to the cancelled registration should no longer be treated as active attendees. Their records remain useful for historical purposes. Depending on the workflow, attendee status can also reflect the cancellation. ## Cancellation and Check-In A cancelled attendee should not be treated as a normal valid participant for check-in. If the attendee was already checked in, review the situation before changing the booking state. ## Cancellation and Virtual Events For Virtual and Hybrid events, cancelled bookings should not continue to receive the same registration-based access as valid active bookings. Meeting visibility can still depend on: - Booking state - Attendee state - Occurrence - Reveal timing ## Cancellation and Recurring Events For recurring events, cancellation applies to the booking associated with the selected occurrence. Always verify: - Event - Event date - Occurrence reference before cancelling. A booking for one occurrence should not be confused with another date of the same recurring event. ## Cancellation and Waitlist > **Requires Eventixa Pro** If a sold-out ticket has Waitlist enabled, cancellation can trigger the Waitlist reservation workflow. When capacity becomes available, Eventixa can immediately reserve the place for the next eligible waitlisted visitor. ## Waitlist Capacity May Not Become Public Suppose: **Available:** 0 **Cancelled quantity:** 1 If there is an eligible waitlisted visitor, that released place may be reserved immediately. The public availability can therefore remain: **0** even though a booking was cancelled. This is expected when Waitlist claims the released capacity. ## Waitlist Reservation When a place is offered to a waitlisted visitor, Eventixa can: - Reserve the capacity - Notify the visitor - Provide a protected checkout link - Apply the configured reservation expiration If the reservation expires, the next applicable workflow can continue. ## Payment Refunds If the cancelled booking was paid, the purchaser may also require a monetary refund. Eventixa booking cancellation and payment-provider refund are separate operations. ## Manual Refund Workflow The recommended workflow is: 1. Open the Eventixa booking. 2. Verify the booking and payment. 3. Cancel the booking. 4. Confirm that capacity is released or transferred to Waitlist. 5. Process the financial refund using the actual payment provider. 6. Confirm the refund succeeded. 7. Mark the Eventixa booking as **Refunded**. 8. Add an internal note if needed. ## Why Cancel First? Cancelling first allows Eventixa to immediately update the registration and capacity state. This is important for: - Sold-out events - Waitlist - Last-seat availability - Attendee eligibility The financial refund can then be processed separately. ## Refunded Status After the actual monetary refund is completed, the booking can be marked: **Refunded** This tells administrators that both the registration and financial refund workflow have been handled. ## Do Not Mark Refunded Too Early Do not mark a booking Refunded merely because: - The customer requested a refund - The booking was cancelled - You intend to refund later Use Refunded after the actual refund has been completed according to your payment workflow. ## PayPal Refunds For a PayPal booking, process the real monetary refund through the appropriate PayPal workflow unless your current integration explicitly performs it automatically. Verify the PayPal transaction before updating Eventixa. Then mark the booking Refunded after the real refund is complete. ## Stripe Refunds > **Payment method requires Eventixa Pro** For Stripe bookings, process the monetary refund through the supported Stripe workflow. Verify: - Transaction - Amount - Refund result Then update the Eventixa booking to Refunded. ## WooCommerce Refunds If the booking payment was handled through WooCommerce, the refund workflow can also involve the WooCommerce order. Review: - Eventixa booking - WooCommerce order - WooCommerce payment gateway Keep the records aligned. ## Offline / Local Refunds Offline payments must be refunded outside Eventixa. Examples: - Return a bank transfer - Return cash - Cancel an invoice - Return another manually collected payment After the real-world refund is completed, update the Eventixa booking accordingly. ## Free Bookings Free bookings have no financial transaction to refund. If a free registration is cancelled: - Cancel the booking - Release the capacity - Keep the booking history There is no monetary refund to process. ## RSVP Cancellation RSVP registrations do not involve payment. If an RSVP registration needs to be changed or cancelled, manage its registration state rather than using a financial refund workflow. ## Partial Refunds If your payment provider supports partial refunds, verify how you want the Eventixa booking to represent the final state. The Eventixa booking should remain consistent with: - Active attendee quantity - Capacity - Financial outcome Avoid using a full Refunded state if only part of the original registration remains active unless the workflow explicitly supports that scenario. ## Multiple Attendees in One Booking One booking can contain several attendees. For example: **Quantity:** 4 If the entire booking is cancelled, all applicable four places are released. If only one attendee can be removed through a supported attendee-editing workflow, make sure you do not cancel the entire booking unintentionally. ## Whole Booking vs Individual Attendee Before cancelling, decide whether the request concerns: - The entire booking - One individual attendee Use booking cancellation only when the full booking should become inactive. For attendee-specific changes, use the appropriate attendee-management workflow where supported. ## Refund Amount Before refunding a paid booking, verify the correct amount. Review: - Ticket price - Quantity - Discounts - Coupon - Total paid - Previous refunds The booking total may not always equal the original ticket list price. ## Coupons and Refunds If the purchaser used a coupon, refund the actual amount paid rather than the undiscounted ticket value. For example: **Ticket subtotal:** $100 **Coupon:** -$20 **Amount paid:** $80 The applicable refund should be based on the actual transaction. ## Transaction IDs The Payment panel can show a transaction reference. Use the transaction ID when locating the payment in: - Stripe - PayPal - WooCommerce gateway - Other connected payment systems This helps prevent refunding the wrong transaction. ## Booking Notes After cancellation or refund, add an internal note when useful. For example: **Customer requested cancellation by email. Stripe refund completed for $19.00.** This gives administrators context for future support or reconciliation. ## System Notes Eventixa can also add system-generated notes when booking status changes. For example: **Booking status changed: Completed → Cancelled** or another supported transition. Review system notes before taking further action. ## Internal Notes Internal notes are private to administrators. Use them to record information such as: - Refund request date - Refund amount - Provider used - Reason for cancellation - Organizer approval - Support conversation Do not include unnecessary sensitive financial information. ## Refund and Capacity Are Separate A financial refund does not itself determine ticket capacity. Capacity is controlled by the Eventixa booking/registration state. This is another reason cancellation should be handled explicitly. ## Example: Paid Booking Cancellation Booking: **Standard Pass × 2** Payment: **$38.00 — Stripe — Paid** Workflow: 1. Cancel the Eventixa booking. 2. Two places are released. 3. Refund $38 through Stripe. 4. Verify the refund. 5. Mark the booking Refunded. 6. Add an internal note. ## Example: Free Booking Cancellation Booking: **Student Admission × 1** Total: **$0.00** Workflow: 1. Cancel the booking. 2. One place is released. 3. No financial refund is required. ## Example: Offline Payment Refund Booking: **VIP Pass × 1** Payment method: **Local / Offline** Workflow: 1. Cancel the Eventixa booking. 2. Release capacity. 3. Return the payment manually. 4. Confirm the customer received the refund. 5. Mark the booking Refunded. ## Example: Waitlisted Event A sold-out event has: **Available:** 0 **Waitlist:** 4 visitors An attendee cancels one ticket. Eventixa can immediately reserve that released place for the next eligible waitlisted visitor. The public event can still show no open capacity. ## Example: Expired Booking An Expired booking generally does not need to be cancelled simply to release its checkout hold. The temporary reservation should already follow the expiration workflow. Review its Booking Notes and payment state before taking manual action. ## Failed Booking A Failed booking should not be treated as a successfully completed paid booking. Before attempting a refund, verify whether any money was actually captured. Do not refund a payment that never completed. ## Customer Says They Were Charged If the booking shows Failed, Pending, or Expired but the customer says they were charged: 1. Do not ask them to pay again immediately. 2. Check the Payment panel. 3. Copy the transaction ID. 4. Verify the transaction with the payment provider. 5. Determine whether payment actually succeeded. 6. Reconcile the Eventixa booking accordingly. ## Duplicate Bookings If the customer accidentally created two bookings: 1. Verify both booking references. 2. Verify both payment transactions. 3. Determine which booking should remain active. 4. Cancel the duplicate. 5. Process the appropriate refund. 6. Mark the duplicate Refunded after payment is returned. ## Cancellation Email Depending on the active Eventixa email workflow, booking-status changes can participate in customer communication. Before relying on automatic cancellation communication, test the workflow on your site. ## Re-Sending Tickets After Cancellation Do not resend tickets for a cancelled booking unless the registration has been restored through a valid workflow. A cancelled attendee should not continue to use an old ticket as if the registration were still active. ## Refund Fraud Prevention Before issuing any financial refund, verify: - Booking reference - Purchaser - Payment transaction - Amount - Gateway Do not process a refund based solely on an email request without confirming the booking. ## Administrator Permissions Only trusted administrators should be able to change booking states and manage refund-related workflows. Refunds affect: - Customer money - Capacity - Event attendance - Accounting records Treat these actions carefully. ## Common Problems ### Cancel Button Is Not Available The current booking status may not support cancellation. Review the booking status and available actions. ### Booking Is Cancelled but Still Shows Paid This can be correct until the financial refund is processed. Cancellation and payment refund are separate. ### Booking Was Marked Refunded but No Money Was Returned The Eventixa status does not itself guarantee a payment-provider refund. Verify the actual transaction and process the real refund. ### Customer Was Refunded but Booking Still Says Cancelled If the monetary refund has completed, update the Eventixa booking to the appropriate Refunded state. ### Capacity Did Not Increase After Cancellation Check whether: - Waitlist is enabled - Released capacity was reserved for another visitor - The booking cancellation completed successfully ### Sold-Out Event Still Shows Sold Out After Cancellation This may be correct if Waitlist immediately reserved the released capacity. ### Payment Provider Shows No Transaction Verify the booking's payment method and transaction ID. The booking may have been free, offline, failed, or never successfully paid. ### Expired Booking Still Shows Pending Payment Verify the payment provider. The checkout hold may have expired before the external payment state was resolved. ### Refund Amount Seems Wrong Review the actual transaction amount, including any coupon or discount. Refund the amount actually paid according to your policy. ## Recommended Cancellation Workflow 1. Open **Eventixa → Bookings**. 2. Locate the booking. 3. Verify the booking reference. 4. Check event and occurrence. 5. Review ticket quantity. 6. Review attendees. 7. Review booking status. 8. Review payment status. 9. Verify the gateway transaction if applicable. 10. Cancel the booking. 11. Verify the new booking status. 12. Confirm capacity behavior. 13. Check Waitlist if enabled. 14. Add an internal note if useful. ## Recommended Refund Workflow 1. Confirm the booking is the correct registration. 2. Verify the actual amount paid. 3. Verify the payment transaction. 4. Cancel the Eventixa booking. 5. Confirm capacity release. 6. Process the real refund through the payment provider. 7. Verify the refund completed. 8. Mark the booking Refunded. 9. Add an internal note. 10. Review Eventixa and provider records for consistency. ## Important Notes - Cancelling and refunding are separate actions. - Cancellation changes the registration state and releases applicable capacity. - A financial refund may need to be processed through PayPal, Stripe, WooCommerce, or an offline method. - Mark a booking Refunded only after the real refund has been handled. - Cancelled paid bookings can still show Paid until the financial transaction is refunded. - Free and RSVP bookings do not require monetary refunds. - Waitlist can immediately reserve capacity released by cancellation. - Always verify recurring-event occurrence before cancelling. - Verify the actual transaction before refunding. - Keep the booking record for history rather than deleting it. - Use Booking Notes to document important cancellation and refund activity. ## Related Documentation - [Managing Bookings in Eventixa](https://eventixawp.com/docs/managing-bookings/) - [Booking Details in Eventixa](https://eventixawp.com/docs/booking-details/) - [Booking Statuses in Eventixa](https://eventixawp.com/docs/booking-statuses/) - [Manual Bookings in Eventixa](https://eventixawp.com/docs/manual-bookings/) - [Payment Overview](https://eventixawp.com/docs/payment-overview/) - [PayPal Payment](https://eventixawp.com/docs/paypal-payment/) - [Stripe Payment](https://eventixawp.com/docs/stripe-payment/) - [Offline Payment](https://eventixawp.com/docs/offline-payment/) - [Event Waitlist Overview](https://eventixawp.com/docs/event-waitlist-overview/)