Payment Methods
In our Passenger App, we offer various payment methods, so you can charge your customers in the way you prefer.
PayInTaxi
This method allows your passengers to pay in cash for their taxi ride. This can be used in conjunction with one of the payment methods listed below. You can enable or disable this option at any time. Depending on what payment method you configure, the passenger is presented with the option of 'Cash' at the applicable time during their journey (either during booking or at the end). This also allows your passengers to pay with cash if their card payment fails/does not have enough funds.
To configure your passenger app for PayInTaxi:
- In AppSettings, click on the Passenger App 5G tab and open the Payment section.
- Here there are two options related to PayInTax:
- Can Pay Cash: Toggle on or off to enable or disable allowing the use of cash payments from passengers booking with your app.
-
Pay In Taxi Description: Enter a description of your PayInTaxi option that appears within the Cash option button in your passenger app, for example, "Pay with Cash".
The following options require your passengers to use a card and for you to be set up with a card provider. As these settings are Engineer Only, you must contact Platform Delivery (platform.delivery@autocab.com) to configure these settings for you.
PayOnBooking
When a passenger books a journey, they pay the quoted fare upfront. If the payment fails, the app will not allow the booking to be made. To ensure passengers aren't charged twice, the system ignores what the driver shouts back at the end of the journey. This payment method is most suitable for fixed fares. It uses Address, Postcode, CV2, and 3D Secure to safeguard transactions against chargebacks.
The following card providers support this payment type:
- SagePay (Opayo)
- JudoPay
- PayPal
- myPOS
- EBizCharge
- PayU
PayAtEnd3DS
Pay At End 3DS (3D Secure) is a feature that lets passengers pay the exact fare amount at the end of their journey. This eliminates the need for any authorisation holds on a passenger's payment card, and they don't have to wait to be reimbursed for any held charges.
Once the journey is complete, the driver can swipe the 'Authorise Payment' button, which will then prompt the passenger app to notify the passenger to pay for the booking. The app will display a payment screen, where the passenger can pay for the booking via a 3DS payment.
If the passenger is not on the app, they will receive a 'Payment required' push notification. Tapping on this notification will take them to the in-app payment screen, where they can complete the payment.
For security and chargeback prevention, this method uses 3D Secure.
The following card providers support this payment type:
- SagePay (Opayo)
- JudoPay
- PayPal
With PayAtEnd you can implement tipping on your passenger app, for more info, see the Tipping section of this article. However, cancellation fees cannot be used with PayAtEnd3DS since no money is held.
ChargeAtEnd
This payment method involves charging the passenger's card once the journey has ended.
At the time of booking, a 3D Secure challenge is initiated with a pre-authorisation buffer, which does not check the card for sufficient balance and hence, no hold is placed on the balance. The final fare is automatically deducted when the booking is completed. If the fare amount exceeds the pre-authorised amount, the transaction will fail, and the driver will need to collect the full fare amount from the passenger.
Only SagePay supports this payment type.
Deferred
The Deferred method allows you to reserve the quoted fare at the time of booking onto the passenger's card, with an additional amount as per your pre-authorisation rules.
When the driver shouts back the fare, the amount is deducted from the reserved pot. If there is not enough money in the pot, the payment will be declined. In this case, the driver is informed to request an alternative payment method, and the reserved amount is returned to the passenger. Any excess amount in the reserves after the transaction is successfully completed is returned. This usually happens instantly, but in some cases, it may take a few days.
To ensure a secure transaction and prevent chargebacks, this payment method supports the use of Address, Postcode, CV2, and 3D Secure.
The following card providers support this payment type:
- SagePay (Opayo)
- JudoPay
- EBizCharge
- PayU
Payment Extras
Depending on your payment method, you can use extras on the passenger app such as tipping and cancellation fees.
Tipping
Currently, the only payment method that supports tipping is PayAtEnd3DS. 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, 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)
Unfortunately, other providers do not support cancellation fees. We do not recommend setting up cancellation fees if using a provider other than JudoPay or SagePay.
To configure cancellation fees, refer to How to configure cancellation fees.