Checkout Problems
Use this guide when Eventixa checkout does not open, does not progress, rejects a valid-looking ticket, asks for unexpected information, shows no payment method, expires unexpectedly, or creates an incomplete booking.
Eventixa checkout validates more than the selected ticket. It also checks the current ticket quantity, remaining capacity, checkout session, purchaser details, attendee requirements, payment configuration, and recurring occurrence context.
A typical Eventixa checkout flow is:
Event → Ticket Selection → Proceed to Checkout → Purchaser Details → Attendee Details → Payment if Required → Booking → Attendees
For limited-capacity tickets, checkout also creates a temporary reservation so the same places are not sold to multiple customers at the same time.
Before You Begin
Before changing checkout settings:
- Identify the exact event and ticket being tested.
- If the event is recurring, identify the exact occurrence.
- Confirm whether the visitor is logged in or checking out as a guest.
- Note the exact step where checkout stops.
- Record any error message exactly as displayed.
- Check whether the issue affects free tickets, paid tickets, or both.
- Test in a private/incognito browser window.
- Clear relevant page, server, CDN, and browser caches before retesting.
When possible, reproduce the issue using a controlled test event rather than making repeated changes to a live event.
Quick Diagnosis
| Symptom | First Check |
|---|---|
| Proceed to Checkout is disabled | Ticket quantity, ticket status, availability |
| Checkout says ticket is unavailable | Remaining capacity, pending bookings, active checkout reservation |
| Checkout timer is already partly expired | Existing checkout session |
| Checkout expired | 10-minute session timeout |
| Login is required unexpectedly | Guest Checkout setting |
| Purchaser email cannot be changed | Logged-in account email behavior |
| Attendee fields are missing | Ticket attendee collection setting |
| Required attendee fields block checkout | Missing required attendee information |
| No payment method appears | Paid ticket and gateway configuration |
| Free ticket asks for payment | Ticket price/configuration |
| Paid booking remains pending | Payment result and gateway status |
| Wrong recurring date is booked | Selected occurrence |
| Checkout total looks wrong | Ticket quantity, ticket price, coupon/adjustments |
| Capacity remains held after leaving checkout | Reservation has not expired yet |
Confirm the Ticket Can Be Selected
Checkout cannot begin until Eventixa receives a valid ticket selection.
On the single event page, verify:
- The ticket is visible.
- The ticket is within its sale period.
- Remaining capacity exists.
- The selected quantity is valid.
- Minimum and maximum quantity rules are satisfied.
- The ticket belongs to the intended event or occurrence.
If the ticket itself appears sold out or unavailable, use the Ticket Availability Problems guide first.
Proceed to Checkout Is Disabled
The Proceed to Checkout action requires a valid ticket quantity.
Check:
- At least one eligible ticket has been selected.
- Quantity is not zero.
- Quantity does not exceed the ticket maximum.
- Quantity does not exceed remaining availability.
- Quantity satisfies any configured minimum.
- The ticket is currently on sale.
If the button remains unavailable after a valid selection, clear frontend cache and retest in a private browser window.
Checkout Session
When checkout begins, Eventixa creates a temporary checkout session.
The session protects selected ticket capacity while the visitor completes registration.
This is especially important for limited-capacity events.
The checkout session duration is: 10 minutes
The checkout summary can display the remaining session time.
Checkout Timer Is Already Partially Expired
This is expected after a page refresh.
Refreshing checkout does not create a new 10-minute session.
The current session continues from its original expiration time.
This prevents a visitor from holding limited ticket capacity indefinitely by repeatedly refreshing the page.
Checkout Session Expired
If checkout is not completed before the session expires, the temporary reservation can be released.
The visitor may then need to:
- Return to the event page.
- Select the ticket again.
- Confirm that capacity still remains.
- Start a new checkout session.
If the ticket has sold out while the session was open, a new checkout may no longer be possible.
Capacity Is Held After Leaving Checkout
If a visitor abandons checkout, Eventixa can continue holding the temporary reservation until the current checkout session expires.
This does not mean capacity is permanently lost.
Wait until the original session expires and then recheck availability.
For detailed ticket-capacity diagnosis, see Ticket Availability Problems.
Checkout Says the Ticket Is No Longer Available
Eventixa rechecks capacity during the booking workflow.
A ticket can therefore be visible when the visitor first selects it but become unavailable before checkout completes.
This can happen when another visitor reserves or books the final places first.
Example:
- Two places remain.
- Visitor A selects both.
- Visitor B loads the event page before Visitor A reaches checkout.
- Visitor A starts checkout and temporarily reserves the two places.
- Visitor B tries to continue.
- Eventixa revalidates capacity and blocks the second request.
This protects the event from overselling.
Over-Capacity Validation
Checkout validates selected quantity against current remaining capacity.
Example:
Remaining capacity: 2
Requested quantity: 3
The booking should not complete.
Reduce the selected quantity or confirm that the ticket capacity is configured correctly.
Last Available Place
Eventixa should allow a valid request for the final remaining place.
Example:
Remaining capacity: 1
Requested quantity: 1
If the last place cannot be purchased, check:
- Minimum quantity
- Maximum quantity
- Pending bookings
- Active checkout sessions
- Selected recurring occurrence
Guest Checkout
Guest Checkout controls whether visitors can complete eligible Eventixa registrations without signing in to WordPress.
Review: Eventixa → Settings → Tickets → General
Check: Allow Guest Checkout
When Guest Checkout is disabled, visitors may be required to log in or register before continuing.
When enabled, eligible visitors can complete checkout without a WordPress account.
Checkout Requests Login
If a visitor is unexpectedly asked to log in:
- Go to Eventixa → Settings → Tickets → General.
- Confirm Allow Guest Checkout is enabled.
- Save the settings.
- Log out of WordPress.
- Retest the event in a private browser window.
If WooCommerce Checkout is being used, also review WooCommerce account/guest-checkout settings because WooCommerce can enforce its own checkout rules.
Logged-In Purchaser Email
When a visitor is logged in, Eventixa can use the authenticated WordPress account information.
The logged-in email may be locked to the account email where applicable.
If a logged-in customer cannot edit the purchaser email, this can be expected behavior.
To test true guest checkout, log out and use a private browser session.
Purchaser Information
The purchaser is the person creating the booking.
Checkout can collect purchaser information such as:
- Name
If checkout rejects the purchaser section, verify that all required fields contain valid values.
A malformed or missing email can prevent the workflow from progressing.
Purchaser and Attendee Are Different
Purchaser details and attendee details are not necessarily the same.
For example:
1 purchaser can register 3 attendees.
If individual attendee collection is enabled, Eventixa can request information for each selected ticket.
This means checkout can legitimately show one purchaser section and several attendee sections.
Attendee Fields Do Not Appear
Review the ticket’s attendee collection configuration.
Depending on the ticket setup, attendee information can be:
- Not collected
- Optional
- Required
If individual attendee collection is disabled, checkout should not be expected to show a separate attendee form for every selected ticket.
Required Attendee Fields Block Checkout
When attendee information is required, checkout cannot complete until the required values are valid.
Core attendee information can include:
- Name
Eventixa Pro can add advanced attendee fields.
If checkout does not continue:
- Review the affected ticket.
- Confirm which attendee fields are required.
- Complete every required field for each attendee.
- Check for invalid email values.
- Retest the booking.
Multiple Ticket Quantities
If a customer selects multiple tickets and attendee collection is required, Eventixa can request attendee information for each selected quantity.
Example:
Quantity: 3
Checkout can request:
- Attendee 1
- Attendee 2
- Attendee 3
If fewer attendee forms appear than expected, verify the ticket’s attendee collection mode.
Free Ticket Checkout
Free standard tickets do not require an online payment.
The normal flow is: Select Ticket → Enter Details → Confirm Booking
If a free ticket unexpectedly asks for payment, check the ticket’s configured price.
A price of zero should not require a paid gateway.
Paid Ticket Checkout
Paid tickets continue through a payment step.
The normal flow is:
Select Ticket → Enter Details → Choose Payment Method → Complete Payment → Booking Finalized
Available payment methods depend on the Eventixa payment configuration.
No Payment Method Appears
For a paid ticket, check:
- The ticket price is greater than zero.
- At least one supported payment gateway is active.
- The selected gateway is correctly configured.
- Required gateway credentials are present.
- Eventixa Pro is active if using native Stripe.
- WooCommerce is correctly configured if using WooCommerce Checkout.
Review: Eventixa → Settings → Payments
Only enabled and properly configured payment methods should be shown during eligible paid checkout.
PayPal Checkout Problems
If PayPal does not appear or cannot complete:
- Confirm PayPal is enabled.
- Confirm the PayPal configuration is complete.
- Verify you are testing a paid ticket.
- Verify the selected environment/credentials are correct.
- Review the resulting Eventixa booking and payment state.
For payment-specific diagnosis, use the Payment Problems guide.
Stripe Checkout Problems
Native Stripe support requires Eventixa Pro.
If Stripe is missing:
- Confirm Eventixa Pro is active.
- Confirm Stripe is enabled and configured.
- Verify the ticket is paid.
- Retest checkout.
For gateway-specific failures, use the Payment Problems guide.
Offline Payment
Offline Payment allows Eventixa to create a booking while payment is handled outside the website.
Examples include:
- Pay at venue
- Bank transfer
- Direct organizer payment
An offline booking should not automatically be interpreted as already paid.
Review the booking/payment state separately.
WooCommerce Checkout
When Eventixa uses WooCommerce Checkout, the applicable checkout can be routed through WooCommerce.
If checkout behaves differently from native Eventixa checkout, review both:
- Eventixa WooCommerce configuration
- WooCommerce checkout/account/payment settings
Do not troubleshoot WooCommerce payment availability only from Eventixa settings.
Paid Booking Remains Pending
A booking can exist without being successfully paid.
If a paid booking remains pending:
- Open Eventixa → Bookings.
- Review the booking status.
- Review the payment status.
- Confirm whether the gateway returned success.
- Check for a failed or interrupted payment.
- Retry through the supported payment flow where appropriate.
Use Payment Problems for gateway-specific diagnosis.
Checkout Total Looks Incorrect
The checkout summary can reflect:
- Ticket price
- Quantity
- Subtotal
- Discounts
- Total
If the total is unexpected, verify:
- Ticket price
- Selected quantity
- Applied coupon
- Any supported checkout adjustment
Example:
Ticket price: $19
Quantity: 3
Subtotal: $57
before applicable coupon or other supported adjustments.
Coupon Is Not Applied
If a coupon is expected to work during checkout:
- Confirm the coupon is valid for the event/ticket.
- Confirm the coupon is within its active dates.
- Confirm any usage conditions are satisfied.
- Recheck the checkout total after applying it.
If the coupon itself is rejected, use the relevant coupon documentation rather than changing checkout settings first.
Recurring Event Checkout
Recurring events require occurrence-aware checkout.
The booking must remain associated with the correct occurrence.
Before proceeding, verify the selected occurrence.
If the wrong recurring date is booked:
- Return to the event.
- Select the intended occurrence.
- Select the ticket again.
- Start checkout from that occurrence.
- Verify the booking after completion.
Do not treat the parent recurring event as interchangeable with each individual occurrence.
Virtual and Hybrid Event Checkout
Virtual and Hybrid events can use the normal Eventixa registration workflow.
Checkout itself may complete successfully while virtual access is controlled separately by the event’s virtual-access configuration.
If checkout succeeds but the attendee cannot access the meeting, use the Virtual Event Integration Problems guide rather than troubleshooting checkout.
Waitlist Instead of Checkout
Requires Eventixa Pro
When a ticket has no available capacity and Waitlist is enabled, normal checkout may no longer be available.
Visitors can be directed to the waitlist workflow instead.
If you expected normal checkout:
- Check current ticket capacity.
- Check pending bookings.
- Check active checkout reservations.
- Check existing waitlist reservations.
Use Ticket Availability Problems if the ticket appears sold out unexpectedly.
Checkout Page Does Not Load Correctly
If the checkout page is blank, incomplete, or visually broken:
- Clear WordPress/server/CDN/browser cache.
- Test in a private browser window.
- Temporarily disable aggressive JavaScript optimization for the checkout page.
- Check the browser console for JavaScript errors.
- Check failed AJAX/REST requests.
- Confirm required Eventixa assets are loading.
Dynamic checkout pages should not be cached in a way that prevents current session and ticket information from updating.
Caching and Optimization
Aggressive optimization can interfere with dynamic checkout behavior.
When troubleshooting, temporarily test without:
- Full-page cache on checkout pages
- JavaScript delay/defer rules that alter Eventixa scripts
- HTML optimization that changes checkout markup
- CDN cache for dynamic checkout content
After changing optimization settings, clear every relevant cache and retest.
Checkout Works When Logged In but Not as Guest
Check:
Eventixa → Settings → Tickets → General → Allow Guest Checkout
Also confirm no other plugin or commerce layer requires authentication.
If WooCommerce Checkout is active, WooCommerce can apply its own guest/account policy.
Checkout Works for Free Tickets but Not Paid Tickets
This usually points to payment configuration rather than the base checkout form.
Check:
- Gateway activation
- Gateway credentials
- Currency
- Test/live mode
- Payment result
Then continue with Payment Problems.
Checkout Works for One Event but Not Another
Compare the two events.
Check differences in:
- Ticket status
- Sale schedule
- Capacity
- Quantity rules
- Attendee collection
- Recurrence
- Event date/time
- Coupons
- Virtual/Hybrid configuration
If only one event fails, the issue is more likely event-specific than global.
Booking Is Created but Attendees Are Missing
Review the ticket attendee collection configuration.
Attendee records are created according to the selected quantity and attendee collection behavior.
Remember:
1 booking can contain multiple attendees.
If the booking exists but attendee records do not match the expected quantity, verify the ticket’s attendee requirements and the completed checkout data.
Checkout Succeeds but Confirmation Email Is Missing
Checkout and email delivery are separate stages.
If the booking exists correctly but the email is missing:
- Confirm the booking completed.
- Review Eventixa → Settings → Emails.
- Check the relevant template.
- Check recipient information.
- Check WordPress/SMTP delivery.
Use the Email Delivery Problems guide for further diagnosis.
Example: Checkout Says Ticket Is Unavailable
Suppose a visitor selects two tickets and reaches checkout, but Eventixa reports that the ticket is no longer available.
A useful diagnosis is:
- Verify the ticket still has capacity.
- Review Eventixa → Bookings for pending/active bookings.
- Consider whether another checkout session is holding capacity.
- Confirm the requested quantity.
- Confirm the selected recurring occurrence.
- Clear frontend cache.
- Reload the event and retry with current availability.
If another visitor reserved the final two places first, the rejection is expected over-capacity protection.
Example: Guest Cannot Complete Checkout
Suppose logged-in users can book successfully but guests are asked to sign in.
Check:
- Open Eventixa → Settings → Tickets → General.
- Enable Allow Guest Checkout.
- Save the settings.
- Log out.
- Open the event in a private browser.
- Select the ticket and continue to checkout.
- Complete the purchaser and attendee fields.
- Confirm the booking.
If WooCommerce Checkout is active, also review WooCommerce guest-checkout settings.
Recommended Diagnostic Workflow
When checkout fails:
- Confirm the ticket is currently available.
- Confirm the selected quantity is valid.
- Confirm the correct recurring occurrence.
- Start checkout.
- Check the session timer.
- Complete purchaser information.
- Complete required attendee fields.
- Confirm Guest Checkout behavior if logged out.
- For paid tickets, confirm a payment method appears.
- Complete or intentionally test the payment.
- Check Eventixa → Bookings.
- Check attendee records.
- Clear cache and retest if frontend behavior looks stale.
- Continue to the Payment, Email, or Ticket Availability troubleshooting guide if the failure occurs after checkout reaches those stages.
Important Notes
- Eventixa checkout sessions last 10 minutes.
- Refreshing checkout does not restart the session timer.
- Temporary checkout reservations help protect limited ticket capacity.
- Eventixa rechecks capacity during the booking workflow.
- The final valid remaining place should be purchasable when ticket rules allow it.
- Guest Checkout is controlled under Eventixa → Settings → Tickets → General.
- Logged-in purchaser email can remain tied to the authenticated account.
- Required attendee fields must be completed before checkout can finish.
- Free tickets do not require an online payment.
- Paid tickets require an eligible payment workflow.
- Booking status and payment status are separate.
- Recurring-event checkout must use the correct occurrence.
- Checkout, email delivery, and virtual-event access are separate stages.
- Dynamic checkout pages should not be aggressively cached.
Troubleshooting
Proceed to Checkout Is Disabled
Check:
- Valid ticket quantity
- Ticket availability
- Minimum/maximum quantity rules
- Sale schedule
- Ticket status
Checkout Timer Does Not Reset After Refresh
This is expected. The timer belongs to the existing 10-minute checkout session and continues from its original expiration time.
Checkout Session Expired
Return to the event, confirm current availability, and start a new checkout session.
Checkout Says Ticket Is No Longer Available
Availability changed after selection.
Check current capacity, pending bookings, active checkout reservations, and the selected occurrence.
Guest Is Asked to Log In
Enable Allow Guest Checkout under: Eventixa → Settings → Tickets → General
If WooCommerce Checkout is active, also review WooCommerce account settings.
Attendee Fields Are Missing
Review the ticket’s attendee collection configuration.
Required Attendee Information Is Rejected
Confirm all required attendee fields contain valid values, including valid email addresses where required.
No Payment Method Appears
Check:
- Ticket is paid
- Gateway is enabled
- Gateway is configured
- Eventixa Pro is active if using Stripe
- WooCommerce is configured if using WooCommerce Checkout
Free Ticket Requests Payment
Confirm the ticket price is zero.
Paid Booking Remains Pending
Review the payment result and payment status.
Use the Payment Problems guide for gateway-specific issues.
Wrong Recurring Date Is Booked
Verify the occurrence before entering checkout and repeat the booking from the intended occurrence.
Booking Is Created but Email Is Missing
Use the Email Delivery Problems guide.
Checkout Page Is Broken or Stale
Clear caches, disable aggressive optimization for checkout, inspect browser errors, and test in a private browser window.
Related Documentation
- Troubleshooting Overview
- Checkout Overview
- Guest Checkout
- Ticket Availability Problems
- Payment Problems
- Attendee Registration Fields
- Managing Bookings
Frequently Asked Questions
How long does Eventixa checkout stay active?
The Eventixa checkout session lasts 10 minutes.
Does refreshing checkout restart the timer?
No. Refreshing the page continues the existing session and does not grant a new 10-minute reservation.
Why does checkout say a ticket is unavailable when it was available a moment ago?
Another booking or active checkout session may have reserved the remaining capacity. Eventixa rechecks capacity during checkout to prevent overselling.
Why does checkout require login?
Guest Checkout may be disabled. Review Eventixa → Settings → Tickets → General → Allow Guest Checkout.
Why is there no payment method for a paid ticket?
At least one eligible payment gateway must be enabled and correctly configured. Review Eventixa → Settings → Payments.
