Origin
Court 02 booking
The payment row names the booking, time, surface, and member.
Payments
An operator asks why Stripe paid out less than expected and needs the trail by record.
Stripe payments where the booking lives.
Lobby shows payment links, paid state, failed payments, refunds, and payout reconciliation beside the reservation, class, or membership. Lobby does not take a booking percentage.
Money trail
A payment row is useful only when it names the record that created it.
Booking, class, membership, refund, Stripe reference, and payout batch sit in one trail staff can read top to bottom.
Stripe
pi_3N7...
Processor reference remains visible without exposing card data.
Payout batch
Mon 19 May
The record can be reconciled when Stripe pays out.
Confirmation path
An unpaid hold gives the court back. A paid one keeps it.
Checkout starts, the payment lands, the hold confirms. An abandoned checkout releases the slot on its own.
Refund path
Refunds need booking context, not just Stripe context.
Cancellation windows, staff notes, the original payment, and the refund stay tied to the booking or class.
Cancel window
Refund allowed
The refund path starts from the booking cancellation rule.
Original record
Context retained
The refund points back to court, member, date, and payment.
Report update
Finance sees net
Refund state carries into payout and report views.
Payout reconciliation
A payout breaks down into gross, fees, refunds, and Lobby’s cut.
Stripe fees show on their own line. Lobby booking commission shows as €0.00. No export needed to prove either.
Payments handoffs
Every payment traces back to the booking that created it.
Payments demo
Bring the real workflow.
Test the real week.
Illustrative club data. The payments story follows money from the booking or class that took it, through Stripe, refund, and payout.