...

There are identifiers that are used on different request/response chains.

...

13.1.1. EXCURSIONRESERVATIONIDS

The ExcursionReservationIDs is used as unique identifier of a booking.

...

You have to store all values of ExcursionReservationIDs in your system, and use it unchanged through whole booking's life cycle.

...

Diagram 1113.1.1.1. ExcursionReservationIDs flow

...

<ExcursionReservationIDs>
  <ExcursionReservationID ResID_Source="agent" ResID_Value="hjo8dfg"/>
  <ExcursionReservationID ResID_Source="client" ResID_Value="34rf4g3frre45"/>
  <ExcursionReservationID ResID_Source="supplier" ResID_SourceContext="supplierCode" ResID_Value="164-4732160"/>
</ExcursionReservationIDs>

...

13.1.2. BOOKINGCODE

The BookingCode attribute in ExcursionRate element is used as unique identifier of an offer starting Excursion Availability response and till the time the booking is confirmed. The BookingCode is valid for limited time (normally 15 minutes); if the reservation was not confirmed (or at least initiated) during this time limit, then new search should be performed again.

...

BookingCode may change between Availability search and Reservation Initiate response (it depends on supplier specific). In Reservation Confirmation request, the BookingCode must be taken from the Reservation Initiate response.

...

Diagram 1113.1.2.1. BookingCode usage

Since an excursion booked, the BookingCode does not play role for the reservation anymore. The ExcursionReservationIDs should be used for the booking cancellation.

...

13.1.3. TRANSACTIONIDENTIFIER

Excursion Reservation and Cancellation should always be done in two steps: 1) Initiation (request/response) and 2)Confirmation or Ignore (request/response). Both these steps have to be done within one transaction.

The TransactionIdentifier allows to recognize which Confirmation or Ignore request relates to the Initiation response.

...

Diagram 1113.1.3.1. TransactionIdentifier usage

...