The challenge
Public events need more than an attendance list
An event open to the wider public needs a page people can discover, a checkout that does not require membership and a reliable ticket for each attendee.
Organisers also need to understand ticket capacity, payments, check-in and refunds without piecing together several unrelated systems.
How MyNetworx approaches it
A public journey backed by organiser controls
Shared organiser profiles can publish in-person or online events with a public description, image, ticket types, capacities and event-specific discount codes. Visitors can search future events by postcode or current-location radius, while online events remain available without exposing the private meeting link.
Paid checkout runs through the organiser’s connected Stripe account. Successful bookings receive individual QR tickets, while organiser administrators can review bookings, check guests in and issue supported refunds.
How it fits together
A connected public-event journey
The same event record supports customer discovery and the organiser’s operational work.
In practice
What a public event can include
Configure the ticket offer and retain the operational information needed on the day.
Flexible ticket types
Offer multiple free or paid ticket types with individual capacities.
In person or online
Show an event as online and reveal its meeting link only with the confirmed booking.
Discount codes
Create event-specific percentage or fixed-value codes for the whole cart.
QR tickets and check-in
Issue individual tickets and scan or update their status from the organiser check-in view.
Booking refunds
Review purchasers and amounts, then issue a full, after-fees or custom Stripe refund.
Benefits
One record of the event and its bookings
Account-free booking
A customer can find and book a public event without being a MyNetworx member.
Capacity awareness
Ticket availability reflects paid bookings and active checkout reservations.
Traceable refunds
Stripe refunds remain tied to the connected account and produce a separate credit note for the customer.
Common questions
Questions about this feature
Does a customer need a MyNetworx account?
No. Public-event discovery and ticket checkout are available without a MyNetworx account.
Who receives the ticket money?
Paid tickets are charged on the organiser’s connected Stripe account. Stripe deducts its processing charge and MyNetworx collects the configured platform fee.
What happens when an organiser issues a refund?
An organiser administrator can choose the full remaining amount, the amount after the original Stripe and MyNetworx fees, or a custom amount. The refund is made against the connected-account charge and Stripe creates a linked credit note.
What happens to tickets after a refund?
A partial refund keeps the booking and its tickets active. A full refund marks the associated attendee and ticket records as refunded.