Versions Compared

Old Version 8

changes.mady.by.user lnn [X] (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Oanh HO

Saved on

Key

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


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

resal

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

to activate the Ticket Resale feature ?

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

From Application Features setting in Backoffice, set "Ticket resale via S-360 ticketshop" to "TRUE" (key:enable-resale-ticket-shop-s360)

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

Enable this 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:

    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 URL for the S-360 ticketshop resale page.


    Expand
    titleClick here to see the S-360 integration section

    Image Added

    Resale keys in the Ticket rules

    Name

    Key

    Default Value

    Rule

    S-360 Resale for any spectator

    allowReturnToOrganizer

    FALSE

    • Use TRUE to enable Ticket Resale for this ticket.

    • Use FALSE to disable Ticket Resale for this ticket.

    S-360 Resale for initial spectator

    allowReturnToOrganizerForInitialSpectator

    FALSE

    • Use TRUE to restrict Ticket Resale feature to the initial spectator ONLY

    • Use FALSE to allow any spectator to use the Ticket Resale feature


    Expand
    titleClick here to see the parameters in the Ticket Rules

    Image Added

    Wallet behavior

    User flow

    Access Resale ActionsWebviewTickets Returned For ResalePending Resale Ticket you resellingCancel Ticket resaleCompleted ResaleTicket you resold 
    From the ticket details screen, scroll to reveal available ticket actions (either via a main button or floating action button).Tap the “Resell Your Ticket” button

    Upon confirming resale, the spectator is redirected to the Ticketshop's Resale screen (if configured).

    After login to S-360 ticketshop resale, spectator will be redirected to resale page of the selected ticket 

    		After listing a ticket for resale, the spectator can view it under the “Tickets Returned for Resale” sectionOnce the ticket is posted on the resale platform, it appears in the Pending Resale section, indicating it’s awaiting purchaseSpectators can review details of tickets they are currently resellingSpectators can cancel the resale, which will return the ticket to their walletWhen a ticket is purchased on the resale platform, it moves to the Completed Resale section, indicating the resale is finalizedSpectators can review details of tickets they are resold

    Image Added Image AddedImage Added

    Image Added

    Image Added
    		Image Added
    Image Added
    		Image AddedImage AddedImage Added

    Resale Button visibility

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

    Allow Resale (Event)

    S360 Resale for any

    spectator (Ticket Rules)

    S360 Resale for initial

    spectator (Ticket Rules)

    Expected behavior

    Resale button visibility

    FALSE

    N/A

    N/A

    Ticket Resale is completely disabled for this event. Any ticket rules permitting resales 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 resales 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 resales 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 URL specified at the event level will be used to redirect spectators to the ticketshop.

    • 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

    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:

    • 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” as it will appear as below at event level 
    • If you use ticketDetails.hidden only, it’s suitable if you have different URLs for different ticket categories/types/locations. But since it’s under ticket level, so you can’t do a bulk update massively for all tickets

    • How it is displayed on app:

    Image Removed

    Image Removed
    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.