LIBRERIDE · PLATFORM POLICIES
Fares, payment authorization & receipts
Review the amount
The booking screen is the place to review the actual fare and trip conditions. This page creates no fare table or new fee. Any toll or additional charge needs an amount or calculation method disclosed before charging, with any required authorization. Do not assume a future fee mentioned here is currently charged.
Payment authorization
The native Rider app can authorize the displayed ride amount before a request is released, then capture the fare when the trip completes. Browser booking may instead use a hosted checkout. Opening a payment screen alone does not confirm a payment or ride. Your bank may require verification.
Tips and other amounts
A tip is optional and its amount must be chosen and confirmed. It may be charged separately and require bank verification. The current flow has no separate cancellation or no-show fee. Any subscription or unrelated future payment needs separate terms and authorization.
Changes to a booked route
Review the route and amount shown before confirming a change. The current route-edit flow can keep the booked fare unchanged and requires acceptance of that unchanged fare. A higher-cost edit may require additional authorization and may be unavailable. A shorter route does not automatically recalculate the booked fare.
Payment details and receipts
Stripe collects card details through its payment form or hosted checkout; LibreRide uses payment references rather than full card details. Payment confirmation and receipts depend on backend/provider verification. Review confirmed fare, tip, and total in the receipt. If a receipt is missing or inaccurate, contact support with the trip reference.
Holds, disputes and refunds
Pending holds and completed charges are different. See refunds and billing review for canceled rides, duplicate amounts, unrecognized charges, and approved refunds. The invited beta does not imply public live-payment availability.