Belong CheckIn POS Events and Venue Follow-Up
Publication date

Belong CheckIn POS Events and Venue Follow-Up

What it does

Belong CheckIn's POS & Check-In Events capability carries a POS payment request into the venue follow-up that staff handle next. It is for venue operators who need a bar or register total to become a pending request, a staff-sent amount, and a recorded payment and check-in.

The documented pattern is a payment-request QR. It keeps the POS moment and the next staff action in one documented venue workflow, without claiming that the POS sends the amount automatically. It fits a venue where the amount is not fixed before the scan. A visitor scans the QR, the request appears for staff, and staff send the amount. The visitor then completes the supported payment route shown in the app.

That follow-up remains identifiable because the pattern also captures attribution. The `payment_request_source field can show whether a payment request came from a standard check-in QR, a static venue QR, or a POS receipt QR. An optional payment_request_label` can carry a staff-facing label such as a table, bar, patio, or register. These are runtime attribution fields; they do not change the venue's check-in configuration.

How it works

  1. In Hub details → CheckIn → General, set Check-in Access to Venue payment. This selects the venue payment check-in mode used by the pattern.
  2. In Venue, set the venue payment flow to owner-set amounts. The venue owner or staff then supplies the amount for each pending request.
  3. On the Check-in QR Code card, switch from Check-in to Pay request. The payment-request QR uses a separate link from the standard check-in QR.
  4. Optionally add a label that helps staff identify the source, such as `Table 12, Bar, Patio, or Register 2`. The label travels with the pending request as attribution.
  5. Print, download, copy, or share the QR, then place it where the relevant visitor can scan it. The documented source values include `checkin_qr, venue_static_qr, and pos_receipt_qr`.
  6. When a visitor scans, the app re-validates that the venue still accepts owner-quoted payments. The visitor confirms the request, and a pending item appears for staff with its source and optional label.
  7. Staff send the amount. The visitor completes the supported wallet or enabled card route offered by the app. When the transaction is complete, it is recorded and the check-in is marked paid.

Payment routes must be kept separate. The existing Venue payment flow settles supported USDC/LONG payments through the venue payment account, and thirdweb's card checkout can help a customer complete that payment where enabled. This is separate from regular Stripe Connect ticket checkout. Connecting Stripe for event tickets does not automatically enable Stripe for every venue QR payment.

Who it's for and when to use it

The payment-request QR pattern is for venue owners and staff who need POS activity at a bar or register to lead to a specific follow-up after a visitor has scanned. The docs use a POS total as the example: it supports a flow where the venue confirms the amount before payment.

It is also useful when staff need to tell scans or requests apart. Source attribution distinguishes a POS receipt QR from a venue static QR or the standard check-in QR. The optional label can give staff a practical location reference.

Staff surfaces can read pending owner-quote requests so that staff can send the amount. Venue operators can also review recent check-ins and reward activity from the venue's CheckIn area.

For programmatic access, the docs point to the Belong API with an `x-api-key` to read event and hub data. Outbound event webhooks that push to an organizer's own endpoint on each check-in are on the roadmap, not a current capability. Today's integration path is to read check-in and venue data through the API.

At the event

A venue operates a bar where each sale produces a POS total that depends on the order. Staff print a payment-request QR for the register and add a staff-facing label. When a visitor scans, the request appears with the source and label. The bar staff member reads the total from the POS, sends that amount, and the visitor completes the supported payment route in the app. The transaction is recorded, and the check-in is marked paid.

If the venue stops accepting owner-quoted payments, the app re-validates that setting on the next scan. The docs explicitly note that a stale QR cannot be used to force a payment.

Get started

Read the POS & Check-In Events documentation for the payment-request QR pattern, attribution fields, and current API access notes. Then open Belong CheckIn to review your hub's CheckIn and Venue settings.

Before distributing a QR, confirm that Check-in Access is set to Venue payment and that the venue payment flow uses owner-set amounts. Then choose Pay request on the Check-in QR Code card, add any useful label, and share the QR.

FAQ

Does the POS determine the payment amount automatically?

No. In the documented owner-set amounts flow, staff send the amount after the visitor scans the payment-request QR.

What can the source and label tell staff?

The source distinguishes standard check-in, venue static, or POS receipt QR requests. The optional label can name a table, bar, patio, or register.

Are outbound check-in webhooks available now?

No. The docs say that outbound event webhooks are on the roadmap. Current programmatic access reads check-in and venue data through the Belong API.