--- title: Setting up and managing Secure Smart Tickets slug: en/setting-up-and-managing-secure-smart-tickets createdAt: 2024-02-07T14:26:09.242Z --- Secure Smart Tickets offer an advanced, user-friendly solution for controlling ticket fraud and scalping, focusing on a balance between security and accessibility for legitimate buyers. ## Setting Up Secure Smart Tickets ### Smart Tickets vs. Secure Smart Tickets Regular Smart Tickets have standard security; the QR code is visible as soon as the tickets appear in the app after purchase. It is also possible to forward these tickets to other app users. Secure Smart Tickets offer higher security as they **cannot be forwarded** and are **delivered to only one device**. In addition, the QR code refreshes every 30 seconds. ### Configuration Setting up Secure Smart Tickets requires a specific configuration. For example, a separate delivery scenario must be created where the 'Allow e-tickets' field is set to 'Only secure smart tickets'. If you want to restrict this delivery scenario to specific events, a custom field must be activated and scripts added to the delivery scenarios. Contact support to set this up. ### Access Control Secure Smart Tickets can be scanned using Android scanners running a recent version of the [Getting started with the Ticketmatic scanning app](docId\:xf0vR7MrpAxuhO62CKC2J). ## Secure Smart Tickets Management Module Via **Orders > Actions > Manage Secure Smart Tickets** you can open the management module for secure smart tickets. The management module allows you to: - View **detailed information** about which secure smart tickets are delivered to which device - Perform a risk assessment and optionally **activate manual verification** for certain users - **Verify** users - **Transfer tickets** to another device of the user ![](https://api.archbee.com/api/optimize/zGnEynQy6cgPdn1J1kZsn/1VNgQfB0kf8ZeBHOA7zOj_image.png) Next, select the event for which you want to view the secure smart tickets: ![](https://api.archbee.com/api/optimize/zGnEynQy6cgPdn1J1kZsn/SLBe1YydsumQPcaEhIlWJ_image.png) You will now see a list of all users and devices where tickets for the selected event are available. ![](https://api.archbee.com/api/optimize/zGnEynQy6cgPdn1J1kZsn/1DolzOUfMuqOcdBL6MIc3_image.png) Each row provides **information about the user and their device**. Based on this information, you can decide whether manual verification should be activated for the user. The **following info** is shown: | **Field** | **Description** | | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Name** | Name of the user | | **Device** | Name of the device where the tickets are available, indicating whether it is an Android or Apple device, along with the device’s unique code | | **Devices** | Total number of devices on which this user has the app installed | | **Tickets** | Number of tickets available on this device | | **Orders** | IDs of the orders in which these tickets were purchased | | **Loyalty score** | Indicates how often and how many tickets the user purchased in the past (see below) | | **Transfer** | Number of times tickets were transferred between devices | | **Session** | Indicates whether the user had the app installed on this device at the time of ticket purchase. `Existing` means the app was already installed; `New` means the app was installed only after ticket purchase. | | **Status** | Current status for this device | ### Loyalty Score (5 years) :::Paragraph{listStyleType="disc" indent="2"} \-: User bought no tickets in the last 5 years ::: :::Paragraph{listStyleType="disc" indent="2"} v: User bought tickets for at least one event in the last 5 years ::: :::Paragraph{listStyleType="disc" indent="2"} vv: User bought tickets for at least two events in the last 5 years ::: :::Paragraph{listStyleType="disc" indent="2"} vvv: User bought tickets for at least two events in the last 3 years ::: :::Paragraph{listStyleType="disc" indent="2"} vvvv: User bought tickets in the last year and in at least 1 of the previous two years ::: :::Paragraph{listStyleType="disc" indent="2"} vvvvv: User bought tickets for at least one event in each of the last 3 years ::: **** :::hint{type="info"} App users can also transfer their Secure Smart Tickets themselves by logging in on another device with the same credentials. They must provide a reason for this transfer, which you can review in the **log**. ::: ### Detailpage per user Clicking a row takes you to a detail page with further information: ![](https://api.archbee.com/api/optimize/zGnEynQy6cgPdn1J1kZsn/5mr8XLJAw3I7U_M9klTys_image.png) Here you can find: - A list of alternative devices where the user has installed the app (A) - A log of all status changes for this session (B) - Ticket details with a link to the relevant order (C) - A button to activate manual verification for this user (D) ### Manual Verification When suspicious transfers are detected, you can activate manual verification for certain users. - **Activate**: click in the users detailpage on the button Actions ![](https://api.archbee.com/api/optimize/zGnEynQy6cgPdn1J1kZsn/pGKqqNvrN0ZlozHwDBOUV_image.png) - **Impact user:** for these users, the app will display a message instead of the tickets, indicating that identification is required and that they must go to the service desk for the event. - **Configuration**: the message shown can be configured via the mobile app management module: ![](https://api.archbee.com/api/optimize/zGnEynQy6cgPdn1J1kZsn/DhBsyhPW1mTi9jOamu7Xe_image.png) ::Image[]{src="https://api.archbee.com/api/optimize/zGnEynQy6cgPdn1J1kZsn/lp8FGuIHFnbMWm-rbHzYN_image.png" size="32" width="648" height="1326" position="center" darkWidth="648" darkHeight="1326" showCaption="false"} Manual verification can be done from the detail screen as shown above, but also from the list: you can select one or more devices and use the **Action** button to activate or deactivate manual verification (A). ## Secure Smart Tickets for the Customer ### Downloading the App It is not mandatory for a user to have the app installed at the time of purchase, but it is highly recommended. Communication to ticket buyers should clearly suggest installing and logging into the app in advance (e.g., via the delivery email). Ticketmatic records whether the user had the app installed at the time of purchase, which can be used in risk assessment. In case of doubt, manual verification can be activated for the user. ### When is the Barcode Visible? The barcode becomes visible as soon as the tickets are delivered to the wallet. The barcode refreshes every 30 seconds, making it impossible to copy. ### Resale Secure Smart Tickets **cannot be resold** via secondary channels. As an administrator, you maintain full control over all resale and can define the policy. # FAQ Secure Smart Tickets Find the answers to the most frequently asked questions about Secure Smart Tickets here: [Why are tickets not visible in the App?](docId\:T47vZu9QmJhwngoW_GKBu) en [What are Secure Smart Tickets?](docId\:LVtjial9oQyZRzTm-m_M6)