Payment provider status
Controlled payment workflow
RideShare is preparing live payment-provider integration for passenger payments and driver payouts. Until live settlement is enabled, payout records, platform fee calculations, payout readiness, admin decisions, notifications, and decision history are managed through a controlled platform workflow.
Passenger payments
Passengers will pay for accepted journey bookings through the app once live payment processing is enabled. Until then, payment records are handled through a controlled platform workflow while the payment provider integration is completed.
Platform fees
RideShare deducts a small platform fee from successful passenger payments. The remaining amount is treated as the driver payout value.
Driver payout requests
When a passenger payment succeeds, the driver payout amount becomes available for the driver to request. Once requested, the linked payment is locked to that payout request and cannot be requested again unless the payout is rejected or cancelled.
Admin payout review
Admin users review payout requests before marking them as processing, paid, rejected, or cancelled. Every admin payout decision is recorded in the payout decision history.
Processing payouts
Processing means an admin has started checking or preparing the payout. The driver is notified when the payout status changes.
Paid payouts
Paid means the payout has been completed or confirmed by admin. Once a payout is marked as paid, the linked passenger payments remain attached to that payout request.
Rejected payouts
A payout may be rejected if it should not be approved. Admin must provide a reason. Rejected payouts release the linked payments so the driver can request payout again later.
Cancelled payouts
A payout may be cancelled if it needs to be stopped before approval, for example because the payout amount needs recalculation. Admin must provide a reason. Cancelled payouts release the linked payments so the driver can request payout again later.
Refunds and disputes
Refunded, disputed, failed, cancelled, and unpaid bookings are excluded from payout readiness. This protects the platform and driver payout process from incorrect payout amounts.