Organizers currently manage ticket resale through organizer settings and transfer rules, which display the "Resell your ticket" button, even when no active resale platform is available on the S-360 side. To streamline on-site operations and align with the new "Ticket Exchange" feature, we are pleased to simplify the management of Resale configurations. This enhancement not only improves the user experience for organizers but also for spectators, ensuring a consistent and efficient process.

Overview

In substance, the Ticket Resale process remains fully managed by S-360 and can be initiated directly from TIXNGO.

A new “Resell” button will be visible based on the following configurations: Organizer's Application settings AND Event settings AND Specific ticket rules.
When the spectator clicks the “Resell” 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.

Notes: 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 Resale feature ?

Enable the S-360 Ticket Resale feature from the organizer settings

From the Application Settings, enable the feature Ticket resale via S-360 ticketshop (key: enable-resale-ticket-shop-s360)

Enable or Disable the S-360 Ticket Resale on an per-Event basis

Enable this feature from the “Edit Event” screen under the “S-360 Integration” tab, specifically in the “Resale” section.

In this section, you can:

Enable or disable completely the ticket resale feature for this event by setting the value of “Allow Resale”
Define the URLs for the S-360 ticketshop resale pages to put a ticket on resale or to remove it from resale.

Resale keys, new behaviour in the Ticket rules

We’ve adapted the current resale keys in the Ticket rules to provide clarity and consistency with Ticket Exchange and streamline button visibility.

Name

Key

Default Value

Rule

S360 Resale for any spectator

allowReturnToOrganizer

FALSE

Use TRUE to enable Ticket Resale for this ticket.
Use FALSE to disable Ticket Resale for this ticket.

S360 Resale for initial spectator

allowReturnToOrganizerForInitialSpectator

FALSE

For this parameter to take effect, “S-360 Resale for any spectator” must be set to TRUE.

Use TRUE to restrict Ticket Resale feature to the initial spectator ONLY
Use FALSE to allow any spectator to use the Ticket Resale feature

Wallet behavior

User flow

	My Tickets	Ticket details	Ticket actions	Resale confirmation popup	Webview
	Navigate to your event and find the ticket you want to exchange	Select the ticket you want to resell	Scroll to reveal possible ticket actions (main button or floating action button)	Tap the "Reseet" button.	Once confirmed, spectator is redirected to the ticketshop on the Exchange screen (if configured accordingly)

Changes	None	None	None. Same button "Resale on ticket shop".	New popup "Resell this ticket" including : a title and a description/message a button to proceed with the resale a button to abandon the resale	New title for the Webview Screen "Ticket shop"
Crowdin label	N/A	N/A	Button to initiate Resale → exchange_ticket_fab_title	Title → confirm_resale_ticket_dialog_title Message → confirm_resale_ticket_dialog_msg Button to proceed → confirm_resale_ticket_dialog_button_01 Button to abandon → confirm_resale_ticket_dialog_button_02	Webview Title → ticket_exchange_webview_title

Resell Button visibility

“Resell” button visibility is determined by specific rules that define which spectators can initiate a Ticket Reale, as outlined in the table below:

Allow Resale (Event)	S360 Resale for any spectator (Ticket Rules)	S360 Resale for initial spectator (Ticket Rule)	Expected behavior	"Post on resale" button visibility
FALSE	N/A	N/A	Ticket Resale is completely disabled for this event. Any ticket rules permitting resale will be ignored.	Not visible
TRUE	FALSE	N/A	Ticket Resale is enabled for this event, and any ticket rules permitting resale will be applied. However, if “Resale for any spectator” is set to FALSE, Ticket Resale will be disabled for this specific ticket.	Not visible
TRUE	TRUE	FALSE	Ticket Resale is enabled for this event, and any ticket rules permitting resale will be applied. If “Resale for any spectator” is set to TRUE, Ticket Resale is enabled for this ticket, regardless of whether the current owner is the initial one or not.	Always visible
TRUE	TRUE	TRUE	Ticket resale is enabled for this event, and any ticket rules permitting resale will be applied. If “Resale for initial spectator” is set to TRUE, Ticket Resale 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 Resale URLs specified at the event level will be used to redirect spectators to the ticketshop :

Posting a ticket on resale
- event.metadata.index.key = RESALE_TICKETSHOP_URL
- event.metadata.index.value = https://ticketshop.secutix.com/account/resale/resellTickets?ticketIds=
Removing a ticket from the resale
- event.metadata.index.key = CANCEL_RESALE_TICKETSHOP_URL
- event.metadata.index.value = https://ticketshop.secutix.com/account/resale/removeTickets?ids=

Ticket override at injection

However, you can override this URL on a per-ticket basis by modifying the S-360 injection template and utilizing hidden ticket details metadata.
To set this up, apply the following configuration in your S-360 injection template:

Posting a ticket on resale
- ticketDetails.hidden.index.key = RESALE_TICKETSHOP_URL
- ticketDetails.hidden.index.value = https://ticketshop.secutix.com/account/resale/resellTickets?ticketIds=
Removing a ticket from the resale
- ticketDetails.hidden.index.key = CANCEL_RESALE_TICKETSHOP_URL
- ticketDetails.hidden.index.value = https://ticketshop.secutix.com/account/resale/removeTickets?ids=

TIXNGO differentiates how URLs are managed based on their entry points: ticketDetails.hidden and event.metadata.

When both fields are available, ticketDetails.hidden takes precedence.
Using event.metadata applies URLs uniformly to all tickets of an event and allows for easy updates via the "Edit Event" screen under the "S-360 Integration" tab.
Conversely, ticketDetails.hidden is ideal for assigning distinct URLs to different ticket categories, types, locations, or currencies. However, since it operates at the ticket level, bulk updates across all tickets are not feasible.

Limitations

Spectator must be the ticket S-360 Cultural Contact to perform a Ticket Resale

Contact synchronization must be enabled in the feedback interface for ANY spectators to resell their tickets via the S-360 ticketshop.

How does TIXNGO prevent users from transferring tickets that have been resold ?

TIXNGO is unable to block ticket transfers until it receives confirmation from S-360 that the ticket has been invalidated following its resale.
This places the responsibility on the "Push Cancelled/Invalidated Tickets" function within the S-360 TIXNGO interface to ensure proper ticket management.

Handling Transfers of Resold Tickets

If a spectator manages to initiate or complete a transfer of a ticket that has been resold, 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).