# Accept Card Payments for Crypto-Settled Venue Payments Source: https://belong.net/blog/accept-card-payments-for-crypto-settled-venue-payments Published: 2026-11-03T08:59:49.652Z Updated: 2026-11-03T08:59:56.224Z Learn how Belong CheckIn can use enabled card checkout for venue payments that settle in supported USDC or LONG through the venue account. Accept Card Payments for Crypto-Settled Venue Payments What it does Belong CheckIn supports an enabled thirdweb card checkout for venue operators accepting a venue payment from a customer. For venues using this capability, the customer can complete the card checkout while the existing Venue payment flow settles supported USDC or LONG through the venue payment account. This is a venue payment capability, not the regular event-ticket checkout. Regular, non-NFT tickets use Stripe Connect and hosted Stripe Checkout when the organizer and event are configured. NFT tickets use the configured NFT checkout partner and can offer cards or supported crypto wallets where enabled. Venue payments instead use the supported USDC or LONG wallet flow, with thirdweb card checkout available to help the customer complete the payment where it has been enabled. That distinction keeps the payment method separate from the result. A regular ticket buyer receives a paid ticket registration and entry QR after confirmed payment and fulfillment. An NFT ticket buyer receives a ticket NFT after the purchase completes. A venue payment produces a recorded venue payment and check-in rather than a Stripe Connect ticket order. Belong CheckIn also supports a payment-request QR for venues where staff confirm the amount before the customer pays. The customer scans, staff send the amount, and the customer completes the supported wallet or enabled card option shown in the app. How it works - Confirm the venue payment capability. Use the Venue payment flow only where the venue payment account supports the required payment. The documented settlement applies to supported USDC or LONG payments, and the thirdweb card checkout is available only where enabled. - Set Venue payment access. In Hub details → CheckIn → General, set Check-in Access to Venue payment. This selects the venue payment experience rather than a standard check-in flow. - Choose owner-set amounts when staff provide the total. In Venue, set the payment flow to owner-set amounts. This configuration is intended for a venue where staff confirm an amount, such as a POS total, before the customer pays. - Create the payment-request QR. 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. - Identify the payment point. Add an optional label such as Bar, Patio, Table 12, or Register 2. Staff see the source and label when the customer's scan creates a pending request. - Let the customer scan and confirm. The app confirms that the venue still accepts owner-quoted payments. The customer then confirms the request, and staff send the amount. - Offer the supported payment option. The customer completes the wallet option or enabled card option displayed in the app. Where thirdweb card checkout is enabled, it can help the customer complete the venue payment that settles through the supported Venue payment flow. - Record the result. After the customer pays, the transaction is recorded and the check-in is marked paid. This result remains separate from a regular ticket registration or an NFT ticket purchase. The app re-validates venue settings every time the payment-request QR is scanned. A stale QR therefore cannot force a payment after the venue no longer accepts the owner-quoted flow. Who it's for and when to use it This capability is for venue operators that use the supported USDC or LONG venue payment flow and have thirdweb card checkout enabled. It is useful when a customer should be able to complete the offered card option without changing the venue transaction into a Stripe Connect ticket order. Use the payment-request QR when staff need to confirm the amount first. The documented examples include a bar, patio, table, and register, and the optional label helps staff identify the source of each pending request. The customer starts by scanning, while staff remain responsible for sending the amount. Do not assume that connecting Stripe for event tickets enables venue card payments. Stripe Connect for regular tickets is separate from the venue payment flow. A configured regular-ticket checkout does not automatically enable Stripe for every venue QR payment. Do not assume that a card payment defines the ticket format either. Regular event tickets use Stripe Connect. NFT tickets use the configured NFT checkout partner, which can support cards and crypto according to the partner, network, and collection configuration. Venue payments have their own supported wallet or enabled thirdweb card option. Event-bracelet card top-ups are another separate capability. They should only be presented as available when both the event and the bracelet_topups payment capability report availability. Regular ticket payment availability does not prove that bracelet top-ups are enabled. At the event At a venue bar, staff can display a payment-request QR labelled Bar. A customer scans it, the app checks that owner-quoted venue payments remain active, and the customer confirms the request. Staff then send the amount from the pending request. The app presents the supported payment option. If thirdweb card checkout is enabled for that venue flow, the customer can use the card option to help complete the payment. The Venue payment flow settles the supported USDC or LONG payment through the venue payment account. When payment finishes, the transaction is recorded and the check-in is marked paid. This is not a regular ticket purchase. It does not use the Stripe Connect ticket-order checkout, and it does not imply that bracelet top-ups are available. It is the documented venue payment flow with its own payment account, supported settlement assets, and enabled customer payment options. Get started Read the Belong CheckIn Payments documentation to review venue settlement, card availability, and the payment-request QR steps. Confirm that the venue payment account supports the intended USDC or LONG payment and that thirdweb card checkout is enabled before presenting card payment to customers. Open Belong CheckIn, select Venue payment, and configure owner-set amounts when staff need to provide the total. Switch the QR card to Pay request, add an optional source label, and print, download, copy, or share the dedicated code. Keep ticket checkout and venue payment setup separate. Stripe Connect handles regular ticket cards, the configured NFT checkout partner handles NFT purchases, and the Venue payment flow uses its supported wallet option or enabled thirdweb card checkout. FAQ Can a customer use a card for a crypto-settled venue payment? Where thirdweb card checkout is enabled, it can help the customer complete a Venue payment. The existing Venue flow settles supported USDC or LONG through the venue payment account. Does Stripe Connect for tickets enable card payment at every venue QR? No. Regular ticket checkout through Stripe Connect is separate. Connecting Stripe for event tickets does not automatically enable Stripe for every venue QR payment or enable the thirdweb card option. Is a card-based venue payment an NFT ticket purchase? No. A venue payment records a venue payment and check-in. NFT tickets use the configured NFT checkout partner, while regular tickets use Stripe Connect and produce a registration and entry QR.