Skip to main content

Implementation Status - August 14, 2025

Ready for testing​

  • Ready for testing by Deb.
  • Old WordPress system is still source of truth for now, we are just testing the new system with data migrated at 3:19pm EST on August 14, 2025
  • When we are ready to launch the new system, we will clear the new system's data and replace it with the latest data from the old WordPress system, at which point we no longer use the old system, we only use the new system

Questions​

  1. Where do boot rentals go in the breakdown for WY Department of Revenue?
  2. Gratuity: I configured gratuity to be set to 18% when there are 6 or more guests. Should it be set to something when there are less than 6 guests? Do you want gratuity % to be something the guests can enter themselves?
  3. I've integrated the payment system using the Fluidpay sandbox account I was provided. It is working well but no real money is being transferred. You told me you want to turn on the new system at the same time as you start taking in person payments with your new Fluidpay. Do you have a timeline for that?
  4. Do you want to be able to make a credit card payment for someone or we keep the button disabled when you view the reservation?
  5. When migrating old data I set all youth and children based on their birthdates in the rider form, and set all others (no birthdate) as adult, that means someone who was actually a child but never had a birthday added for them might incorrectly be shown as an adult
  6. Credit card fee: Do we never charge it on the first payment/down payment, and do we only charge it on the second payment/balance payment when the credit card fee percentage has been set for that reservation?
  7. When migrating the reservations from the old system, is it ok that I exclude unconfirmed ones? This is just to help prevent importing incomplete bookings (38% of the WordPress reservations are unconfirmed) and it gives us more clean data to start with. We could ensure that you have had the time to confirm all reservations you want to preserve before we launch the new system for real. Also, do you want me to offer an option to delete a reservation and its request for the new system going forward?
  8. When someone submits a reservation request they can add an email address for the other adult(s), and this creates an account allowing those other adults to login and complete their rider form (I didn't show this part in the video, but it is there and you can test it if you want). When you send the "reservation confirmed" email to the billing contact, do you want us to automatically send those other adult guests an email telling them they can login to complete their rider form for the reservation they are a guest in?

Deployment steps to remember​

  • Update FluidPay API environment variable to use prod instead of sandbox

Git commits​

A PDF of all git commits made since the last update up until today's update is available here (871 pages).