Versions Compared

Old Version 8

changes.mady.by.user jbo (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user jbo (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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
titleClick here to see the S-360 integration section

Image RemovedImage Added

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

KeyDefault ValueRule
S360 Exchange for any spectators360ExchangeForAnySpectatorFALSE
  • Use TRUE to enable Ticket Exchange for this ticket.
  • Use FALSE to disable Ticket Exchange for this ticket.
S360 Exchange for initial spectators360ExchangeForInitialSpectatorFALSE

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

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

...

Expand
titleClick here to see the new parameters in the Ticket Rules

Wallet behavior

User flow


My Tickets

Ticket detailsTicket actionsExchange confirmation popupWebview


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 screen (if configured accordingly)


Image Added

Image Added

Image Added Image Added

Image Added

Image Added

ChangesNone

None 

New button "Exchange your ticket"

New popup "Exchange this ticket" including :

  • a title and a description/message
  • a button to proceed with the exchange
  • a button to abandon the exchange
New title for the Webview Screen "Ticket shop"
Crowdin labelN/AN/A
  • Button to exchange → exchange_ticket_fab_title
  • Title → confirm_exchange_ticket_dialog_title
  • Message → confirm_exchange_ticket_dialog_msg
  • Button to proceed → confirm_exchange_ticket_dialog_button_01
  • Button to abandon → confirm_exchange_ticket_dialog_button_02
  • Webview Title → ticket_exchange_webview_title

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:

...

Redirection to the ticketshop

Event configuration at injection

By default, the S-360 Ticketshop Exchange URL 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:


Info

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