Integrations

• Vehicle device provider. Connect the service that controls physical vehicle release and return. Bring the provider’s event references and actual event times into ride evidence, and agree how staff retrieve delayed receipts.
• Payment provider. Connect authorization, capture, refund and void evidence to the correct booking. Preserve event identity and provider reference, verify the event through the agreed procedure and keep repeated deliveries from duplicating payment reporting.
• Customer entitlement and consent. Arrange the source used to confirm a customer’s eligibility and required consent before booking confirmation. Decide what staff must inspect and how evidence is attached to the booking.

App Administrator establishes the organization, resource and team scope. During setup, authorize each connection through the selected provider’s access controls. Booking Supervisor agrees what counts as sufficient evidence for a confirmation or completion decision. Keep provider credentials in the approved connection setup and retain references in the operating record.

Rehearse late delivery, repeated delivery and an event that belongs to a different vehicle or booking. A provider request acknowledgment must be followed through to the physical or financial event it represents. When the evidence remains uncertain, retain the discrepancy for operational review.

Agree the handling of USD booking, fare and payment amounts before connecting a provider that uses another currency. Test the selected rule using a real provider event in the approved rehearsal environment. Use Reconciliation and payment to define the follow-up procedure.