Set Ticket Supply Before Sales with Belong CheckIn
Publication date

Set Ticket Supply Before Sales with Belong CheckIn

What it does

Belong CheckIn lets event organizers configure ticket tiers, pricing, and supply before tickets go on sale. For organizers creating free or paid events, the event-creation workflow turns a plain-language description into a configured event. Organizers can choose regular (non-NFT) tickets with Stripe Connect card payments, or NFT tickets purchased through the configured NFT checkout partner.

The setup can begin in chat, through Voice Mode, or with a guided wizard. Chat accepts a description of the event and drafts the event and its ticket tiers. Voice Mode transcribes a spoken event description and creates the event with a visual summary card. The guided wizard steps through free or paid event setup with prompts.

Ticket supply is configured at the tier level. An organizer can create multiple tiers, such as General, VIP, or Student, and give each tier its own price and supply. This places the number of tickets available in the same setup flow as the event title, date, location, and pricing.

Belong CheckIn also connects the event setup to the rest of the ticket journey. After reviewing the event details, the organizer chooses the regular or NFT ticket format. Regular ticket buyers pay by card through Stripe Connect and receive a ticket registration and entry QR without an NFT. NFT ticket buyers use the configured NFT checkout partner; card or crypto methods can be available, and that route delivers a ticket NFT.

How it works

  1. Describe the event. Enter the title, date, location, ticket tiers, and pricing in plain language. The assistant uses that description to draft the event and its tiers. Organizers can also use Voice Mode to transcribe the event description or follow the guided wizard for a prompted free or paid setup.
  2. Configure each ticket tier. Add the tiers the event needs and set a price and supply for each one. The documentation uses General, VIP, and Student as examples of separate tiers. Because every tier has its own supply, the organizer can define what will be offered before opening sales.
  3. Review the event card. The assistant presents an event summary card containing the key details and a direct link. This review stage comes before opening sales, so the drafted event information, ticket format, and tier structure can be checked together.
  4. Configure the chosen checkout. For regular tickets, connect the organizer’s Stripe account and enable card payments for the event. An NFT collection is not required. For NFT tickets, configure and deploy the collection; when a wallet signature is required, Belong CheckIn displays an inline signing surface.
  5. Sell tickets. Regular tickets use Stripe Connect card checkout and are fulfilled as ticket registrations and entry QR codes. NFT tickets use the configured NFT checkout partner, which can accept cards or crypto where supported. NFT mint and resale fees apply to the NFT route; do not apply them to regular tickets that do not mint an NFT.
  6. Check attendees in. Use the issued ticket registration and entry QR for regular tickets. For NFT access, use the configured NFT verification flow. Follow the admission route for the event’s selected ticket format.

This sequence keeps event description, ticket tiers, review, checkout configuration, sales, and check-in in one documented progression. The organizer moves from a natural-language brief to live tickets, while the ticket supplies remain part of the tier configuration created before sales.

Who it’s for and when to use it

This workflow is for organizers who need to create an event and define its ticket offer. It supports both free and paid event setup, with chat, voice, and guided options for entering the details.

Use it when an event requires more than one ticket type. Separate tiers can represent options such as General, VIP, and Student, with a distinct price and supply for each. The same workflow also suits an event with a simpler ticket structure because the organizer still describes the event, reviews the summary card, configures regular or NFT checkout, and opens sales.

It is also relevant when event access is connected to a hub. NFT ticket mode connects hub access to paid ticket tiers. If a hub does not have a ticketed event attached, the app can guide the organizer into chat-assisted paid event setup.

The event does not have to rely on a single discovery surface. Belong supports event pages, event-week pages, and shareable public event maps that prioritize active location context. Attendees can also discover events in the app.

At the event

Consider an organizer running an event with General, VIP, and Student admission. During setup, the organizer creates those ticket tiers and assigns each its own price and supply. The assistant drafts the event from the description, and the organizer reviews the summary card before enabling Stripe Connect regular ticket payments or configuring the NFT collection and its checkout.

For a regular ticket, the buyer completes Stripe Connect card checkout and receives a ticket registration and entry QR after confirmed payment and fulfillment. For an NFT ticket, the configured NFT checkout partner handles the supported card or crypto method and delivers the ticket NFT. When doors open, staff use the admission flow for the ticket that was actually issued.

The tier names, prices, and supplies were defined before sales. At the venue, the check-in step therefore follows the event and ticket configuration the organizer already reviewed, rather than creating a separate ticket structure at the door.

Get started

Open the Belong CheckIn event-creation guide to review the available creation methods and the full sequence from event description to ticket sales and check-in.

Then go to Belong CheckIn to create the event. Describe the title, date, location, ticket tiers, and pricing; set the price and supply for each tier; review the event card; and configure the selected regular or NFT checkout when the details are ready.

Before opening sales, check the tier configuration shown in the event summary. Regular tickets use Stripe Connect card checkout; NFT tickets use the configured NFT checkout partner and can also accept cards where enabled. Check that the event’s payment route is available before opening sales.

FAQ

Can each ticket tier have a different supply?

Yes. Belong CheckIn supports multiple ticket tiers, and each tier can have its own price and supply. The documentation gives General, VIP, and Student as example tiers.

When does the ticket NFT collection get created?

Only NFT tickets require a collection to be created during deployment, after event review. Regular Stripe Connect tickets do not require an NFT collection. When NFT setup requires a wallet signature, the app displays an inline signing surface.

How are tickets checked at the event?

Regular tickets use their issued registration and entry QR. NFT access uses the configured ticket NFT verification flow. A card purchase can belong to either route, so follow the ticket format issued for that event.

Are all paid tickets NFTs?

No. Regular tickets can be paid by card through Stripe Connect and issue a ticket registration and entry QR. NFT tickets use the configured NFT checkout partner, which can also accept cards where enabled. The payment method and ticket format are separate choices.