Ticket sales
Revenue from paid orders
Sales data is unavailable.
Connecting to HighLevel…
Seat holds, payment events, Elite applications and Wallet updates waiting
Revenue from paid orders
Sales data is unavailable.
Event totals
| Attendee | Order | Tier | Status | Amount | Actions |
|---|---|---|---|---|---|
| No orders yet. | |||||
Recent changes for this event
See every order and the attendees on each ticket.
Unpaid checkouts holding seats, and FanBasis payment events that need a person.
Loading seat holds…
| Buyer | Hold | Seats | Age | Time left | Payment link | Actions |
|---|---|---|---|---|---|---|
| Connect to HighLevel to view seat holds. | ||||||
Loading payment events…
Elite is by application and phone call. Read the application, approve after the call, then create and send the payment link. Answers are saved as applicants go, so an application shows here as soon as they pass the contact step: “Not finished” until they submit it.
Loading applications…
Find orders, view attendee details, and manage ticket tiers.
Find each attendee by name, tier, or order.
0 ticket holders
| Attendee | Order | Tier | Status | Amount | Actions |
|---|---|---|---|---|---|
| No ticket holders yet. | |||||
Send time-sensitive event updates to selected Apple Wallet pass holders.
Only active passes registered on a device are eligible.
Queued, then accepted by Apple, then fetched by Wallet. Accepted by Apple is not fetched: a locked or idle phone may not ask for a long time. Fetched by Wallet counts passes the service returned to Wallet (HTTP 200), so a later fetch also counts for an older alert; it does not prove anyone saw the alert. Wallet decides how to display it (Lock Screen or Notification Center). Passes still waiting are under Wallet updates waiting in Wallet setup.
Loading alert history…
Provider status, pass details, arrival pins, staff credentials and every attendee’s saved pass.
Buyers always get the web ticket and QR code. A Wallet button shows only while its provider works.
Add a pass to Wallet and visit one of its pins with location access and Lock Screen suggestions enabled. For a push test, open Push notifications and check that the pass appears in the audience count.
Issue a Staff, Speaker or Performer pass for Apple Wallet. The staff door scanner admits it on every event day until you cancel it. It is never sold and records no purchase or message.
Loading credentials…
Paste the URL or code from a test pass’s QR. This updates only the sandbox test-pass record.
Saved Apple passes that have not fetched a change yet. Apple accepting the update push only means Apple took the request: the phone still has to ask, and a locked or idle phone can wait a long time. This is a wait for Wallet, not a failure on the attendee’s phone. The web ticket and its QR code are always current.
Loading Wallet updates…
| Ticket | Expected change | Last push accepted | Last fetch | Age | Status | History |
|---|
Each attendee’s Wallet pass, newest activity first. Last fetched is the last time Wallet was served the pass through its update request (a buyer’s own download does not count). Open History to see downloads, saves, updates and voids.
Loading passes…
| Attendee | Pass | Apple Wallet | Google Wallet | Last fetched | History |
|---|
Apple acceptance only confirms Apple took a refresh request. A signed pass shows Wallet asked for it; only a pass served to Wallet (HTTP 200) means the phone received the update, and nothing here proves anyone looked at it.
Loading Wallet activity…
Manage event discounts and track how often they’re used.
| Code | Discount | Eligible tickets | Uses | Expiration | Status |
|---|---|---|---|---|---|
| No discount codes yet. | |||||
| Code | Discount | Eligible tickets | Uses | Starts | Ends | Status | Actions |
|---|---|---|---|---|---|---|---|
| Connect to HighLevel to manage discount codes. | |||||||