SC Ticketing  ·  June 2026
RTQ Platform
Delivery Status
NBA 2026 & FU17WC 2026  ·  August 2026 Target
Prepared for Executive Director  ·  Internal Use Only
What We Have Today
🎫

Secure Digital Ticket

Timed rotating QR code. Auto-brightness for scanning. Match info, seat, and zone clearly displayed.

🔒

Security Features

Screenshot disable active. Running dash around QR code prevents copying or duplication.

📋

Ticket History & Active/Expired View

Fans see all active and past tickets — complete attendance record in-app.

Accessibility Indicators

Accessibility flags displayed on qualifying tickets for gate identification.

📡

Offline Ticket Mode

Ticket remains accessible when offline. App displays an "offline" label, and a "low connection" label when signal is weak.

💬

Live Support Chat

In-app live chat with support, added following SC's request.

Access Control Flag

A "Validated" stamp appears on top of the QR code once a ticket is scanned at the gate.

📍

Detailed Ticket Information

Flow data (category, section, row, seat) and gates opening time displayed on the ticket, per SC's request.

🛒

Discover Screen

Fans browse upcoming events and reach the purchase page directly from within the app.

↔️

Transfer & Claim Flow

Ticket transfer mechanism built. Claim flow active. Transfer and recovery available.

💰

Resale Platform

Built and ready, accessible directly from the RTQ app. Awaiting deployment at the next suitable event.

⚙️

Operator-Initiated Transfer & Recovery

Operators can transfer or recover tickets via C-Panel even after the cut-off window — supporting customer service operations on event day.

What We Requested — May 2026 Platform Specification

Following the Amir Cup, SC Ticketing submitted a consolidated Platform Specification to FeverUp — a formal document replacing the previous approach of ad hoc feature requests. It covers 24 capabilities across 5 workstreams, all targeting delivery by August 2026 ahead of NBA 2026 and FU17WC 2026. Click any workstream to expand the capability list.

Sales & Inventory
4
capabilities
Per-Sales-Lot rule configuration
Attribute-driven Sales Lot routing
Visual differentiation of tickets by Sales Lot
Sales Lot session-level configuration
Ticket Lifecycle
3
capabilities
Transfer, Recovery, and Return lifecycle
Digital-to-physical and physical-to-digital conversion
Bulk transfer with B2B traceability
Back-Office Tooling
5
capabilities
Full ticket history visibility in C-Panel
Operator-facing seat assignment UI
Role-based access control framework
B2B Distribution Portal
Audit trail framework
RTQ Mobile App
11
capabilities
Transfer state rendering on the ticket card
Notifications history in the app
Push notifications for transfer events with deep-linking
Saved recipients for ticket transfers
End-to-end ticket purchase in the RTQ app
Searchable country selection in customer profile flows
Ticket purchase history in the Profile section
Accessibility ticket and companion ticket permanent linkage
Accessibility identification on ticket card and ticket info view
Critical update labels on ticket cards
NFC trigger mitigation at gate scan
Payments
1
capability
Local Qatar payment gateway, configurable per event
This specification marks a structural shift in how SC engages with FeverUp — from reactive feature requests to a defined, accountable delivery framework. Every capability has a clear requirement, a priority level, and a target event.
Capabilities Not Yet Responded To by FeverUp

A set of capabilities submitted in the May specification have not yet received a formal response from FeverUp. These are lower-priority items for August 2026 and SC has not pushed on them at this stage. They remain on the full specification baseline.

Bulk Transfer — Distribution PortalBulk transfer of tickets from the Distribution Portal for B2B clients.
Accessibility Pair LinkageAccessibility ticket and companion ticket permanently linked through the lifecycle.
Time-Bound C-Panel AccountsOperator accounts with time-bound, individually scoped permissions for back-office access.
Zendesk IntegrationCustomer support history integration with Zendesk for unified case visibility.
Accessibility Ticket IdentificationVisual indication of accessibility tickets on the ticket card and within the ticket info view.
Critical Update LabelsCritical update labels on ticket cards to surface urgent changes to fans.
NFC Trigger MitigationMitigation of accidental NFC triggers during gate scan to prevent disruptions.
Concurrent Session ControlConcurrent session tracking and forced logout for back-office accounts.
These items are parked — not forgotten. SC's focus for August 2026 is on the capabilities where FeverUp has formally responded.
Delivery at a Glance — Responded Capabilities

Based on FeverUp's formal responses received 22 June 2026. This is the current delivery picture across capabilities where FeverUp has formally responded.

Confirmed Delivered
Confirmed
2
Partially Delivered
Partial
3
Deferred Beyond August
Deferred
5
Contested / Not Delivered
Contested
4
Unconfirmed
Unconfirmed
2
All deferred and contested items remain on the full specification baseline. Deferral is not a waiver. SC continues to hold FeverUp to the original requirements.
Differentiated Configuration per Client Group — A Step Forward

Today, all client groups share the same ticket configuration. A VIP ticket and a General Admission ticket are configured identically at the platform level.

With this capability, each group — General Admission, VIP, VVIP, and Hospitality — will have its own independent configuration. The result is a genuinely differentiated digital ticket experience for each audience.

  • Independent ticket description per client group
  • Independent ticket appearance and visual identity
  • Independent transfer rules per group
  • All differences visible digitally in the RTQ app
Today — all groups share one configuration
All client groups → Same ticket design, same rules
After delivery — each group independently configured
General AdmissionOwn design · Own rules
VIPOwn design · Own rules
VVIPOwn design · Own rules
HospitalityOwn design · Own rules
Intelligent Sales Routing — QID-Based Access at Point of Sale

Today, any fan can purchase any available ticket regardless of who they are. There is no mechanism to direct specific audiences to specific areas of the stadium at the point of sale.

FeverUp is developing a mechanism that reads a fan's verified QID at login and automatically grants access to designated ticket categories — no manual intervention required.

SC is also exploring nationality and country of residence as additional routing attributes for future events.

This approach replaces IP-based sales controls, which SC does not recommend due to their technical limitations and unreliability.
QID-based purchase flow
1
Fan logs in
Opens the RTQ app or web sales page and signs in to their account.
2
QID verified
Platform reads the fan's verified Qatar ID from their profile.
3
Eligible seats displayed
Only the ticket categories the fan is eligible for are shown — automatically.
🎟️
Fan purchases the right ticket for them — without any manual filtering or intervention.
Ticket Transfer Lifecycle — What We Envisioned vs. What Is Delivered
Sender initiates transfer
Delivered
Recipient accepts or declines
Delivered
Operator override in back office
Delivered
Ticket expires if unclaimed
Delivered
Sender cancels pending transfer
Not delivered
User B returns ticket to User A
Pushed to 2027
Push notifications at every step
Not delivered
Why We Cannot Activate Accept/Decline Today
Accept and decline are built and working. The blocker is the recovery functionality. Today, if a fan sends a ticket to the wrong address, they can recover it themselves. If we activate accept/decline alongside recovery, the two mechanisms contradict each other — there is no point in the recipient accepting if the sender can simply take the ticket back.

To activate accept/decline cleanly, recovery must be disabled. But disabling recovery today means fans who send to the wrong address have no self-service option — they would have to contact support to recover on their behalf.
Solution: FeverUp to deliver cancel transfer or return functionality. With either of these in place, recovery can be disabled safely and the full accept/decline flow becomes usable.
Ticket Purchase — In-App vs. External Browser
🎯 What SC requested
Fans complete the full ticket purchase journey inside the RTQ app — browsing, selecting, and paying — without being redirected to an external browser at any point.
⚙️ What FeverUp will deliver
When a fan taps to purchase, they will be redirected to an external browser to complete the transaction. The fan will not need to log in again when the browser opens — their session will carry over automatically. This is referred to as SSO. The core redirect, however, will remain.
📅
SC's deadline for end-to-end in-app purchase: end of October 2026

For events with seat selection, the redirect is understandable. Even FeverUp's own app does not support in-app seat selection purchase. This is an industry-level limitation at this stage.

However, for events without seat selection, there is no technical reason the full purchase cannot happen inside the app.

That is SC's intent and what we continue to push for.

Saved Recipients for Ticket Transfers

Fans currently have to manually enter the full details of the person they are transferring a ticket to — every single time. For fans who regularly transfer tickets to the same people, this is unnecessary friction.

SC requested the ability to save frequent transfer recipients in the app — so repeat transfers require no manual re-entry.

15
June 15 — FeverUp confirmed this capability as feasible and on track for delivery.
22
June 22 — FeverUp reversed their position. Capability dropped entirely, citing priority — not a technical constraint. Earliest evaluation pushed to 2027.
What it would look like — saved contacts in transfer flow
AK
Ahmed Al-Khalifa
ahmed.k@email.com · Frequent recipient
SM
Sara Mohammed
sara.m@email.com · Frequent recipient
FA
Faisal Al-Ansari
faisal.a@email.com · Frequent recipient
Dropped by FeverUp
No technical justification provided.
SC has not accepted this position. Full requirement stands.
Remaining Items — Deferred and Unresolved
⏳ Deferred — FeverUp targeting Q4 2026
🎫

Transfer State on Ticket Card

Ticket card does not show whether a transfer is pending, accepted, or declined. Fan must navigate separately.

🔔

Push Notifications for Transfer Events

Fans not notified in-app when a transfer is sent, accepted, or declined. Deep-linking not yet available.

📬

Notifications History in App

No dedicated screen for fans to retrieve past notifications. Once dismissed, notifications are gone.

🛍

Purchase History in Profile

Fans cannot view their full ticket purchase history from their profile.

⚠️ Unresolved — No confirmed delivery date
🔐

Role-Based Access Control (RBAC)

The operator permission framework has been pushed to Q2 2027. No interim solution proposed. Expected by end of 2026.

📁

Full Ticket History in Back Office

FeverUp's response was insufficient to assess delivery. SC cannot confirm what is and is not in place.

📅 SC's position: all items deferred by FeverUp to Q4 2026 are required by end of October 2026 — ahead of FU17WC 2026.
All items listed here remain on the full specification baseline. SC has not waived any requirement. Deferred means a later delivery date — not a cancelled obligation.
Thank You
SC Ticketing  ·  RTQ Platform Programme
June 2026  ·  Internal Use Only
📝 Slide Notes
Slide 1
No notes yet.
Add a note below for this slide.
Adding note for Slide 1
1 / 12