

Showcase Events are general-purpose public pages for trainings, meetups, conferences, programs, and other virtual or physical experiences.
Choose online, in-person, or hybrid delivery, add the schedule and venue details, set registration dates and capacity, then publish when the page is ready.
A cover image becomes the Event link-preview image. When none is supplied, Showcase uses its default preview image.
Free registration is confirmed immediately while capacity is available.
Paid registration uses the shared Bachs checkout ledger. A seat and payment order are reused safely across retries. A signed successful-payment webhook is first stored durably, then Showcase fulfils the same purchase idempotently until the registration and ticket are verified for the purchaser.
Showcase collects paid Event checkout on the platform account. Paid checkout opens only when the Event owner has completed Bachs onboarding and the connected account has both transfers and payouts active.
The Event owner can invite Showcase Builders as admins or organizers. Invitations must be accepted before collaborator access becomes active.
Organizer membership and administrative changes remain auditable rather than relying on shared credentials.
The Event owner is the settlement recipient. Co-organizers do not automatically receive a revenue share and cannot redirect host payouts from the Event workspace.
The Event workspace shows confirmed registrations, checked-in guests, pending payments, paid-ticket counts, gross ticket sales, discounts, ticket classes, promo-code usage, organizers, announcements, check-in access and payout access in one place.
Open Workspace → Events → Payouts to start or continue payout setup, review transfers and payouts readiness, see ticket revenue settlements, settled and pending balances, choose a usable Bachs destination, preview a withdrawal, and review payout history.
Showcase creates a Bachs connected financial identity for the Event owner. Hosts do not need an existing Bachs account. Showcase opens Bachs hosted onboarding, where the host supplies whichever identity and payout details are currently required. Returning from that form triggers a status refresh, while Bachs capability events remain authoritative for activation.
For each successful paid ticket, Showcase snapshots the configured EVENT_PLATFORM_FEE_PERCENT, retains that platform share, and records the Event owner’s host share. Payment success alone cannot release host funds. The registration and ticket must first be durably fulfilled for the purchaser, then Bachs must report the original payment settled, and any EVENT_HOST_TRANSFER_HOLD_DAYS period must pass before the host share becomes eligible. Changing either configuration affects future settlement decisions, not the recorded fee split for earlier orders.
Every forward transfer, refund/dispute recovery, and re-credit has a stable idempotency key and is reconciled against the provider before another money movement can occur. Refund/dispute webhooks are stored durably even if they arrive before the payment settlement row exists, then replayed after payment reconciliation.
If a refund or dispute means the host has received more than the currently supported share, Showcase pauses new in-app Event withdrawals while the recovery is unresolved. If a dispute is later won or another adjustment reduces the loss, the same ledger can re-credit the host without double paying.
Showcase stores settlement and payout state, while Bachs remains authoritative for connected-account balances, destinations, transfers, payout processing, and terminal provider outcomes.
The private Event workspace shows registrations and payment state to authorized organizers.
Announcements can be published from the workspace and registered attendees receive a Showcase notification.
Browse Events · Your Events · Event payouts · Bachs hosted onboarding · Refund policy · Terms