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
How to make the Resale on ticketshop available on a ticket in TIXNGO:
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 | ||
|---|---|---|
| ||
|
Resale keys in the Ticket rules
Name | Key | Default Value | Rule |
|---|---|---|---|
S-360 Resale for any spectator | allowReturnToOrganizer | FALSE |
|
S-360 Resale for initial spectator | allowReturnToOrganizerForInitialSpectator | FALSE |
|
| Expand | ||
|---|---|---|
| ||
Wallet behavior
User flow
| Access Resale Actions | Webview | Tickets Returned For Resale | Pending Resale | Ticket you reselling | Cancel Ticket resale | Completed Resale | Ticket 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” section | Once the ticket is posted on the resale platform, it appears in the Pending Resale section, indicating it’s awaiting purchase | Spectators can review details of tickets they are currently reselling | Spectators can cancel the resale, which will return the ticket to their wallet | When a ticket is purchased on the resale platform, it moves to the Completed Resale section, indicating the resale is finalized | Spectators can review details of tickets they are resold |
|
|  |  |  |  |  |  |
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=
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
How it is displayed on app:
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=
| Info |
|---|
TIXNGO differentiates how URLs are managed based on their entry points:
|