Belong.net Logo
Belong CheckIn

Check-In Modes

Venue access modes, regular ticket registrations, and NFT ticket or membership verification.

Overview

Belong CheckIn uses a single QR-scanning flow that adapts to different kinds of businesses — cafés, events, communities, and co-working spaces. The core idea is a clean split between getting access (buying a ticket or membership ahead of time) and verifying on site (scanning a QR at the door).

Buy / get access (ahead of time):
Regular ticket: Event page → Stripe Connect card checkout → Ticket registration + entry QR
NFT ticket: Event page / Chat / Shop → NFT checkout partner (card or crypto) → Ticket NFT

Check in (on site):
Regular ticket: Staff scan entry QR → Verify ticket registration → Admit
NFT access: Scan venue QR → Check configured NFT → Confirm → Done

Regular (non-NFT) tickets and NFT tickets are both supported. Stripe Connect processes regular ticket payments; NFT checkout partners can accept cards or crypto for NFT purchases. These are different checkout routes, even when the customer pays by card. See Payments.

Access modes

The following settings are the venue/hub access modes, with one primary access mode optionally combined with membership. Regular event ticket registrations are a separate event-ticket admission flow; they do not require an NFT ownership check.

ModeAmount entryNFT checkBest for
FreeNoNoMeetups, free community visits, simple attendance
Venue paymentYes / NoNoCafés, bars, restaurants, paid local experiences
NFT ticketNoYesConferences, concerts, ticketed and gated entry
NFT membershipNoYesClubs, communities, recurring and member-only spaces

Venue payment supports three amount flows:

  • Customer-entered amount — the visitor types in their check total
  • Owner-set quote — staff send an amount after the visitor requests payment (see Payments)
  • Fixed amount — a set price configured by the venue (e.g. a day pass)

The check-in flow

flowchart TD;

A[Scan QR code] --> B[Read venue settings]
B --> C{Multiple modes?}
C -->|Yes| D[Visitor chooses how to check in]
C -->|No| E[Use the single configured mode]
D --> F{Which mode?}
E --> F
F -->|Free| G[Confirm attendance]
F -->|Venue payment| H[Enter or receive amount, then pay]
F -->|NFT ticket / membership| I[Check wallet for NFT]
I -->|Found| G
I -->|Not found| J[Show buy option]
G --> K[Check-in complete]
H --> K

style A fill:#e1f5fe
style K fill:#c8e6c9
style J fill:#fff3e0

Example scenarios

AspectCafé / BarEventCommunityCo-working
EntityHubEventHubHub
ModesPayment + membershipTicket onlyFree + membershipPayment + membership
Amount entryYes (variable)NoNoNo (fixed)
NFT checkOptionalOnly for NFT ticketsOptionalOptional
Daily limit—1 per ticket11
Main outcomeConfigured spend rewardAccessAttendance or configured rewardAccess

Café / Bar — A visitor enters their order total, pays in USDC or LONG, and can receive the venue's configured spend reward. A membership NFT can gate member perks.

Event — Choose regular tickets paid through Stripe Connect or NFT tickets purchased through the configured NFT checkout partner. Regular tickets use their issued registration and entry QR; NFT access checks the configured ticket NFT. Paying by card is possible on either route where enabled.

Community — A free check-in records attendance and can apply the configured flat reward. A membership check-in verifies the configured NFT collection for member-only access.

Co-working — A fixed-price day pass via venue payment, or a monthly membership NFT that's verified on entry.

Edge cases the flow handles

  • Multiple valid NFTs in the wallet — the visitor picks which one to use; already-used-today tickets are marked
  • NFT already used today — a warning appears with other available modes and when it can be used again
  • Amount below the minimum — the payment is blocked with a clear minimum
  • Connection lost mid-payment — the pending state is saved so the visitor can resume, retry, or cancel
Copyright © 2026