Organizers currently handle ticket exchanges outside of TIXNGO, relying on the S-360 back-office and ticketshop, which results in a manual and fragmented process. To streamline on-site operations, enhance the user experience, and provide spectators with more flexibility and autonomy, we’re integrating this functionality into TIXNGO. This enhancement will not only simplify management but also unlock new revenue opportunities.
Overview
Ticket Exchange operates similarly to Ticket Resale, meaning that while the exchange process is fully managed by S-360, it can be initiated directly from TIXNGO.
A new “Exchange” button will be visible based on the following configurations:
- Organizer's Application settings
- Event settings
- Specific ticket rules
When the spectator clicks the Exchange button, he will be redirected to a dedicated S-360 ticketshop page where he can complete the exchange according to the S-360 sales configuration.
Note: All sales configurations—including catalog, tariffs, seat categories, contingents, and sales periods—will continue to be managed directly in S-360.
How to activate the Ticket Exchange feature ?
Enable the S-360 Ticket Exchange feature from the organizer settings
From the Application Settings, enable the feature Ticket exchange via S-360 ticketshop (key: ticket.s360.ticketshop.exchange)
Enable or Disable the S-360 Ticket Exchange on an per-Event basis
Enable the this feature from the "Edit event" screen in the "S-360 integration" tab and more precisely in the "Exchange" Section“Edit Event” screen under the “S-360 Integration” tab, specifically in the “Exchange” section.
In this section: , you can:
- to turn ON Enable or OFF disable completely the S-360 Exchange of tickets ticket exchange feature for this event only, by changing setting the value of "Allow exchange"to define “Allow Exchange”
- Define the URL of for the S-360 ticketshop exchange page.
| Expand | ||
|---|---|---|
| ||
|
New Exchange keys in the Ticket rules
Wallet behavior
TIXNGO wallet will do
...
| Name | Key | Default Value | |
|---|---|---|---|
| S360 Exchange for any spectator | FALSE |
| |
| S360 Exchange for initial spectator | FALSE | Dependent on S360 Exchange for any spectator ↔ If |
Wallet behavior
Exchange Button visibility
Event: | Transfer group: | Transfer group: | Exchange button visibility |
|---|---|---|---|
| FALSE | N/A | N/A | Hidden |
| TRUE | FALSE | N/A | Hidden |
| TRUE | TRUE | FALSE | Always visible |
| TRUE | TRUE | TRUE | if current Owner == Initial Spectator → Button visible if current Owner != Initial Spectator --> Button hidden |
Redirection to the ticketshop
By default, the S-360 Ticketshop Exchange URL defined at
...
the event level will be used to redirect
...
spectators to the ticketshop.
...
However, it
...
is possible to override
...
this URL on a per-ticket basis
...
by adjusting the S-360 injection template and
...
leveraging hidden ticket details metadata.
To
...
configure this, use the following configuration in your S-360 injection template:
- ticketDetails.hidden.index.key = EXCHANGE_TICKETSHOP_URL
- ticketDetails.hidden.index.value = https://ticketshop.secutix.com/account/tickets/exchange
What does this mean for you?
All sales configurations, such as catalog, sales period, and tariff settings, will continue to be managed in S-360.
...