Require payment method if booking could produce additional costs

The product feature require payment method if booking could produce additional costs makes ioki Platform require a payment method for bookings that start at no cost but can still create charges later.

This feature only has an effect when payment for rides is enabled for the product. It applies wherever a passenger books, including ioki Web Booking.

• If the booking price is greater than zero, a payment method is already required during booking.
• This feature extends that behavior to some bookings with an initial booking price of zero.

A zero-price booking can still require a payment method when:

• the product uses passenger update after booking (passenger) and a later passenger change could increase the booking price
• the product uses passenger update after booking (driver) and a driver-side passenger change could increase the booking price
• the fare setup can later charge fees, such as cancellation, early cancellation, quick cancellation, late cancellation, or no-show fees

Use this feature when a booking might still become chargeable after it has been created and you want a payment method to be available from the start.

Scope and limitations

• If payment is disabled for the product, this feature has no effect.
• Enabling this feature does not charge the user by itself. It only requires a payment method during booking when later costs are possible.
• This feature does not guarantee that every allowed payment method can settle a later fee. For example, a cancellation fee or no-show fee cannot be collected in cash, because cash is collected in person and the passenger is not in the vehicle when the fee is due. In that case the fee becomes an outstanding failed payment instead.

Activate this feature

Roles: Super Admin

1. Navigate to the management settings of the product.
2. Within the Product features section, select the checkbox Require payment method if booking could produce additional costs.
3. Select Save.