Start with the service you already agreed
A direct-customer chauffeur payment normally begins after the passenger and provider have already agreed the transport service and fare. The payment workflow should record that agreement rather than create or redefine it.
That distinction matters. Payment technology can help present and collect the amount, but the provider still owns the customer relationship and remains responsible for the transport service.
Give the passenger a clear payment request
A professional payment request should make it easy for the passenger to understand who is requesting payment, what the agreed service relates to and what complete amount will be authorised.
Avoid sending disconnected amounts with no useful reference. Passenger, journey and fare context make later reconciliation much easier.
Use supported payment rails
Card acceptance depends on the provider's payment account, applicable payment-provider requirements and the payment methods available in the relevant market.
UbiLimo publishes payment-method readiness separately so providers can distinguish supported, eligible, planned and coming-soon methods.
- Confirm your payment account is eligible.
- Use the supported UbiLimo payment flow.
- Check the complete amount before sending the request.
- Review the final payment state rather than assuming a payment attempt succeeded.
Keep transport and payment responsibilities separate
Receiving payment does not transfer responsibility for licensing, insurance, vehicle compliance, service delivery, tax or invoicing to the payment platform.
Those obligations remain with the independent provider according to the rules that apply to its own operation.