Paid tickets on Faby

What ticketing supports

Paid experiences use ticket types as the inventory source of truth. The simple host flow still stays simple: mark the experience as paid, enter a price, enter capacity, and publish. Behind the scenes, Faby creates a default Regular ticket type with that price and capacity.

• Free experiences show Free.
• Paid experiences with one active ticket type show the exact price.
• Paid experiences with multiple active ticket types show Starts from $X.
• Guest checkout uses Faby's quote model first, then Stripe Checkout for payment collection.

Creating a paid experience

1. Open the experience creation or edit flow.
2. Choose a paid pricing option.
3. Enter the guest price and capacity.
4. Publish once the rest of the experience details are ready.

Managing ticket types

Hosts manage advanced inventory from the host experience page under Tickets & discounts. This is where Regular, VIP, early bird, or other ticket tiers live.

• Ticket name: the label guests see when choosing a ticket.
• What guests pay: the checkout price for this ticket type.
• What you get: a host-net estimate after Faby and Stripe fees. The final order quote is the source of truth.
• Total available: blank means unlimited. You can increase capacity later, but not below tickets already sold.
• Description: optional guest-facing context, such as what is included in a VIP ticket.
• Enable ticket: disabled tickets are hidden from guest checkout but stay visible to the host.

How guests buy

1. Open the paid experience.
2. Select an available ticket type when more than one exists.
3. Add one discount code if they have one.
4. Review ticket price, Faby fee, discount, tax if applicable, and total.
5. Continue to Stripe Checkout and complete payment.
6. Return to Faby, where the payment banner verifies the actual order state.

Discounts

Faby supports one discount code per order. Codes can be percent-off, fixed-amount-off, or a Faby-fee waiver. Discounts are applied before Stripe Checkout opens and are preserved on the quote and order.

• Codes can have redemption limits.
• No stacking: one code per order.
• Faby-funded promotions do not reduce host payout.
• Host-funded promotions reduce host net when that funding mode is enabled.

Refunds and removals

Every paid experience has a refund policy. The current product supports non-refundable tickets and tickets refundable until 24 hours before the experience. Requests outside the policy window go to admin review.

• Buyers can cancel unpaid checkout sessions without a charge.
• Approved refunds are processed through Stripe.
• Paid attendees are removed through Refund & Remove, not a casual remove action.
• Refunds create audit events and ledger entries for support and reconciliation.

Payouts

Hosts are paid through Stripe Connect Express. Faby charges the guest, snapshots the order economics, and releases host payout after the experience and required safety checks.

• Hosts set up payouts in Faby settings under Hosting, then Payouts.
• The first payout is delayed by Stripe's first-payout reserve.
• At MVP, finance releases eligible payouts manually from the admin tools.
• Admin payment views include order status, Stripe references, timeline, ledger, and notes.

Sandbox testing

Internal testers can use Faby's sandbox payment mode from an allowed test account. Sandbox checkout uses Stripe test mode and does not charge a real card.

Not supported in this release

These are intentional gaps in the current Faby implementation, not hidden settings:

• No cash or card-at-the-door ticket sales inside Faby.
• No ticket transfer or third-party resale flow.
• No Apple Wallet pass or QR-code check-in surface yet.
• No per-ticket max-per-person setting yet.
• No shopping cart across unrelated experiences.

If you need help with a paid ticket order, email support@getfaby.com.