The Payments system in Eventixa manages all payment-related activities for event bookings. Whether you’re accepting online payments through supported payment gateways or registering attendees using free tickets and RSVP registrations, Eventixa automatically records the payment information associated with each booking.
Payment details are tightly integrated with the booking system, allowing organizers to track payment status, monitor transactions, and review payment history directly from the Booking Details page.
Available in: PayPal Payment and Offline Payment Available in Eventixa Core
Additional payment gateways available in: Stripe Payment Available in Eventixa Pro
How Payments Work
When an attendee registers for an event, Eventixa determines whether payment is required based on the selected ticket type.
The registration process follows one of these workflows:
Paid Tickets
Select Ticket
│
▼
Proceed to Checkout
│
▼
Choose Payment Method
│
▼
Payment Processed
│
▼
Booking Completed
Free Tickets / RSVP
Select Free Ticket or RSVP
│
▼
Complete Registration
│
▼
Booking Created
Since RSVP registrations do not require payment, no payment transaction is created.
Payment Methods
Eventixa supports multiple payment methods depending on the installed edition.
Eventixa Core
- PayPal Payments
- Offline Payments
Eventixa Pro
- Stripe Payments
Each payment gateway can be enabled or disabled independently from the Eventixa settings.
Payment Information
Every paid booking stores payment information alongside the booking record.
Depending on the payment method, the booking may include:
- Payment Method
- Payment Status
- Transaction ID
- Booking Total
- Payment Date
These details are available from the Booking Details page.
Payment Status
Each booking includes a Payment Status that reflects the current payment state.
Eventixa currently supports the following payment statuses:
| Payment Status | Description |
|---|---|
| Pending | Payment has not yet been completed. |
| Processing | Payment is currently being processed. |
| Paid | Payment was successfully received. |
| Failed | The payment attempt was unsuccessful. |
| Cancelled | The payment was cancelled. |
| Refunded | The booking has been marked as refunded. |
Payment status is displayed on both the Bookings list and the Booking Details page.
Payment Gateway Behavior
Payment status handling depends on the selected gateway.
Stripe
Stripe payments are processed automatically.
After a successful transaction:
- Payment Status becomes Paid
- Booking Status becomes Completed
Manual payment status changes are not available for Stripe payments.
PayPal
PayPal payments are also processed automatically.
Once payment is successfully completed:
- Payment Status becomes Paid
- Booking Status becomes Completed
Payment information is synchronized directly with the booking.
Offline Payments
Offline payments allow organizers to accept payments outside the website.
Examples include:
- Cash
- Bank Transfer
- Cheque
- Manual Payment
Bookings created using Offline Payments initially remain Pending until the administrator confirms that payment has been received.
Administrators can then manually update the payment status from the Booking Details page.
Free Tickets and RSVP
Free registrations do not create payment transactions.
Instead:
- The booking is created.
- The attendee is registered.
- No payment processing occurs.
This allows organizers to manage free and paid registrations within the same booking system.
Viewing Payment Details
Payment information can be viewed from the Booking Details page.
Typical information includes:
- Gateway
- Payment Status
- Transaction ID (for supported gateways)
- Booking Total
- Payment History
This provides organizers with a complete overview of the financial status of the booking.
Payment and Booking Synchronization
Payments and bookings work together automatically.
For example:
Successful Payment
│
▼
Payment Status → Paid
│
▼
Booking Status → Completed
│
▼
Attendee Registration Confirmed
Likewise:
Booking Cancelled
│
▼
Payment Status Updated (when applicable)
This synchronization ensures booking and payment information remain consistent.
Refunds
If a booking is cancelled, administrators can mark the booking as Refunded.
When a booking is refunded:
- Booking Status becomes Refunded
- Payment Status becomes Refunded
- Booking history records the refund
- Refund notification emails can be triggered
Important: Eventixa does not process refunds through Stripe, PayPal, or other payment gateways. Refunds must be completed using the respective payment provider. Updating a booking to Refunded only updates the booking record within Eventixa.
Payment Emails
Payment-related events can automatically trigger email notifications.
Examples include:
- Payment Confirmation
- Booking Confirmation
- Booking Refunded
Email templates can be customized from:
Eventixa → Settings → Emails
Payment Reports
Payment information is available throughout the booking system, allowing organizers to review:
- Booking Totals
- Payment Status
- Payment Method
- Transaction Details
These records help administrators monitor event revenue and payment activity.
Best Practices
- Configure your preferred payment gateways before publishing an event.
- Verify gateway settings by completing a test booking.
- Use Offline Payments only when manual payment verification is part of your workflow.
- Review payment statuses regularly to identify bookings requiring attention.
- Process refunds through the payment gateway before marking bookings as refunded in Eventixa.
- Monitor booking and payment statuses together to ensure accurate attendee registration.
Tips
- Payment information is automatically linked to every booking, providing a complete financial record for each registration.
- Stripe and PayPal payments are synchronized automatically, reducing the need for manual intervention.
- Offline Payments allow organizers to accept alternative payment methods and manually confirm payment when received.
- Free tickets and RSVP registrations bypass payment processing while still creating complete booking and attendee records, allowing all registrations to be managed from a single system.
