Set up chapter-level Bevy Pay so each chapter can receive its own ticket revenue: designate a payment lead, let them connect Stripe from chapter Payments settings, manage the seller account, and change leads without leaving payouts pointed at the wrong Stripe account.

When your community sells paid tickets with Bevy Pay, ticket money has to land somewhere. Most communities use one of these two patterns:

• HQ-level payouts — one community Stripe account receives ticket revenue for every chapter. HQ manages that account from Admin Dashboard → Settings → Payments.
• Chapter-level payouts — each chapter that sells tickets can receive revenue in its own connected Stripe account. An HQ admin designates a chapter Payment lead; that person connects Stripe from the Chapter Dashboard and manages day-to-day money movement for that chapter.

This article walks through the chapter-level path end to end: who does what, how to designate the payment lead, how the payment lead connects Stripe, how to manage the seller account afterward, and how to change the lead without leaving payouts pointed at the wrong Stripe account.

Need the side-by-side comparison of HQ vs chapter (disputes, payout schedule, refund vs delete)? See Managing paid events: payouts, refunds, and deleting attendees. Need community-wide Bevy Pay enablement, fees, or card declines? See the Bevy Pay guide.

Before you start

Make sure these pieces are in place before you try to sell paid tickets under a chapter seller account:

• Bevy Pay is enabled for your community. If paid ticketing is unavailable, start with What HQ must enable first, or ask Bevy Support / your Customer Success Manager.
• The future payment lead is already on the chapter team. The Payment lead list only shows chapter team members. Add them to the team first if they are missing.
• Someone can edit chapter payment settings — typically an HQ admin, or a chapter team member whose role can edit Payment lead, Bevy Pay account, and Currency.
• The payment lead can complete Stripe onboarding with accurate business or individual seller details and a bank account that can receive payouts in the chapter’s currency.
• You know which payout model this chapter should use — chapter seller account (Allow Payment Lead to manage their own account) or community HQ account (Only use HQ account).

Designate a payment lead

Chapter-level payouts start with one named person. The Payment lead is the chapter team member who will connect Stripe and open the chapter’s Payment dashboard. Other organizers can still create events and manage attendees; they do not get the Stripe Connect buttons unless they are the payment lead.

An HQ admin (or a chapter team member with permission to edit payment settings) completes these steps:

1. Sign in and open the Chapter Dashboard for the chapter that should receive its own ticket revenue.
2. In the left navigation, open Settings.
3. Open the Payments tab.
4. Find Payment lead. Open the list and select the chapter team member who will own Stripe for this chapter. If the person you want is not listed, add them to the chapter team first, then return to this tab.
5. Find Bevy Pay account. Choose Allow Payment Lead to manage their own account. That setting tells Bevy to prefer this chapter’s own seller account for ticket revenue (once Stripe is connected) instead of forcing everything through the HQ account.
6. Set Currency to the currency this chapter will use for ticket sales and payouts. Choose carefully — paid events inherit chapter currency when they are created, and unsupported currencies can block paid ticketing.
7. Select Save (or your chapter’s save control) so the payment lead, Bevy Pay account setting, and currency are stored together.

Connect Stripe as the payment lead

After HQ designates the payment lead and sets Bevy Pay account to allow the chapter’s own account, the payment lead must finish Stripe setup before paid ticket revenue can settle to that chapter seller account.

Only the designated payment lead sees and can use Start selling / Manage seller info / Payment dashboard for the chapter seller connection. Sign in as that person before you continue.

1. Sign in to Bevy as the payment lead (the same person selected under Payment lead).
2. Open that chapter’s Chapter Dashboard → Settings → Payments.
3. Confirm you still see yourself listed as Payment lead and that Bevy Pay account is set to Allow Payment Lead to manage their own account. If either is wrong, ask an HQ admin to fix the designation settings first.
4. Select Start selling. Bevy opens Stripe’s onboarding flow (often in a new browser tab or window).
5. In Stripe, create a new account or sign in to an existing one. Complete every required screen: business or individual details, identity verification, tax information, and the bank account that should receive payouts.
6. When Stripe says you are done, return to the Bevy Payments tab and refresh the page if the new buttons do not appear yet.
7. Confirm you can see Payment dashboard and Manage seller info. Those controls mean Bevy has a chapter seller account linked for this chapter.

If setup is only partly finished — for example Stripe still needs more information — select Manage seller info to reopen onboarding and complete the remaining Stripe steps before you sell paid tickets. Do not assume ticket charges will succeed until Stripe onboarding is complete enough for the seller account to accept charges.

Manage the chapter Stripe account

After the seller account is linked, use the Payments tab controls for ongoing money work. Attendee payment status still shows in Bevy on the event Registrations list; bank transfers, seller profile changes, and most dispute work happen in Stripe.

What to expect after a successful paid registration:

• The charge appears in Bevy as a paid registration (and in Stripe as a payment on the chapter seller account).
• Available funds in Stripe usually become ready for bank payout on Stripe’s rolling schedule — often about 2–3 business days after a successful charge, depending on Stripe, the country, and the bank. Exact timing is controlled in Stripe, not in Bevy.
• The payment lead uses Payment dashboard to check balances, payout history, and any Stripe alerts that need attention.

Change the payment lead

You change the payment lead in the same chapter Payments settings — you do not need Bevy Support for a routine handoff. The important detail is how the existing Stripe seller account behaves.

Bevy stores the connected seller account on the chapter, not as a personal preference that automatically moves with the new lead. If you change the Payment lead while a seller account is still connected, Bevy warns you: further sales can continue to pay out to the existing Stripe account until someone disconnects it. Plan the handoff on purpose.

Recommended handoff when the new lead will use a different Stripe account

1. Open the chapter’s Chapter Dashboard → Settings → Payments.
2. Confirm whether Payment dashboard / Manage seller info / Disconnect seller are visible. If a seller account is connected and should stop receiving chapter sales, continue with disconnect.
3. Select Disconnect seller.
4. Read the confirmation carefully. Disconnecting removes the seller link in Bevy and cannot be undone. Confirm only when you intend to stop using that Stripe account for this chapter’s Bevy Pay sales.
5. Under Payment lead, choose the new chapter team member.
6. Confirm Bevy Pay account is still Allow Payment Lead to manage their own account (unless you are intentionally switching this chapter to HQ-only).
7. Save the chapter payment settings.
8. Ask the new payment lead to sign in, open Settings → Payments, and select Start selling to connect their Stripe account. They should finish onboarding until Payment dashboard and Manage seller info appear.

If you must change the lead but keep the same connected Stripe account for now

1. Open Settings → Payments.
2. Change Payment lead to the new team member.
3. Save. When Bevy shows the payment-lead change warning, read it, then choose Save anyway only if you understand that sales will keep paying out to the existing connected account.
4. Give the new payment lead access to that Stripe account outside Bevy if they need to manage payouts and disputes there. In Bevy, they become the person who can open Payment dashboard and Manage seller info once they are the designated lead.

If Payment lead is read-only, or you do not see Disconnect seller when you need it, ask an HQ admin with payment permissions, or contact Bevy Support / your Customer Success Manager.

Run paid events after chapter-level setup

After the payment lead’s Stripe account is connected and Bevy Pay account allows the chapter’s own account, organizers create paid events the same way they always do. The difference is where the money settles.

• Where ticket revenue goes — With Allow Payment Lead to manage their own account and a completed chapter seller connection, paid Bevy Pay ticket revenue for that chapter’s events settles to the chapter’s connected Stripe account. With Only use HQ account, revenue for that chapter routes to the community HQ Stripe account instead.
• What organizers see in Bevy — Attendee payment status still appears on the event Registrations list. Organizers manage check-in and registrations in Bevy as usual.
• How to refund — Prefer Refund total order on Registrations so Bevy and Stripe stay aligned. Do not use Delete to reverse a paid Bevy Pay order. Step-by-step: Refund a paid ticket. Concepts and common errors (insufficient funds, Stripe-only refund still showing paid, 180-day window): Managing paid events: payouts, refunds, and deleting attendees.
• Who to contact for problems — Use Stripe support for failed bank payouts, Stripe Dashboard errors, identity verification, and chargebacks on the chapter seller account. Use Bevy Support or your Customer Success Manager when the problem is enablement, permissions, missing Payments controls, or a Registrations list that no longer matches Stripe after a refund.