We offer various payment types and providers allowing you to charge your customers for their journeys in the way you prefer.
Terminology
For the definitions of the payment types we offer, see the list below:
In-App Payments - Payments that are processed via the app backend, for E-Booker and Passenger App Payments.
Autocab 365 Payments - Payments that are processed directly through Autocab 365/Ghost for passenger payments via the phone or SMS, in-car payments or driver rent payments.
Deferred Payments - Deferred payments involving reserving or 'pre-authorising' (pre-auth) an amount on the customer's payment method at the time of booking. The payment is held in the passenger's account to ensure the funds are available. Once the journey is completed, the final amount is captured and the payment is processed. Any difference is returned to the customer.
Fares set using this method can set a price range to be shown to the passenger.
Incremental Authorisation - Incremental authorisation is built on top of deferred payments. It allows the authorised amount to be increased if the expected journey fare increases. This ensures that the final payment can cover the increase without needing to void and create a new transaction.
PayOnBooking - PayOnBooking means that the customer is charged immediately when they make a booking or reservation. This ensures that the business receives payment upfront, securing the transaction at the time of booking. No amendments can be made to the transaction and a new one must be created for any additional payment.
ChargeAtEnd - This involves a 3D Secure Challenge with a pre-authorised buffer applied at the time of booking. Unlike deferred payments, no verification is made to check if the card has sufficient funds nor is a hold placed on the account. The final fare is automatically charged once the journey is completed. However, if the final fare exceeds the pre-authorised buffer, the transaction fails and the passenger will need to pay the full amount directly to the driver.
PayAtEnd3DS - Pay At End 3DS involves no checks at the time of booking. When the driver swipes to 'authorise payment' at the end of the booking, the system notifies the user to pay for the booking. This brings up a screen for the passenger to complete the payment, which includes a 3D Secure (3DS) verification step.
Pay On Complete - This is deprecated. A pre-authorisation for £1.01 is applied at the time of booking, placing a hold of £1.01 on the card. This hold is immediately voided, although it may take a few days for the funds to be released. The final fare is charged using a 'Merchant-Initiated Transaction' (MIT), a mechanism no longer supported by our payment providers, who advise against its use.
Note: PayOnComplete is not compatible with countries that have mandatory 3D secure requirements.
Payment Types & Providers
Below are tables highlighting the payment types and the providers that support or do not support them. This is separated into UK, EU & International and F10 Payments in Booking & Dispatch.
In App Payments (UK)
| Payment Type | Judopay | Sagepay | Stripe |
| Deferred Payment | |||
| Incremental Authorisations | |||
| PayOnBooking | |||
| ChargeAtEnd | |||
| PayAtEnd3DS | |||
| Google Pay | |||
| Apple Pay |
In App Payments (EU and International)
| Payment Type | Judopay | Sagepay | Stripe | EBiz Charge | PayU | myPOS |
| Deferred Payment | ||||||
| Incremental Authorisations | ||||||
| PayOnBooking | ||||||
| ChargeAtEnd | ||||||
| PayAtEnd3DS | ||||||
| Pay On Complete | ||||||
| Google Pay | ||||||
| Apple Pay |
F10 Payments - Payments made from Booking & Dispatch (Easypay)
| Method | Judopay | Sagepay | Stripe | EBiz Charge | PayU |
| Authorise | |||||
| Payment | |||||
| Pay By Link |
Authorise (Deferred) - A transaction where funds are reserved but not immediately captured. The payment must be manually processed later using Easypay dockets.
Payment - The customer pays the full fare at the time of booking, typically for a fixed-fare journey.
Pay By Link - A payment method where a link is sent via SMS to the customer's mobile. It allows them to pay, but in cases of variable fares, the amount captured may not cover the entire journey cost.
Payment Extras
Depending on your payment method, you can use extras such as tipping and cancellation fees.
Tipping
Currently, only the PayAtEnd3DS payment method permits tipping. Tipping allows your passengers to give their driver a predefined tip (based on your AppSettings configuration) or a custom amount. For further information on how to configure this feature, see Payment (Passenger App 5G). Or to see how your passengers would tip, see Tipping Your Driver.
Note: To use tipping on PayAtEnd3DS, you must be on Passenger App version 34.3 or above.
Cancellation Fees
Cancellation fees are designed to compensate your drivers for this loss and also encourage passengers to avoid booking rides they do not intend to take.
Passengers can be charged a cancellation fee if they cancel a credit card booking after the driver has been dispatched. When trying to cancel a booking a warning message is displayed informing the passenger of potential cancellation fees and the reason.
Cancellation fees are not available with the PayAtEnd3DS method as no funds are held on the card when booking.
Currently, the credit card providers that support cancellation fees are the following:
- JudoPay
- SagePay (Opayo)
- Stripe
Unfortunately, other providers do not support cancellation fees. We do not recommend setting up cancellation fees if using a provider other than JudoPay, SagePay or Stripe.
To configure cancellation fees, refer to How to configure cancellation fees.