Release 5.113

November 5, 2026

Vasto 5.113 introduces a major new enrolment experience alongside Stripe payments, giving you more flexibility over how students enrol and pay. This release also includes a substantial refresh of several administrative list views and the Certificate Queue, plus improvements to partner lodgements, funded enrolment visibility, booking information and payment security. A smaller set of targeted bug fixes rounds out the release, including updates to RPL handling and dashboard accuracy.

New Features

• Separated the field for SA SACE ID from the Purchasing Contract section in the funded information for enrolments.
• We have built a new enrolment form experience. This opt-in feature lets you customise more about the Vasto enrolment form than ever before and have different journeys for different courses and individual timetables.
• We have added an integration with Stripe for taking payments for your enrolments.

Improvements

• Added a section for “linked invoices” to the booking editor page.
• Added an alert when timetables that are part of a group are not / no longer published, preventing enrolment in them.
• The Advanced Student Editor button in the person profile page now turns orange if it’s a funded enrolment.
• Updated the look and functionality of the certificate queue to provide a consistent experience. You can now also un-ignore certificates in bulk.
• We’ve had a major overhaul of a lot of the “list” pages in Vasto to make use of the new component library.
• Updated the partner lodgement process to show the history of lodgements to the training partner as well as the admin users.
• Made some security upgrades to cut down on fraudulent credit card payment attempts.
• Added a warning for admin users overriding unit statuses where there are incomplete activities.
• Fixed an issue with Skills lists containing %0A and %0D characters.

Bug Fixes

• Updated RPL claims to look at the unit in a student’s enrolment, taking upgrades into account, rather than the one in the course.
• Fixed an issue where admin user counts were showing higher than the number of admins associated with an account.