
Belong CheckIn provides wallet-optional access for event visitors by creating a guest wallet automatically on their first visit. It lets guests begin without wallet setup, then secure and enrich the same account later through email, Google, a Belong account, or a linked passkey.
The automatically created guest wallet is an EVM wallet. A visitor does not need to sign up or manage a seed phrase before starting, and the wallet acts as the persistent identifier for check-ins, rewards, and tickets. When the visitor later signs in, the original EVM address is preserved rather than replaced.
This account model separates the first visit from the decision to sign in. A guest can start instantly with an auto-created wallet, while email sign-in secures the account with a one-time code. Google sign-in adds a Sui wallet alongside the existing EVM wallet, and linking a Belong account connects the visitor’s Belong identity for cross-product features.
Belong CheckIn also supports passkeys for signed-in accounts. A visitor can link a passkey for faster future sign-in with Face ID, Touch ID, or device biometrics, then view or remove linked passkeys from Profile → Integrations.
The account can therefore hold wallets across more than one chain. The EVM wallet is created for every user, while a Sui wallet is added when the user signs in with Google.
Wallet-optional access is for visitors who want to begin using Belong CheckIn without completing wallet setup first. The guest option is the direct route: the app creates the EVM wallet on the first visit, with no signup and no seed phrase.
Email sign-in is suitable when a visitor wants to secure the account with an email one-time code. Google is another supported sign-in choice and adds a Sui wallet without replacing the original EVM wallet. Visitors who already have a Belong identity can link their Belong account for cross-product features.
A passkey is useful after sign-in when the visitor wants faster future access through Face ID, Touch ID, or device biometrics. Because passkeys can be viewed and removed from Profile → Integrations, the signed-in visitor can manage those linked sign-in methods from the app.
The wallet area is also relevant after the first check-in. Visitors can use it to view balances and transaction history, see and use tickets and memberships, and track rewards and vesting. Operators can manage venue payment accounts from the same area.
Wallet creation does not mean that every ticket is an NFT. Regular, non-NFT ticket purchases use Stripe Connect card checkout and issue a ticket registration and entry QR; the buyer does not need to fund a crypto wallet or mint an NFT. NFT tickets instead use the configured NFT checkout partner, where cards may also be accepted, and the ticket NFT is delivered to a wallet.
Consider a visitor arriving at an event and opening Belong CheckIn for the first time. The app creates an EVM guest wallet automatically, so the visitor can check in without first signing up or handling a seed phrase. That wallet becomes the persistent identifier for the visitor’s check-ins, rewards, and tickets.
After the event, the visitor can secure the account with an email one-time code. The EVM address remains the same when the account moves from guest access to signed-in access, so the original wallet is preserved. If the visitor later links a passkey, future sign-in can use Face ID, Touch ID, or device biometrics.
The visitor can then return to the wallet area to see balances, transaction history, tickets, memberships, rewards, and vesting. If Google is chosen as the sign-in method, a Sui wallet is added alongside the existing EVM wallet rather than taking its place.
Read the Wallet & Sign-In documentation for the complete account model, supported sign-in methods, passkey controls, and wallet-management options.
Open Belong CheckIn to start with an automatically created guest wallet or use one of the supported sign-in options.
No. Belong CheckIn creates an EVM wallet automatically on the visitor’s first visit, with no signup and no seed phrase. The guest wallet can identify check-ins, rewards, and tickets.
The original EVM address stays the same when a guest becomes a signed-in user. Email secures the account with a one-time code, while Google also adds a Sui wallet alongside the EVM wallet.
Yes. A signed-in visitor can link a passkey for faster future access with Face ID, Touch ID, or device biometrics. Linked passkeys can be viewed and removed from Profile → Integrations.