Sprint 10 Notes

Key Defects:

The following key defects have been addressed as part of this Sprint:

New Joiners - Money Taken - no membership created

Reported cases where customers sign up online, see payments taken, but receive no confirmation and no membership is created.

• We found payments were authorised (checkout was completed) but not captured, meaning no money was actually taken.
• The memberships did not get created as the process stopped before final confirmation.
• We have added monitoring to track this while we continue investigating the cause.

• Identified an issue where membership renewals could fail or charge incorrect fees if processed at the boundary between dates due to timezone differences. This is now corrected to ensure renewals happen reliably.
• Reported cases when clicking on ‘Bookings’ and selecting an activity they staff are met with an error message.
• Reported cases that an issue was presented when locating customer records after a card is scanned

Opayo Payment Form Duplicate Submissions

A fix was released to resolve an issue on the Opayo payment form where using the browser's back and forward buttons was causing duplicate payment submissions.

What was happening:

• Each time the payment page loaded, it added a new "listener" to process payment responses.
• Using the back/forward buttons did not clear these listeners, so multiple listeners were triggered on a single payment attempt.
• This caused multiple submissions and API errors, like having several cashiers trying to process the same payment simultaneously.

The fix ensures duplicate listeners are cleared correctly, preventing multiple submissions and ensuring a stable payment process for your customers.

Key Defects - Activities V2:

The following key defects regarding Activities V2 where addressed as part of this Sprint:

• Reported cases that adding recurring sessions to existing bookings was not working. We confirmed this and prioritised a fix to ensure you can manage long-term schedules without needing to recreate bookings.
• When editing a recurrence on a draft schedule in V2, BOH staff would get a ‘dropped the ball’ error message instead of being able to open the recurrence.
• An error message would show up when changing the end date of schedule.
• Mid Devon reported an issue where the V2 Activity Utilisation data source came up blank.
• Editing the recurrence dates would come up with an error message preventing users from publishing those changes.
• An issue where activities were not shown as bookable even though they existed and should be available.

Key Enhancement:

A security enhancement whereby staff members must now enter the customer’s UUID into the URL instead of the ID to view a customers profile.