RESALE ON S-360 TICKETSHOP

RESALE ON S-360 TICKETSHOP

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 (TIXNGO V4) Ticket resale via S-360 ticketshop (key: ticket.s360.ticketshop.resa

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.

image-20260206-012810.png
S-360 Integration - Enable Resale

Resale keys, behavior in the Usage rule

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

Name

Description

Default Value

Name

Description

Default Value

S-360 Ticket Resale

Enable or disable the S-360 Ticket Resale feature for this ticket.

Options available:

  • DISABLED (resale disabled),

  • ENABLED (resale open to all owners),

  • RESTRICTED (resale open to initial owner only).

FALSE

image-20260206-014106.png
Usage rule details - S-360 Ticket Resale

Wallet behavior

Posting on Resale > User flow

 

My Tickets

Ticket details

Ticket actions

Confirmation popup

Webview

 

My Tickets

Ticket details

Ticket actions

Confirmation popup

Webview

Step

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 "Resell" button.

Once confirmed, spectator is redirected to the ticketshop on the Post on Resale screen (if configured accordingly)

Screen

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 → resale_ts_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 → resale_ticketshop_webview_title

Removing from  Resale > User flow

 

Burger Menu > Ticket returned for Resale

List of tickets open for resale

Ticket action

Confirmation popup

Webview

 

Burger Menu > Ticket returned for Resale

List of tickets open for resale

Ticket action

Confirmation popup

Webview

Step

Navigate to the Resale screen and find the ticket you want to removed from resale

Tap the name of the event

Select the ticket(s) you want to remove from resale

Tap the "Cancel resale" button.

Once confirmed, spectator is redirected to the ticketshop on the Post on Resale screen (if configured accordingly)

Screen

 

Changes

None

None 

None.
Same button "Cancel resale".

New popup "Cancel ticket resale" 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 → resale_cancel_button

  • Title → resale_cancel_confirm_title

  • Message → resale_cancel_confirm_msg

  • Button to proceed → resale_cancel_confirm_button_01

  • Button to abandon → resale_cancel_confirm_button_02

  • Webview Title → resale_ticketshop_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)

S-360 Ticket Resale

(Usage rules)

Expected behavior

"Post on resale" button visibility

Allow Resale
(Event)

S-360 Ticket Resale

(Usage rules)

Expected behavior

"Post on resale" button visibility

FALSE

N/A

Ticket Resale is completely disabled for this event. Any usage rules permitting resale will be ignored.

Not visible

TRUE

DISABLED

Ticket resale is enabled for this event, and applicable resale usage rules will apply.

If “S-360 Ticket Resale” is set to DISABLED, ticket resale will be

Not visible

TRUE

ENABLED

Ticket resale is enabled for this event, and applicable resale rules will apply.

If “S-360 Ticket Resale ” is ENABLED, ticket resale applies to all tickets under these usage rules, regardless of whether the current owner is the original purchaser.

Always visible

TRUE

RESTRICTED

Ticket resale is enabled for this event, and applicable usage rules will apply.

If “S-360 Ticket Resale” is set to RESTRICTED, resale is enabled for all tickets under this usage rule but limited to the initial owner. It disables resale for 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 :

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:

 

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 fol
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).