Integrations

• Rider booking channels. Configure your booking intake to identify the rider’s pickup and dropoff and prepare the appropriate booking and request. Agree how a change or cancellation refers to the original journey.
• Driver and partner channels. Connect accepted match messages to the intended booking, driver and vehicle. Check availability again before confirming the resource, and keep an unresolved match available for review.
• Telematics and trip events. Configure the event source, observed time and booking reference before importing location or progress observations. Review delayed and repeated messages during the pilot.
• Fare and payment providers. Bring approved fare components and payment evidence from the selected providers. Preserve the provider event identifier, amount and currency so Finance Operator can explain each recorded state.
• Fleet service records. Agree how external inspection and maintenance evidence reaches Fleet Coordinator. Match vehicle identifiers and units before loading condition or fuel information.
• Document storage. Decide where ride vouchers, signatures and fare breakdowns are retained. Test attachment and document-link access with the staff who need to review the evidence.

Assign an owner to each connection and agree which source supplies each fact. A driver event establishes an observation, while a payment event supports a payment outcome. Keep those responsibilities visible when investigating inconsistent records.

Admin configures access with the operating owners. Rehearse duplicate messages, changed source details and a booking reference that cannot be resolved. Agree whether the event is held for investigation or corrected before it reaches the operating records. Keep credentials in the configured connection and limit access to rider and payment details.

Follow implementation and the data model before enabling a live feed.