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.
...
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 completely the ticket exchange feature for this event by setting the value of “Allow Exchange”
- Define the URL for the S-360 ticketshop exchange page.
| Expand | ||
|---|---|---|
| ||
|
New Exchange keys in the Ticket rules
We’ve introduced two new Ticket Rules parameters to provide greater flexibility and control over ticket exchange configurations.
Name | Key | Default Value | Rule |
|---|---|---|---|
| S360 Exchange for any spectator | s360ExchangeForAnySpectator | FALSE |
|
|
| |||
| S360 Exchange for initial spectator | s360ExchangeForInitialSpectator | FALSE |
|
|
|
|
| Expand | ||
|---|---|---|
| ||
|
Wallet behavior
User flow
My Tickets | Ticket details | Ticket actions | Exchange confirmation popup | Webview | |
|---|---|---|---|---|---|
Navigate to your event and find the ticket you want to exchange | Select the ticket you want to exchange | Scroll to reveal possible ticket actions (main button or floating action button) | Tap the "Exchange your ticket" button. | Once confirmed, spectator is redirected to the ticketshop on the Exchange |
...
Event:
Enable S-360 Exchange
| screen (if configured accordingly) | |||||
|
|
|
|
| |
| Changes | None | None | New button "Exchange your ticket" | New popup "Exchange this ticket" including :
| New title for the Webview Screen "Ticket shop" |
| Crowdin label | N/A | N/A |
|
|
|
Exchange Button visibility
“Exchange” button visibility is determined by specific rules that define which spectators can initiate a Ticket Exchange, as outlined in the table below:
Allow Exchange (Event) | S360 Exchange for any |
|---|
| S360 Exchange |
|---|
for initial | Expected behavior | Exchange button visibility |
|---|---|---|
| FALSE | N/A | N/A |
Ticket Exchange is completely disabled for this event. Any ticket rules permitting exchanges will be ignored. | Not visible | |
| TRUE | FALSE | N/A |
Ticket Exchange is enabled for this event, and any ticket rules permitting exchanges will be applied. However, if “Exchange for any spectator” is set to FALSE, Ticket Exchange will be disabled for this specific ticket. | Not visible | |
| TRUE | TRUE | FALSE |
Ticket Exchange is enabled for this event, and any ticket rules permitting exchanges will be applied. If “Exchange for any spectator” is set to TRUE, Ticket Exchange is enabled for this ticket, regardless of whether the current owner is the initial one or not. | Always visible | |
| TRUE | TRUE | TRUE |
if current Owner != Initial Spectator --> Button hidden
Ticket Exchange is enabled for this event, and any ticket rules permitting exchanges will be applied. If “Exchange for initial spectator” is set to TRUE, Ticket Exchange is enabled for this ticket but restricted to the initial owner. It will be disabled for any subsequent owners. | Button visible only if the Current Owner is the Initial Spectator |
Redirection to the ticketshop
Event configuration at injection
By default, the S-360 Ticketshop Exchange URL defined specified at the event level will be used to redirect spectators to the ticketshop.However, it is possible to
- event.metadata.index.key = EXCHANGE_TICKETSHOP_URL
- event.metadata.index.value = https://ticketshop.secutix.com/account/tickets/exchang
Ticket override at injection
However, you can override this URL on a per-ticket basis by adjusting modifying the S-360 injection template and leveraging utilizing hidden ticket details metadata.
To configure set this up, use apply 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
| Info |
|---|
TIXNGO differentiates how URLs are managed based on their entry points:
|
Limitations
Spectator must be the ticket S-360 Cultural Contact to perform a Ticket Exchange
Contact synchronization must be enabled in the feedback interface for spectators to exchange their tickets via the S-360 ticketshop.
How does TIXNGO prevent users from transferring tickets that have been exchanged?
TIXNGO cannot block the transfer until it receives confirmation from S-360 that the ticket has been invalidated after its exchange.
This process is similar to how resales are handled in S-360, with the distinction that ticket invalidation in the case of exchange only occurs after the exchange operation is completed in S-360.
This includes successful payment, marking the original ticket as invalidated (with the reason "REFUNDED"), and issuing the new ticket.
Handling Transfers of Exchanged Tickets
If a spectator manages to initiate or complete a transfer of a ticket that has been exchanged, the delayed invalidation should override the transfer:
If the transfer is initiated (but no action has been taken by the recipient):
- The ticket will be invalidated (due to the Push Cancelled/Invalidated function of the S-360 TIXNGO interface), and
- The transfer will be automatically cancelled by TIXNGO.
If the transfer is completed (accepted, rejected, or abandoned):
- The ticket will be invalidated (due to the Push Cancelled/Invalidated function of the S-360 TIXNGO interface).