Clear operating rules before the night starts.

Pricing

Fees should be visible before anyone pays.

Event tickets and service bookings use server-calculated totals. The cart can show subtotal, platform fee, and estimated total before checkout starts.

• Ticket and service prices come from the live event or service listing.
• Host and provider plan fees are managed in Studio and are not trusted from the browser.
• Taxes, Radar decisions, and final payment-provider settings require Stripe-side proof before they are called launch-final.

Refunds

Refunds are handled through the original payment path.

Refund tooling exists for eligible orders, but approval still depends on the event, host, payment state, and gateway availability.

• Refund requests must be tied to the buyer's own order.
• Approved refunds go back through Stripe to the original payment method when the gateway is available.
• Event-specific refund rules need owner-reviewed policy wording before they are treated as final public terms.

Payouts

Money movement stays gated until provider evidence exists.

Hosts and service providers can connect payout workflows through Studio, but live payout readiness depends on Stripe Connect, KYC, account state, and settlement evidence.

• Projected earnings and promoter revenue share are not payout promises.
• Provider bookings require a payable provider account before checkout can proceed.
• Bank settlement, Tax, Radar, KYC, and payout-balance evidence remain owner-gated.

Media

Gallery visibility follows the event and gallery privacy mode.

Public galleries are intended for published public events. Unlisted and private gallery access is guarded by ownership or super-admin checks.

• Signed upload, signed read, manifest, and ZIP paths are source-backed.
• Protected grant headers, real bucket objects, expiry behavior, and native save proof still need authorized media checks.
• Do not upload private or sensitive media unless the event owner has approved the intended visibility.

Support

Event-specific issues start with the event owner.

For a ticket, refund, door, listing, booking, or gallery issue, the fastest path is usually the host or provider who controls that record.

• Platform support can help route account, payment, listing, and access problems.
• Role and permission checks protect host, provider, promoter, buyer, manager, and admin workspaces.
• Production claims are only upgraded when source, deployed revision, runtime behavior, and real operator evidence all line up.