ThrottleShare currently uses one standardized cancellation workflow. That keeps the payment action tied to the booking state instead of relying on owner-edited refund windows or pickup times the platform does not store.
Before the owner confirms
A pending booking may have a card authorization rather than a captured charge. Cancelling the request attempts to release that authorization before the booking is marked cancelled.
After confirmation, before pickup
A confirmed booking can still be cancelled by the owner or renter. If Stripe shows a captured payment, ThrottleShare attempts to create a full refund before recording the cancellation. If Stripe cannot create the refund, the booking remains unchanged and the person cancelling is directed to support.
After pickup is confirmed
Pickup confirmation moves the booking into its active state. Self-service cancellation is then closed. The owner or renter should stop using the vehicle when safety is involved, contact emergency services when needed, preserve photos and messages, and email [email protected] with the booking ID.
What owners still control
Owners control availability, price, renter requirements, delivery, deposits, allowed use, and the physical handoff. The standardized platform cancellation rule is separate from those listing controls.
What to include in a support request
- The booking ID and account email
- Who requested the cancellation and when
- The current pickup or return status
- Any Stripe error shown in the dashboard
- A short factual timeline, without card numbers or sensitive credentials
This guide describes the current platform workflow. It does not override applicable law, Stripe rules, or the ThrottleShare Terms of Service.