Release notes: Core platform v3.4.1 (22 September 2026)

22 September 2026 (646be64)

Version 3.4.1 is a small maintenance release on the 3.4 line, covering changes since v3.4.0. It contains one fix for card payments that need a 3D Secure check, and one internal improvement to how database changes are rehearsed before each release. There are no database migrations in this release.

B2C Booking Portal

Payments and refunds

Card payments that need a 3D Secure check no longer stall on the loading screen

Jira: V3-381 | FD: 6054

Issue

Some customers paying by card through Opayo (SagePay) were left on the payment loading screen after their bank had approved the 3D Secure check, so their booking did not complete. Payments that did not need a 3D Secure check were not affected, which made the problem appear intermittent.

Fix

After the 3D Secure check, customers are now returned to the booking portal and the payment continues through to confirmation. This also applies to additional payments taken when a customer amends a booking.

Testing

1. On the booking portal, book tickets as a guest and pay with a test card that triggers a 3D Secure check.

2. Complete the 3D Secure check. The booking should go straight to the confirmation page, with the booking reference shown, and should not stall on the loading screen.

3. Repeat while signed in to a customer account. The result should be the same.

4. Amend an existing booking so that an extra payment is due, and pay with a card that triggers a 3D Secure check. The amendment should save and the payment should complete without stalling.

5. Amend a booking so that a refund is due, and separately cancel a booking. Both should complete without errors, and the refund should show against the order.

Infrastructure

Release rehearsals now cover database changes that run after deployment

Jira: DEVOPS-659

Need

Some database changes run after a new version has been deployed, and can take a long time to complete. Our pre-release rehearsal of database changes did not include these.

Change

The rehearsal now includes database changes that run after deployment, and records how long each step takes, so they can be checked before a release goes live. There is no change to day-to-day use.