The Transactions section in Eventixa provides payment-related information associated with event bookings. Every successful payment made through a supported payment gateway is linked to its corresponding booking, allowing administrators to review payment details, verify transactions, and troubleshoot payment issues.

Unlike bookings, which manage attendee registrations, transactions focus on the financial side of an event registration.

Available in: Eventixa Core
Online payment transactions: Stripe & PayPal

How Transactions Work

When a customer completes a paid booking, Eventixa records the payment information received from the selected payment method.

The typical workflow is:

Customer Registers
        │
        ▼
Payment Processed
        │
        ▼
Transaction Recorded
        │
        ▼
Booking Updated
        │
        ▼
Attendee Registered

For free tickets and RSVP registrations, no payment transaction is created because no payment is required.

Viewing Transaction Information

Transaction information is available from the Booking Details page.

Depending on the payment gateway, you can review:

• Payment Method
• Payment Status
• Transaction ID
• Booking Total
• Booking Number
• Customer Information

This allows administrators to verify that a payment was successfully associated with a booking.

Transaction Details

Each payment record may include the following information:

Field	Description
Payment Method	The gateway used to complete the payment (Stripe, PayPal, or Offline Payment).
Payment Status	The current payment state.
Transaction ID	The unique reference returned by the payment gateway, when available.
Booking Total	Total amount charged for the booking.
Booking Number	The booking associated with the transaction.

The exact information displayed depends on the payment method used.

Payment Status

Each transaction is associated with a payment status.

Possible statuses include:

• Pending
• Processing
• Paid
• Failed
• Cancelled
• Refunded

Payment status is synchronized with the booking and is displayed throughout the booking management interface.

Stripe Transactions

For bookings paid through Stripe, Eventixa records the payment information returned by Stripe after a successful payment.

Typical information includes:

• Payment Method
• Payment Status
• Transaction ID (when provided)
• Booking Total

Stripe automatically updates payment information after payment confirmation.

PayPal Transactions

For PayPal payments, Eventixa stores the transaction details associated with the completed payment.

Administrators can review:

• Payment Method
• Payment Status
• Transaction ID (when provided)
• Booking Total

Payment information is synchronized automatically after PayPal confirms the payment.

Offline Payments

Offline payments do not generate an online payment transaction.

Instead, Eventixa records:

• Payment Method
• Payment Status
• Booking Total

Since the payment occurs outside the website, there is no gateway-generated transaction ID.

Administrators manually confirm payment after funds have been received.

Relationship with Bookings

Every payment transaction is linked to a booking.

From the Booking Details page, administrators can review:

• Customer Information
• Event Information
• Purchased Tickets
• Payment Information
• Booking Notes
• Related Attendees

This provides a complete overview of the registration and its associated payment.

Failed Transactions

If an online payment fails:

• The payment status is updated accordingly.
• The booking is not completed.
• The attendee registration is not confirmed until payment succeeds.

Administrators can review failed payments from the associated booking.

Refunded Transactions

If a booking is refunded:

• Payment Status becomes Refunded.
• Booking Status is updated.
• Booking Notes record the refund.
• Refund notification emails can be sent if enabled.

Important: Updating a booking to Refunded in Eventixa does not process the refund through Stripe or PayPal. Refunds must first be completed through the respective payment provider.

Transaction History

Eventixa maintains payment activity as part of the booking record.

Payment-related events automatically recorded include:

• Payment received
• Payment status changes
• Refund status updates
• Booking completion
• Booking cancellation

This creates a reliable audit trail for each booking.

Email Notifications

Successful payment transactions can trigger automatic emails, including:

• Booking Confirmation
• Payment Confirmation
• Administrator New Booking Notification

Refunded transactions may also trigger refund notification emails, depending on your email configuration.

Best Practices

• Verify payment information before granting access to paid events.
• Review transaction details when investigating payment-related support requests.
• Process refunds through the payment gateway before marking bookings as refunded in Eventixa.
• Monitor failed or pending payments and contact customers if payment issues persist.
• Use the Booking Details page as the primary location for reviewing transaction information alongside booking and attendee data.

Tips

• Eventixa does not include a separate Transactions management screen. Payment information is stored and managed as part of each booking.
• Online payment gateways such as Stripe and PayPal automatically synchronize transaction details with the corresponding booking.
• Offline Payments do not generate gateway transaction IDs because payments are handled outside the website.
• Transaction information, booking details, attendee records, and booking history are all linked together, providing administrators with a complete view of each event registration.