Hawaii - Patch (22.28.2)
This Hawaii patch release resolves issues affecting pay-per-passenger payments, shared-unit pricing, and Booking Wizard payment details. It also improves cabin availability accuracy during booking and cancellation, helping teams avoid incorrect prices, payment schedules, and cabin status without manual correction.
Booking Wizard Deposit Details on Guest Statements (KT-15184)
Booking Wizard pay-per-pax creates leave itinerary deposit stamps blank (Guest Statement 0.00) Booking Wizard Payments Fixed Booking Wizard pay-per-passenger bookings so the itinerary deposit amount and final payment expected date are stamped on create, and Guest Statement shows those values instead of a 0.00 deposit and a blank date.
Shared-Unit Pricing After Edits and Recalculation (KT-15104)
KtApiPriceQuery builds price_lines_by_passengers per passenger instead of per unit — multi-passenger shared-unit bookings silently zero-price against KTAPI ≥ v1.0.1 (edit/recalc path still broken after KTAPI v1.0.2) Price Breakdown Fixed bookings with multiple passengers sharing an occupancy unit showing a zero total price after an edit or price recalculation. This fix requires KTAPI v1.0.3 or later in addition to the Kaptio Travel package update.
Multi-Passenger Payment Allocation (KT-15058)
Multi-passenger payment-request checkout collapses allocation into a single entry (full amount on first passenger's schedule) — Aurora patch candidate Payments Fixed payment schedules showing Amount Paid as zero or incorrect when a customer paid for multiple passengers in a single payment-request checkout. Each passenger's schedule now receives the correct per-passenger amount instead of the full payment being applied to one passenger only.
Pay-per-Passenger Payment Schedule Updates (KT-15057)
Payment allocation writeback omits passengerId on pay-per-passenger itineraries (Amount Paid stuck at 0) — Aurora patch on 22.12.7.x Payments Fixed payment schedules showing Amount Paid as zero on pay-per-passenger itineraries when payments were made through the classic payment-request checkout or entered manually (for example, bank transfer). Payments are now correctly linked to the passenger and reflected on the payment schedule.