Release Identification

Release Version	Type (Version, Update, or Patch)	Date	Approved by	Description of Change
21.08	Version	July 2021	Rafał Hołub	Software updated

Enhancements

Digital Connect introduces the following enhancements:

• 3D-Secure (3DS) version 2.0 authentication support
• Manage Your Bookings: Modify Trip Options (MYB: MTO) flow performance improvements
• EndTransaction service version upgrade

Defects

The following Digital Connect defects have been fixed for this release:

• Newly selected seats and retained seats both shown in exchange products
• Data missing from /pnr response
• Segment time issue in PNR retrieval
• Itinerary details retrieval issue
• Double last name PNR retrieval failure
• PNR lookup not returning DOCS description
• MTO mandatory email

Enhancements:

3DS version 2.0 authentication support

Digital Connect includes the support for 3D-Secure authentication version 2.0 in order to give the issuing bank additional flexibility in payer authentication. The new online credit card payment protocol adds improvements to the widely used version 1.0 by addressing many of its issues and introducing enhancements such as:

• Allowing for more data to be sent with each transaction
• Integrated "challenge" flow that bolsters security
• Increasing the number of transactions that can be authenticated without customer input
• Integrating the authentication protocol into the payment app
• User experience overhaul
• Integrating passive, biometric, and two-factor identification approaches.

Prerequisites

None.

Limitations

None.

Request and Response examples

3D Secure Request and Response Examples

Modify Trip Options flow performance improvements

The MTO flow has been optimized for increased performance. A new workflow has been introduced to add purchaser information (phone number, email, and address) to the PNR, and redundant calls have been removed.

Prerequisites:

None.

Limitations:

None.

 

EndTransaction service version upgrade

The EndTransaction service has been upgraded to version 2.1.0 TPFC1 services have been replaced with TPFC2 version to decrease latency and achieve faster response time.

Prerequisites:

None.

Limitations:

None.

 

Defect Fixes:

Newly selected seats and retained seats both shown in exchange products

Customer Tracking #: N/A	Sabre Tracking #: DC-12316
Description: When a passenger has already selected seats in the B2C flow, the newly selected seats were not returned by Digital Connect in the exchange path. Instead, the originally selected seats were displayed.
Resolution: When a new seat is selected in the exchange path, the seat number is returned under subelement in the Product Response. Under subelement the seat has a value of zero as the seat has been reassociated.

 

Data missing from /pnr response

Customer Tracking #: N/A	Sabre Tracking #: DC-12500
Description: Upon retrieving the response from /pnr API, instalment information has been missing.
Resolution: /pnr remarks have been updated to return the missing data in the API response.

 

Segment time issue in PNR retrieval

Customer Tracking #: N/A	Sabre Tracking #: DC-12926
Description: The departure field of the frequent flyer section was showing the departure date and incorrect time (00:00:00). The reason behind the issue has been that the GetReservation response only contained the departure date.
Resolution: Departure date and time is populated from passengerFFDetails instead of GetReservation.

 

Itinerary details retrieval issue

Customer Tracking #: 05649714	Sabre Tracking #: DC-12636
Description: Upon retrieving a PNR, not all itinerary details have been returned. For reservations with two stops, only one was returned.
Resolution: All stops in the reservation are successfully returned.

 

Double last name PNR retrieval failure

Customer Tracking #: 05649714	Sabre Tracking #: DC-12560
Description: After a successful booking of a passenger with two surnames, the passenger's name record was not retrievable.
Resolution: The configuration gds.sabre.ws.pnr.tierLevels has been updated to solve the issue.

 

PNR lookup not returning DOCS description

Customer Tracking #: N/A	Sabre Tracking #: DC-12839
Description: Upon retrieving a PNR, only a single document has been returned instead of all the documents included in the reservation. The specialServiceRequests element that contains DOCS value has also been incorrectly returned as empty.
Resolution: PNR retrieve service returns all documents of the passenger. Within the Passenger element, allDocumentInfos have been added to store all the documents of the passenger.

 

MTO mandatory email

Customer Tracking #: N/A	Sabre Tracking #: DC-12839
Description: With Digital Connect allowing for creating a reservation with no mandatory email field, such a reservation could not be updated in the MTO flow as the validation required email to be present.
Resolution: If there are no emails present in the B2C flow, the edit Passenger flow allows action without the email address.