Payments
Overview
Belong CheckIn supports regular (non-NFT) tickets and NFT tickets. Paying by card does not determine which ticket a buyer receives: regular ticket payments use Stripe Connect, while NFT purchases use the configured NFT checkout partner and can also accept cards. Venue payment-request QR codes are a separate payment flow.
Card checkout
| Route | Customer payment | What the customer receives |
|---|---|---|
| Regular (non-NFT) event ticket | Credit or debit card through Stripe Connect | A paid ticket registration and entry QR; an NFT or crypto wallet is not required for the purchase |
| NFT ticket | Card or crypto through the configured NFT checkout partner, where available | A ticket NFT after the purchase completes |
| Venue payment-request QR | The venue's supported wallet payment or enabled thirdweb card route | A recorded venue payment/check-in; this is not the Stripe Connect ticket-order checkout |
Regular ticket payments with Stripe Connect
Organizers connect their Stripe payout account and enable card payments for the event. A ticket tier can accept cards without an NFT collection. The buyer chooses a tier and quantity, completes hosted Stripe Checkout, and receives a regular ticket registration and entry QR after confirmed payment and fulfillment.
Stripe Connect processes the payment on the organizer's connected account. A successful card charge and delivery of the ticket are separate stages: if delivery is still pending, check the existing order rather than paying again. Available events and payment methods depend on the organizer's configuration and payment readiness.
NFT ticket checkout by card or crypto
For an NFT ticket, the configured NFT checkout partner handles the purchase. Credit and debit cards can be available as well as supported crypto wallets; a card purchase can still deliver an NFT. The available methods depend on the checkout partner, network, and collection configuration. The hosted NFT Checkout integration documents its thirdweb wallet and enabled card methods.
Do not describe every card purchase as a Stripe Connect purchase or every paid ticket as an NFT. See Fees & Staking for the separate card-processing and NFT fee categories.
Venue payments and bracelet balances
The existing Venue payment flow settles supported USDC/LONG payments through the venue payment account. Where enabled, thirdweb's card checkout can help a customer complete that payment. It is separate from regular Stripe Connect ticket checkout; connecting Stripe for event tickets does not automatically enable Stripe for every venue QR payment.
Stripe Connect card top-ups for event bracelets are a separate, configuration-gated route. Only describe them as available when the event and the bracelet_topups payment capability report availability. A regular ticket payment being available does not prove bracelet top-ups are enabled.
Payment-request QR
For venues where staff confirm the amount before a customer pays (for example, a POS total), use a payment-request QR. The customer scans, staff send the amount, and the customer completes the supported payment route shown in the app.
Operator flow
- In Hub details → CheckIn → General, set Check-in Access to Venue payment
- In Venue, set the venue payment flow to owner-set amounts
- On the Check-in QR Code card, switch from Check-in to Pay request
- Optionally add a label such as
Table 12,Bar,Patio, orRegister 2 - Print, download, copy, or share the QR
- When a visitor scans it, a pending request appears for staff with the source and label
- Staff send the amount; the visitor pays and the check-in is marked paid
Customer flow
- The visitor scans the payment-request QR
- The app confirms the venue still accepts owner-quoted payments
- The visitor confirms the request
- Staff send the amount
- The visitor completes the offered wallet or enabled card route and the transaction is recorded