RESALE TICKETSHOP S-360

Why should organizer use it?

• Let your fan resell their already injected mobile tickets on S-360 ticketshop in just a few simple steps directly from TIXNGO app.
• For each branded app, we offer the possibility to enable Resale on Ticketshop button on each available ticket which fan can access directly to S-360 webshop for resale
• With that, you can now safely allow injected tickets to be resold with no risk of having ill-intentioned people trying to "resale" their tickets on both systems.

How it works?

• Enable the feature: upon request and need the implementation on mobile side (require new build but wait, we soon will make it available on backoffice configuration)
  
  
• How to make the Resale on ticketshop available on a ticket in TIXNGO: 
  • Make sure the feature is included in the app build
  • Once ticket is injected into TIXNGO, at least one of these 2 parameters is TRUE: 
    • Set transferRules.allowReturnToOrganizer to TRUE : if you want all spectator who owns a ticket can resell it
    • Set transferRules.allowReturnToOrganizerForInitialSpectator to TRUE : if you want only initial spectator who ticket first injected with can resell ticket
      
      
      
      
  • Resale and resale cancel URLs are available (URLs must be updated correctly as your S-360 ticketshop): 

    • If injected via event.metadata:

      • Resale URL
        • event.metadata.index.key = RESALE_TICKETSHOP_URL
        • event.metadata.index.value = https://ticketshop.secutix.com/account/resale/resellTickets?ticketIds=
      • Cancel resale URL
        • event.metadata.index.key = CANCEL_RESALE_TICKETSHOP_URL
        • event.metadata.index.value = https://ticketshop.secutix.com/account/tickets?cancelResaleTicketId=
    • If injected via ticketDetails.hidden:
      • Resale URL
        • ticketDetails.hidden.index.key = RESALE_TICKETSHOP_URL
        • ticketDetails.hidden.index.value = https://ticketshop.secutix.com/account/resale/resellTickets?ticketI
      • Cancel resale URL
        • ticketDetails.hidden.index.key = CANCEL_RESALE_TICKETSHOP_URL
        • ticketDetails.hidden.index.value = https://ticketshop.secutix.com/account/tickets?cancelResaleTicketId=
          
          

• What makes these 2 entry points for URLs different:

  • From TIXNGO, system will prioritize ticketDetails.hidden over event.metadata in case both fields available
  • If you use only event.metada, these URLs are applied to all tickets of the event and you can easily update under “Event Edit”  
  • If you use ticketDetails.hidden only, it’s suitable if you have different URLs for different ticket categories/types/location/currency. But since it’s under ticket level, so you can’t do a bulk update massively for all tickets