Why should organizer use it?
- To allows user to send ticket to another valid email. Transfer feature is at ticket level, so organizer must define if a ticket can be transfered or not.
How it works?
- A ticket can be transferable or not based on these settings below:
| transferRules.groupId | Transfer rules can technically be different for every ticket. Organizer might want to chose to have different transfer rules for different types of ticket (ex: Adult, child, VIP, etc…). This GroupID is the Transfer rules group ID representing a group of transfer rules applied to certain tickets. If Organizers want to apply the same rules to every tickets, by default this groupID is set to the EventID and every ticket will be in this group. |
|---|---|
| transferRules.maxNumberOfTicketPerPhoneInGroupId | Maximum amount of tickets per phone for this Transfer rules group id. |
| transferRules.maxNumberOfTransferPerPhoneInGroupId | Total amount of transfers per Phone (-1 feature is disabled). |
| transferRules.maxNumberOfTransferPerTicketInGroupId | Total amount of transfers per Ticket (-1 feature is disabled). |
| transferRules.assignTransferLimit | Define upper bound of ticket's transfer level for the "Assign" function |
| transferRules.allowTransfer | Enables or Disables transfer functionality for given match (Send menu item in the ticket view hidden or displayed). |
| transferRules.allowTransferMainApplicant | Enable or Disable transfer functionnality for Main Applicant ticket's. |
| transferRules.allowTransferAfterActivation | Enables or Disables transfer functionality for given match for Activated Tickets (Send menu item in the ticket view hidden or displayed). |
| transferRules.allowTransferAfterActivationByBT | Enables or Disables transfer functionality for given match for Activated Tickets by bluetooth (Send menu item in the ticket view hidden or displayed). |
| transferRules.allowTransferAfterControl | Enables or Disables transfer functionality for given match for Controlled Tickets (Send menu item in the ticket view hidden or displayed). |
| transferRules.keepOneInGroupId | Force ALL ticket wallet holders to keep at least 1 ticket per given Match. |
transferRules.keepOneAtInjectInGroupId | Force ticket wallet holder to whom tickets were originally injected to keep at least 1 ticket per given Match. E.g. all his transfer guests will be able to forward all the tickets they received. |
- Organizer can check if a specific ticket is transferable or not on ticket detail view:
- If organizer wants to request for transfer reason, enable the Transfer Reason Feature to true.
- User can also have option to select language when transfering a ticket (email sending to recipient) in case the recipient has not yet registered an account.
- Language options will be retrieved from app supported languages
- Text labels for transfer reasons are adjustable on Crowdin.
How feature is visible on TIXNGO app?
string | Indication as screenshot above |
|---|---|
| transfer_functionality_description | description on ticket screen |
| transfer_functionality_title | |
| recipient_confirmation_page_description | description on confirmation screen |
| transfer_multiple_ticket_option | select more tickets to send |
| transfer_recipient_empty_value |