Skip Navigation

Parameters for ExchangeEmdRQ Fulfill Request

The mandatory request parameters for EMD Exchange fulfillment are the same as those described in section 3.2.1.  The only difference in the request structure, is the attribute on the <Options/> element:

  • Use PriceComparisson to request an exchange calculation summary

    XPath
    //TransactionInfo/@requestType = PriceComparisson
     
  • Use Fulfill to request an exchange fulfillment

    XPath
    //TransactionInfo/@requestType = Fulfill

However, for fulfillment requests, there are some additional parameters, as indicated in the chart below.  These optional qualifiers are used in addition to the mandatory parameters listed on the table in section 3.2.1.

 

Element

XPath
(from root ExchangeEmdRQ)

Purpose

<Commission/>

 

//@Fulfill/Commission/Commission/Amount

 

 

If the EMD Exchange is an additional collection, and that additional collection is commissionable, the agent would specify the add/collect commission with these elements

     <Amount/>

//@Fulfil/Commission/Commission/Amount

Used with commission amount

    <Percent/>

//@Fulfil/Commission/Commission/Percent

Used with commission percent

<NewTicketFullCommission/>

//@Fulfill/Commission/NewTicketFullCommission

For use in ARC locations only. If the agent took commission on the old EMD, the agent would include that commission plus any commission on an additional collection with this element. Always expressed as an amount. 

<Payment/>

//@Fulfill/Payment

Used with additional collection exchanges to show how the amount due was paid for.

   <Card/>

//@Fulfill/Payment/Card

Used for credit cards

      @vendorCode

//@Fulfill/Payment/Card/@vendorCode

The credit card vendor code (e.g. AX for American Express)

      @number

//@Fulfill/Payment/Card/@number

The credit card number

      @expireDate

//@Fulfill/Payment/Card/@expireDate

The credit card expiration date

       @manualApprov
           alCode

//@Fulfill/Payment/Card/@manualApprovalCode

Used when the agency has manually obtained the credit card approval code. When used, the internal automated system credit card authorization code will not be invoked.

   <GovernmentTrav
       el/>

//@Fulfill/Payment/GovernmentTravel

 

   <ReservationFOP/>

//@Fulfill/Payment/ReservationFOP

If your agency uses the TJR option PNAPNR, and stores the form of Payment in the *FOP field, the user would include the *FOP reference number with this element.

   <Virtual/>

//@Fulfill/Payment/Virtual

If your agency accepts Virtual Credit Card payments and has an account with Conferma, the agent would use the traveler’s CAC code with this element.

   <Miscellaneous/>

//@Fulfill/Payment/Miscellaneous

If your agency uses Miscellaneous FOP, Sabre green screen #MS qualifier, the agent would include the miscellaneous information (a string) with this element.