...
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 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 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 | ||
|---|---|---|
| ||
|
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
...
For this parameter to take effect, “transferRules.allowReturnToOrganizer” 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
| Expand | ||
|---|---|---|
| ||
Wallet behavior
User flow
...
...
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
...
...
...
...
...
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=
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=
...
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.
...
| Include Page | ||||
|---|---|---|---|---|
|