New Features
Deposit Top-Up APIs
Added API support for the Deposit Top-Up feature, allowing both customers and agents to purchase and credit deposits through the existing booking and payment flow. The implementation includes APIs to retrieve available top-up options, create top-up bookings, and process payments using existing PSP integrations. A front-end flow/design document is also provided to support seamless implementation. The feature is primarily designed for the new IBE, but can also be used by customers with their own websites connected to AeroCRS via API.
Improvements to existing features
Flight email notifications from PNR screen — Non-English characters
Enhancement to ensure email notifications sent from the PNR screen are correctly stored in the ALOG table when using non-English characters in the Header Text option (for example, Hebrew). Previously, Unicode characters could be saved as question marks, making the log entries unreadable and limiting audit capabilities. The improvement adds proper character encoding support so languages such as Hebrew and other special character sets are preserved exactly as sent. Existing logging behavior for English notifications remains unchanged.
getCustomer — Deposit balance
Enhance the getCustomer API response to return the customer's deposit balances per currency, similar to the deposit object already available in getAgency. This is required for the new IBE so customer deposit information can be retrieved together with the customer profile in one API call.
This improvement allows users to review the customer's deposit easily without the need to use a different API call (getCustomerDataNew), which requires specific validation per customer. The feature can also be used by airlines that have their own website connected to AeroCRS via API.
Traveller Picker — Focus shouldn't skip automatically
Added a new IBE setting to control the search engine auto-focus behavior after selecting a destination. When disabled, the focus remains on the selected field instead of automatically moving to the next one (to destination), allowing users to review and confirm their selection before proceeding. This improvement ensures compliance with accessibility requirements.
Bug fixes
Agency Email Selected from Dropdown Not Logged in PNR Activity
Fix to ensure the PNR logs include any email address selected from the confirmation email sending dropdown, specifically for agency bookings.
Generate name group once ticket is issued (PNL)
Fix to ensure the correct handling and transmission of the group indicator within the PNL/ADL process. The logic should rely on the ticketing process instead of invoice creation to properly identify and send group bookings. Previously, group PNRs in ADL could have the group name missing, as at the moment when ADL was sent, the invoice was not generated yet.
No-show Trigger, Baggage get refund on the original PNR
Fix to properly move and refund the flight-related ancillaries to the new split PNR after triggering the No-show policy (before the fix, the refund amount of the ancillary PNR remained in the original PNR).
MMB duplicate segment
Previously, duplicate flight segments could appear in a booking after a passenger changed their flight through the Manage My Booking (MMB) amend process. Under specific conditions, the newly selected flight could be attached to the reservation more than once, resulting in duplicate segments being displayed in the PNR. This has now been fixed.
The amendment process has been improved to ensure that only a single instance of the new flight segment is attached to the booking, while preserving all associated seats, SSRs, and ancillary services. This enhancement improves booking integrity across CRS, itinerary displays, notifications, reporting, and operational messaging processes.
As part of the fix, additional validation was introduced during the amendment process to detect and remove duplicate flight entries before they are attached to the booking, ensuring only one active segment is retained for the selected flight.
Incomplete check-in records created during IBE online check-in
Previously, duplicate check-in records could be created when a passenger started the online check-in process through MMB but did not complete it, and the airline later completed or corrected the check-in from CRS. In these cases, the system could create a second valid check-in record instead of updating the existing one, resulting in duplicate passenger entries being displayed on the flight passenger list. This has now been fixed.
The online check-in process has been improved to automatically remove incomplete check-in records and generate a PNR log entry when a check-in is not successfully completed. Additionally, CRS validations have been enhanced to verify whether a matching check-in record already exists before creating a new one, preventing duplicate records from being generated.
Additional logging has also been added to the seat map check-in process to improve traceability and assist with future investigations should similar scenarios occur.
Incorrect seat price on the IBE extra summary page
Previously, several issues affected seat pricing display during the seat-only booking flow and ancillary seat reservation process. Under specific scenarios, seat prices could be displayed as free, totals could appear as zero on the summary page, or seat amounts could be incorrectly doubled in the booking summary despite the final PNR being created with the correct pricing. This has now been fixed.
The seat pricing calculation process has been updated to ensure all selected seats are correctly included in the pricing breakdown and session data before totals are calculated. Additional improvements were made to align the seat-only flow with recent API changes and to ensure that the displayed totals reflect the actual amount payable by the customer.
This enhancement provides accurate seat pricing throughout seat selection, basket review, booking summary, and MMB pages, ensuring consistency between the customer-facing display and the final booking records.
New Fare Structure: wrong custom type for children and infants
Availability: All customers (new fare structure)
Previously, airlines using the Advanced Fare Structure configuration could have custom child passenger types incorrectly assigned during the booking process. In certain scenarios, passengers booked under a specific child fare type, such as "Unaccompanied Minor", were assigned to a different child passenger type after passenger creation. This has now been fixed.
The passenger type matching process has been improved to correctly identify and assign the selected custom fare structure passenger type based on the configured adult, child, and infant fare mappings. Additional validation was added to strengthen the lookup process and prevent incorrect passenger type assignments.
This enhancement ensures that custom passenger types are consistently maintained throughout the booking process, improving fare validation and reducing booking errors for airlines using advanced fare configurations.
Booking confirmation email not triggered for zero-value
Fixed the booking confirmation process to correctly handle reservations containing zero-value services. The confirmation email flow previously waited for invoice creation before sending the booking confirmation, ensuring invoice links were included when applicable. In specific scenarios involving services with a total value of zero, no invoice was generated, preventing the booking confirmation email from being sent. The logic has been updated to bypass the invoice validation requirement for zero-priced services, ensuring passengers receive their booking confirmation while maintaining the existing behavior for bookings that require invoice generation.
MMB blocked for split PNR
Fix to ensure the rebooking process works correctly for bookings that have been split into multiple PNRs. Previously, passenger quantity validation was performed using all active flight inventory associated with the same cart reference, which could result in incorrect validation failures when multiple PNRs shared the same cart. This caused valid rebooking attempts to be blocked and displayed the message "No services in your itinerary" in the IBE. The validation logic has been updated to evaluate flight inventory using both the cart reference and the specific PNR, ensuring each booking is processed independently and accurately during the rebooking flow.
New created agency does not inherit GSA
Previously, agencies created by GSA users were not automatically associated with the creating GSA. This has now been fixed. The system now correctly saves the GSA assignment during agency creation, ensuring the agency appears immediately within the GSA user's reporting structure and agency list.
Agency excess PNR for direct customers
On the new IBE, we improved excess booking ownership logic for ancillary and seat purchases on agency reservations. Excess PNRs are now created according to the user performing the action: direct customers generate direct customer bookings, while authenticated web agents generate agency bookings. For API integrations, agency ownership is applied only when valid agent parameters are provided; otherwise, the excess PNR is created as a direct customer booking, matching legacy website behavior.
IBE modify seats — Wrong seats for inbound flight
Previously, in Manage My Booking, incorrect seat assignments could be displayed when modifying seats for the return leg of round-trip bookings. This has now been fixed. The system now correctly loads and displays the assigned seat for each passenger on the selected flight segment, ensuring consistent behavior across both outbound and return flights.
Comments