Charge attendees through Stripe when they book a paid event type — setup, refunds, payouts, and the fine print.
Technical Product Builder & AI Developer
Meeting payments let you charge attendees at the moment they book a paid event type. Payment is taken before the slot is confirmed — no payment, no booking — and funds settle directly into your Stripe account on your existing payout schedule. Tymeslot never holds your money.
Meeting payments are available to Pro plans on the managed cloud (tymeslot.app). To take payments you need:
The whole setup takes under five minutes once your Stripe account is verified.
Open Dashboard → Payments
You will see a Connect Stripe button. Click it to start Stripe's onboarding flow in a new tab.
Complete Stripe onboarding
Sign in to an existing Stripe account or create one. Stripe collects business and bank details directly — Tymeslot never sees them.
Pick your currency
Defaults to your Stripe account currency. You can change it once on the Payments dashboard. All paid event types use this currency.
Turn on payment on an event type
Edit any event type, tick Require payment , and set a price. Save — the next attendee pays through Stripe Checkout before the slot is confirmed.
One currency per host. Each event type carries its own price (whole units — €25, £40, $200, and so on).
Funds flow directly from the attendee to your Stripe account. Tymeslot is never in the middle.
Issue a refund from the Payments dashboard. Pick a payment, choose full or partial, confirm.
Both flows are designed to keep payment state in sync without surprises.
A small share of payments will, eventually, be disputed by the cardholder. Tymeslot surfaces the dispute and keeps you in the loop, but Stripe owns the resolution.
Two fees apply to every paid booking on the managed cloud:
MEETING_PAYMENTS_APPLICATION_FEE_BP
environment variable. See the self-host README for details.