Journey states
The label changes only when the journey does.
A request can be reviewed, sent, waiting, offered, expired, confirmed or unavailable. Each change needs an authoritative event—not a timer, optimistic animation or moving pin.
State by state
No invented movement.
Draft
The journey is being shaped; nothing has left the page.
Requested
The authorised service acknowledged the exact request.
Waiting
No bid or confirmation yet; expiry and retry remain visible.
Offered
A real operator response, terms and validity window are attached.
Confirmed
The accepted offer and provider reference are durable.
Expired or unavailable
No booking is implied; the route remains recoverable.
Contact and privacy
Driver contact is part of the confirmation—not decoration.
When can a customer see driver details?
Only when the verified provider returns the authorised contact state for the confirmed journey.
Can the page show nearby drivers?
Not without real licensed availability and permission to expose it. A decorative moving pin would be false.
What if a request expires?
Keep the route, show that nothing is booked and offer a safe retry or alternative contact route.
When is payment taken?
Only inside an explicitly connected payment journey with amount, currency, payee and confirmed outcome in view.