This week, we have resolved some issues with our Passenger Web App (PWA) and our Online Reservation System (ORES).
Every week we are working on releasing improvements and bug fixes across Limo Anywhere and our products to help your business succeed. Please see below for further information on our release this week, and stay tuned each week to see what else we are bringing to help you and your business.
Bug Fixes
- Resolved an issue with our Passenger Web App (PWA) getting an “Authentication Failure” error in some cases
We have resolved an issue where PWA was giving an authentication error when a user was trying to add anew credit card to their account or book a reservation with a new credit card on LA PAY.
Now users should be able to book on PWA with LA PAY with new or stored credit cards without authentication errors.
- Resolved an issue where Credit Card fields were showing on ORES in some cases when the fields weren’t required or applicable
We have resolved an issue where the fields to enter new credit card information appeared after selecting an existing credit card from the stored payment method drop down list or selecting non-Credit Card payment method (if applicable), and completing CAPTCHA on ORES.
The issue has been resolved, so if users choose an existing credit card and fill out CAPTCHA, they will be able to complete the booking by clicking the “Submit” button. If an existing credit card is selected from the drop down list on the Step 3 of ORES, the fields to enter a new credit card will not be displayed or required.
Also if they select a non-Credit Card payment method (if applicable), then the fields to enter a new credit card will NOT be displayed or required if ORES setting “Require Credit Card on All Reservations (Except Direct Bill):” is set to “No”.
If ORES setting “Require Credit Card on All Reservations (Except Direct Bill): is set to “Yes”, then the fields to enter a new credit card will be displayed or required.
- Resolved an issue with ORES continuously spinning when a user logged into an account on Step 3 in some cases
We have resolved an issue where a user logging into their account on the Step 3 of the booking process on ORES would experience an infinite spinner on the page.
The issue has been resolved, so users should have no issues with the page spinning regardless of if they logged into their account on Step 1, or Step 3 of the booking process on ORES.