Stripe Connect production overview
How Belong uses Stripe Connect for event ticketing
Belong is an event and community platform. Stripe Connect is live in production for one clearly bounded product: fiat card payments for primary sales of standard event admission by organizers to attendees. Every paid order is fulfilled as an off-chain digital ticket with a QR code.
Live Stripe scope
Customer purchase
Admission to a real event, delivered as a standard digital ticket or QR code.
Seller
The event organizer, onboarded through Stripe as a Standard connected account and approved by Stripe to accept charges.
Payment
A Stripe-supported fiat payment through Stripe-hosted Checkout. The ticket price and currency are resolved by Belong’s server, not supplied by the buyer.
Funds flow
A direct charge is created on the organizer’s connected account. Stripe settles the ticket proceeds directly with that organizer; Belong does not hold the organizer’s funds.
Belong’s role
Platform checkout, server-side pricing, order records, QR ticket delivery, organizer tools, customer support, and synchronization of payment and refund status.
Integration status
Live in production. Belong accepts fiat card payments through Stripe Connect for the standard event-ticketing scope described on this page.
How the live payment flow works
- Organizer onboarding. Belong creates a Standard connected account and sends the organizer through Stripe-hosted onboarding. Card sales remain unavailable until Stripe reports that the account has submitted its details and can accept charges.
- Organizer-controlled enablement. Only the verified owner of an event can connect an account or enable card payments. Belong checks the event owner against the connected-account owner again when a buyer starts checkout.
- Attendee checkout. The attendee sees the seller, ticket description, quantity, total price, and currency before paying. Belong derives the amount from the event’s ticket data on the server and creates a Stripe-hosted Checkout Session on the organizer’s account. Belong does not store raw card data.
- Order and ticket delivery. After Stripe confirms the fiat payment, Belong creates one off-chain event registration per seat and issues a standard QR ticket. Webhook processing and the buyer’s order-status check share the same idempotent fulfillment logic so a retry cannot issue duplicate tickets.
- Fees and settlement. The Checkout Session uses a direct charge on the organizer’s connected account. If enabled, Belong takes a configured application fee; Stripe settles the remaining funds with the organizer under that account’s payout settings.
- Refund synchronization. Stripe refund events are verified and recorded by Belong. A full refund marks the order refunded and cancels the corresponding QR registrations so they can no longer be used for admission.
Separation from blockchain functionality
Belong also offers separate blockchain-enabled product features. We are disclosing that broader product context so the production Stripe use is unambiguous. Stripe is used to charge fiat for event admission and to settle those funds with the event organizer. Stripe is not used to process:
- cryptocurrency purchases, sales, conversion, exchange, custody, mining, staking, or initial coin offerings;
- wallet creation or funding, on-chain transfers, payment of blockchain network fees, or payouts to wallet addresses;
- charges for NFT minting, primary or secondary NFT sales, NFT marketplace activity, or token-gated purchases;
- tokens, virtual currency, prepaid value, gift cards, or other stored-value products;
- peer-to-peer money transmission, escrow, crowdfunding, donations, or ticket resale; or
- transactions for an undisclosed merchant, seller, product, or service.
The guaranteed product delivered after every Stripe payment is the off-chain QR ticket described above. The wider Belong codebase also contains an optional, separate post-purchase feature that can create a no-cost NFT representation of an already-valid ticket. It is not sold through Stripe, does not change the Stripe charge, and cannot charge the attendee any on-chain value. It is outside the live Connect scope described here; Stripe-funded orders are fulfilled with off-chain-only ticket delivery.
Production safeguards
- Stripe onboarding must be complete and the connected account must report that charges are enabled before an organizer can turn on card payments.
- Organizer ownership, event ownership, connected-account ownership, and the selected ticket tier are checked on the server before each Checkout Session is created.
- The price and currency come from Belong’s server-side event records; buyers cannot submit their own charge amount. Orders are limited to ten tickets per Checkout Session.
- Checkout creation uses idempotency keys. Webhooks require Stripe’s signature, enforce a five-minute timestamp tolerance, and record event IDs so retries are safe.
- Payment amount, currency, Checkout Session, connected account, and local order must match before Belong issues a ticket.
- Organizers and events must follow Belong’s acceptable-use rules and Stripe’s prohibited and restricted business requirements.
Current production status
As of August 11, 2026, Stripe Connect is live in production for Belong’s standard fiat event-ticketing flow. Organizer onboarding, event settings, buyer Checkout, order storage, webhook processing, off-chain QR fulfillment, and refund synchronization are active. Production card payments are enabled for eligible organizers whose connected accounts can accept charges.
Live mode is enabled only for the fiat event-ticketing scope described on this page. No Stripe funds are routed to cryptocurrency, wallet, token, NFT, or stored-value activity. If that scope changes, Belong will disclose the change to Stripe before enabling it.
Contact and policies
Stripe reviewers can contact [email protected] for business-model details, a product walkthrough, or a funds-flow diagram.
The implementation is based on Stripe’s Connect marketplace guidance and Prohibited and Restricted Businesses policy.