...
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 poss
- 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?
...
- 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
...
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=
...
- ticketDetails.hidden.index.key = RESALE_TICKETSHOP_URL
- ticketDetails.hidden.index.value = https://ticketshop.secutix.com/account/resale/resellTickets?ticketI
...
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:
...
| Include Page | ||||
|---|---|---|---|---|
|