Showing:

Annotations
Attributes
Diagrams
Facets
Instances
Properties
Source
Used by
Main schema ProcessPaymentRQ.xsd
Namespace No namespace
Properties
attribute form default: unqualified
element form default: qualified
[ top ]
Included schema CommonTypes.xsd
Namespace No namespace
Properties
attribute form default: qualified
element form default: qualified
[ top ]
Element ProcessPaymentRQ
Namespace No namespace
Annotations
Root element to issue a request to either charge or refund any item(s) listed in this request.

Such items may be services and/or flights for a single or multiple traveler PNR.

This request supports multiple FOPs to be provided.

This request can be sent to request a charge againsr provided FOPs or to request a refund to the provided FOP(s).  The attribute @ProcessType identifies if it is used as a CHARGE or REFUND request.
Diagram
Diagram ProcessPaymentRQ.tmp#ProcessPaymentRQ_Version ProcessPaymentRQ.tmp#RecordLocator ProcessPaymentRQ.tmp#ProcessPaymentRQ_Traveler ProcessPaymentRQ.tmp#ProcessPaymentRQ_CurrencyCode ProcessPaymentRQ.tmp#ProcessPaymentRQ_FormOfPayment ProcessPaymentRQ.tmp#ProcessPaymentRQ_PymtTotal
Properties
content: complex
Model RecordLocator , Traveler* , CurrencyCode , FormOfPayment+ , PymtTotal{0,1}
Children CurrencyCode, FormOfPayment, PymtTotal, RecordLocator, Traveler
Instance
<ProcessPaymentRQ Version="">
  <RecordLocator>{1,1}</RecordLocator>
  <Traveler>{0,unbounded}</Traveler>
  <CurrencyCode NumberOfDecimals="">{1,1}</CurrencyCode>
  <FormOfPayment>{1,unbounded}</FormOfPayment>
  <PymtTotal Total="">{0,1}</PymtTotal>
</ProcessPaymentRQ>
Attributes
QName Type Fixed Default Use Annotation
Version xsd:string optional
Version of the message to be used.
Example: 2.2
Source
<xsd:element name="ProcessPaymentRQ">
  <xsd:annotation>
    <xsd:documentation>Root element to issue a request to either charge or refund any item(s) listed in this request. Such items may be services and/or flights for a single or multiple traveler PNR. This request supports multiple FOPs to be provided. This request can be sent to request a charge againsr provided FOPs or to request a refund to the provided FOP(s). The attribute @ProcessType identifies if it is used as a CHARGE or REFUND request.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="RecordLocator">
        <xsd:annotation>
          <xsd:documentation>PNR record locator from where this EMD is issued from.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="Traveler" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>Items per traveler (services, air segments) for which charge or refund applies MANDATORY for charges, optional for refunds</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element ref="TravelerElementNumber">
              <xsd:annotation>
                <xsd:documentation>Element number of this traveler from the referenced PNR. Example: 1</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
            <xsd:sequence>
              <xsd:element name="ServiceElementNumber" minOccurs="0" maxOccurs="unbounded">
                <xsd:annotation>
                  <xsd:documentation>Element number of the service from the referenced PNR. Example: 1</xsd:documentation>
                </xsd:annotation>
              </xsd:element>
              <xsd:element ref="SegmentElementNumber" minOccurs="0" maxOccurs="unbounded">
                <xsd:annotation>
                  <xsd:documentation>Element number of the flight from the referenced PNR. Example: 1</xsd:documentation>
                </xsd:annotation>
              </xsd:element>
            </xsd:sequence>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="CurrencyCode">
        <xsd:annotation>
          <xsd:documentation>Currency code of Point of Sale (POS) Example: USD</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:restriction base="CurrencyCodeType">
              <xsd:pattern value="[A-Z0-9]{3}"/>
              <xsd:attribute name="NumberOfDecimals" type="xsd:integer" use="required">
                <xsd:annotation>
                  <xsd:documentation>Decimal position in fare amount. Example: 2</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
            </xsd:restriction>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="FormOfPayment" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>The form of payment(s) to be used for this payment ot refund request</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:annotation>
              <xsd:documentation>Not supported functionality: Split FOP Extended CC payment</xsd:documentation>
            </xsd:annotation>
            <xsd:element name="FOPTotal">
              <xsd:annotation>
                <xsd:documentation>Total amount to be charged or refunded (negative amount) with this request against this FOP</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:attribute name="Total" type="xsd:integer" use="required">
                  <xsd:annotation>
                    <xsd:documentation>Total amount to be debited or credited (negative amount) with this request against this FOP. Example: 10675</xsd:documentation>
                  </xsd:annotation>
                </xsd:attribute>
              </xsd:complexType>
            </xsd:element>
            <xsd:element name="PaymentReference" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>ONLY used if this request is a REFUND request. This is a reference back to the original payment made (and required by some airlines)</xsd:documentation>
              </xsd:annotation>
              <xsd:simpleType>
                <xsd:restriction base="xsd:string">
                  <xsd:minLength value="1"/>
                </xsd:restriction>
              </xsd:simpleType>
            </xsd:element>
            <xsd:element name="ServiceElementNumber" minOccurs="0" maxOccurs="unbounded">
              <xsd:annotation>
                <xsd:documentation>Element number of the service from the referenced PNR may be referenced directly to this FOP as well. Note that any items mapped here must also be mapped under Traveler/ServiceElementNumber. Example: 1</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
            <xsd:element ref="SegmentElementNumber" minOccurs="0" maxOccurs="unbounded"/>
            <xsd:element name="PreviousCredits" minOccurs="0">
              <xsd:annotation>
                <xsd:documentation>Reference to any credit available and to be applied to the payment requested with this transaction. Any credit identified here is applied first, any remaining balance is then charged to credit card provided</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:sequence>
                  <xsd:element name="CreditReference" maxOccurs="unbounded">
                    <xsd:annotation>
                      <xsd:documentation>This can be a voucher, payment ID, credit reference or confirmation number associated to the amount listed under FOPTotal Example: 3665341</xsd:documentation>
                    </xsd:annotation>
                    <xsd:complexType>
                      <xsd:simpleContent>
                        <xsd:extension base="xsd:string">
                          <xsd:attribute name="CreditAmount">
                            <xsd:annotation>
                              <xsd:documentation>The amount of credit available. If entered, the amount is passed to vendor. An error response is possible if amount does not match amount of record</xsd:documentation>
                            </xsd:annotation>
                          </xsd:attribute>
                          <xsd:attribute name="BookingReference">
                            <xsd:annotation>
                              <xsd:documentation>This could be an additional reference, e.g. RecLoc or confirmation number associated to this credit</xsd:documentation>
                            </xsd:annotation>
                          </xsd:attribute>
                        </xsd:extension>
                      </xsd:simpleContent>
                    </xsd:complexType>
                  </xsd:element>
                </xsd:sequence>
              </xsd:complexType>
            </xsd:element>
            <xsd:choice minOccurs="0">
              <xsd:element name="CreditCard">
                <xsd:annotation>
                  <xsd:documentation>Credit card group</xsd:documentation>
                </xsd:annotation>
                <xsd:complexType>
                  <xsd:sequence>
                    <xsd:element name="CCCode">
                      <xsd:annotation>
                        <xsd:documentation>Credit card code. Example: VI</xsd:documentation>
                      </xsd:annotation>
                      <xsd:simpleType>
                        <xsd:restriction base="xsd:string">
                          <xsd:length value="2"/>
                        </xsd:restriction>
                      </xsd:simpleType>
                    </xsd:element>
                    <xsd:element name="CCNumber" type="xsd:string">
                      <xsd:annotation>
                        <xsd:documentation>Credit card number. Example: 4011236654652341</xsd:documentation>
                      </xsd:annotation>
                    </xsd:element>
                    <xsd:element name="CCExpiration">
                      <xsd:annotation>
                        <xsd:documentation>Credit card expiration group</xsd:documentation>
                      </xsd:annotation>
                      <xsd:complexType>
                        <xsd:sequence>
                          <xsd:element name="Month">
                            <xsd:annotation>
                              <xsd:documentation>Credit card expiration month. Example: 02</xsd:documentation>
                            </xsd:annotation>
                            <xsd:simpleType>
                              <xsd:restriction base="xsd:string">
                                <xsd:length value="2"/>
                              </xsd:restriction>
                            </xsd:simpleType>
                          </xsd:element>
                          <xsd:element name="Year">
                            <xsd:annotation>
                              <xsd:documentation>Last two digits of the credit card expiration year. Example: 06</xsd:documentation>
                            </xsd:annotation>
                            <xsd:simpleType>
                              <xsd:restriction base="xsd:string">
                                <xsd:length value="2"/>
                                <xsd:pattern value="[0-9][0-9]"/>
                              </xsd:restriction>
                            </xsd:simpleType>
                          </xsd:element>
                        </xsd:sequence>
                      </xsd:complexType>
                    </xsd:element>
                    <xsd:element name="SecurityID" type="xsd:string" minOccurs="0">
                      <xsd:annotation>
                        <xsd:documentation>Credit card security number for online transactions (referred to also as CVV2, CVC2, CSC or CID). This is a 3-digit (Visa, Master, Discover) or 4-digit (Amex) number.</xsd:documentation>
                      </xsd:annotation>
                    </xsd:element>
                    <xsd:element ref="Authorization" minOccurs="0"/>
                    <xsd:element name="ApprovalCode" type="xsd:string" minOccurs="0">
                      <xsd:annotation>
                        <xsd:documentation>MANUAL credit card approval code. If a code exists here no authorization request will be performed. Example: 996456</xsd:documentation>
                      </xsd:annotation>
                    </xsd:element>
                    <xsd:choice minOccurs="0">
                      <xsd:sequence>
                        <xsd:element ref="CardholderFirstName" minOccurs="0"/>
                        <xsd:element ref="CardholderLastName"/>
                      </xsd:sequence>
                      <xsd:element name="CardholderFullName">
                        <xsd:annotation>
                          <xsd:documentation>Credit cardholder full name as it appears on the card</xsd:documentation>
                        </xsd:annotation>
                        <xsd:simpleType>
                          <xsd:restriction base="xsd:string">
                            <xsd:minLength value="1"/>
                          </xsd:restriction>
                        </xsd:simpleType>
                      </xsd:element>
                    </xsd:choice>
                    <xsd:element name="CCAddressGroup" minOccurs="0">
                      <xsd:annotation>
                        <xsd:documentation>Card holders address</xsd:documentation>
                      </xsd:annotation>
                      <xsd:complexType>
                        <xsd:sequence>
                          <xsd:element ref="Address" maxOccurs="2"/>
                          <xsd:element ref="City"/>
                          <xsd:element ref="PostalCode"/>
                          <xsd:element ref="StateCode" minOccurs="0"/>
                          <xsd:element ref="CountryCode">
                            <xsd:annotation>
                              <xsd:documentation>ISO Country code. This element is introduced as mandatory although GDS implementation will not require its presence until 30MAR2008. Example: US</xsd:documentation>
                            </xsd:annotation>
                          </xsd:element>
                        </xsd:sequence>
                      </xsd:complexType>
                    </xsd:element>
                  </xsd:sequence>
                </xsd:complexType>
              </xsd:element>
              <xsd:element name="Other">
                <xsd:annotation>
                  <xsd:documentation>Other payment type. Possible values: CASH, CHECK.</xsd:documentation>
                </xsd:annotation>
                <xsd:simpleType>
                  <xsd:restriction base="xsd:string">
                    <xsd:enumeration value="CASH"/>
                    <xsd:enumeration value="CHECK"/>
                    <xsd:enumeration value=""/>
                  </xsd:restriction>
                </xsd:simpleType>
              </xsd:element>
            </xsd:choice>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="PymtTotal" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Total amount to be charged or refunded with this request (sum of all FOPs)</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:attribute name="Total" type="xsd:integer">
            <xsd:annotation>
              <xsd:documentation>Total amount to be debited or credited with this request. Example: 10675</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="Version" type="xsd:string">
      <xsd:annotation>
        <xsd:documentation>Version of the message to be used. Example: 2.2</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element RecordLocator
Namespace No namespace
Annotations
PNR record locator.  Example: R1A3SK
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Source
<xsd:element name="RecordLocator" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>PNR record locator. Example: R1A3SK</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / Traveler
Namespace No namespace
Annotations
Items per traveler (services, air segments) for which charge or refund applies

MANDATORY for charges, optional for refunds
Diagram
Diagram ProcessPaymentRQ.tmp#TravelerElementNumber ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_Traveler_ServiceElementNumber ProcessPaymentRQ.tmp#SegmentElementNumber
Properties
content: complex
minOccurs: 0
maxOccurs: unbounded
Model TravelerElementNumber , ServiceElementNumber* , SegmentElementNumber*
Children SegmentElementNumber, ServiceElementNumber, TravelerElementNumber
Instance
<Traveler>
  <TravelerElementNumber>{1,1}</TravelerElementNumber>
  <ServiceElementNumber>{0,unbounded}</ServiceElementNumber>
  <SegmentElementNumber>{0,unbounded}</SegmentElementNumber>
</Traveler>
Source
<xsd:element name="Traveler" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>Items per traveler (services, air segments) for which charge or refund applies MANDATORY for charges, optional for refunds</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="TravelerElementNumber">
        <xsd:annotation>
          <xsd:documentation>Element number of this traveler from the referenced PNR. Example: 1</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:sequence>
        <xsd:element name="ServiceElementNumber" minOccurs="0" maxOccurs="unbounded">
          <xsd:annotation>
            <xsd:documentation>Element number of the service from the referenced PNR. Example: 1</xsd:documentation>
          </xsd:annotation>
        </xsd:element>
        <xsd:element ref="SegmentElementNumber" minOccurs="0" maxOccurs="unbounded">
          <xsd:annotation>
            <xsd:documentation>Element number of the flight from the referenced PNR. Example: 1</xsd:documentation>
          </xsd:annotation>
        </xsd:element>
      </xsd:sequence>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element TravelerElementNumber
Namespace No namespace
Annotations
Element number of traveler associated to this item.  Example: 1
Diagram
Diagram
Type extension of xsd:string
Properties
content: complex
Used by
Source
<xsd:element name="TravelerElementNumber">
  <xsd:annotation>
    <xsd:documentation>Element number of traveler associated to this item. Example: 1</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string"/>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / Traveler / ServiceElementNumber
Namespace No namespace
Annotations
Element number of the service from the referenced PNR.  Example: 1
Diagram
Diagram
Properties
minOccurs: 0
maxOccurs: unbounded
Source
<xsd:element name="ServiceElementNumber" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>Element number of the service from the referenced PNR. Example: 1</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element SegmentElementNumber
Namespace No namespace
Annotations
Element number of the flight associated to this item.  Example: 1
Diagram
Diagram
Type extension of xsd:string
Properties
content: complex
Used by
Source
<xsd:element name="SegmentElementNumber">
  <xsd:annotation>
    <xsd:documentation>Element number of the flight associated to this item. Example: 1</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string"/>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / CurrencyCode
Namespace No namespace
Annotations
Currency code of Point of Sale (POS)  

Example: USD
Diagram
Diagram ProcessPaymentRQ.tmp#CurrencyCodeType_NumberOfDecimals ProcessPaymentRQ.tmp#CurrencyCodeType ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_CurrencyCode_NumberOfDecimals
Type restriction of CurrencyCodeType
Type hierarchy
Properties
content: complex
Attributes
QName Type Fixed Default Use Annotation
NumberOfDecimals xsd:integer required
Decimal position in fare amount.  Example: 2
Source
<xsd:element name="CurrencyCode">
  <xsd:annotation>
    <xsd:documentation>Currency code of Point of Sale (POS) Example: USD</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:restriction base="CurrencyCodeType">
        <xsd:pattern value="[A-Z0-9]{3}"/>
        <xsd:attribute name="NumberOfDecimals" type="xsd:integer" use="required">
          <xsd:annotation>
            <xsd:documentation>Decimal position in fare amount. Example: 2</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:restriction>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / FormOfPayment
Namespace No namespace
Annotations
The form of payment(s) to be used for this payment ot refund request
Diagram
Diagram ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_FOPTotal ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_PaymentReference ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_ServiceElementNumber ProcessPaymentRQ.tmp#SegmentElementNumber ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_PreviousCredits ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_CreditCard ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_Other
Properties
content: complex
maxOccurs: unbounded
Model FOPTotal , PaymentReference{0,1} , ServiceElementNumber* , SegmentElementNumber* , PreviousCredits{0,1} , (CreditCard | Other)
Children CreditCard, FOPTotal, Other, PaymentReference, PreviousCredits, SegmentElementNumber, ServiceElementNumber
Instance
<FormOfPayment>
  <FOPTotal Total="">{1,1}</FOPTotal>
  <PaymentReference>{0,1}</PaymentReference>
  <ServiceElementNumber>{0,unbounded}</ServiceElementNumber>
  <SegmentElementNumber>{0,unbounded}</SegmentElementNumber>
  <PreviousCredits>{0,1}</PreviousCredits>
  <CreditCard>{1,1}</CreditCard>
  <Other>{1,1}</Other>
</FormOfPayment>
Source
<xsd:element name="FormOfPayment" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>The form of payment(s) to be used for this payment ot refund request</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:annotation>
        <xsd:documentation>Not supported functionality: Split FOP Extended CC payment</xsd:documentation>
      </xsd:annotation>
      <xsd:element name="FOPTotal">
        <xsd:annotation>
          <xsd:documentation>Total amount to be charged or refunded (negative amount) with this request against this FOP</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:attribute name="Total" type="xsd:integer" use="required">
            <xsd:annotation>
              <xsd:documentation>Total amount to be debited or credited (negative amount) with this request against this FOP. Example: 10675</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="PaymentReference" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>ONLY used if this request is a REFUND request. This is a reference back to the original payment made (and required by some airlines)</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:minLength value="1"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
      <xsd:element name="ServiceElementNumber" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>Element number of the service from the referenced PNR may be referenced directly to this FOP as well. Note that any items mapped here must also be mapped under Traveler/ServiceElementNumber. Example: 1</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element ref="SegmentElementNumber" minOccurs="0" maxOccurs="unbounded"/>
      <xsd:element name="PreviousCredits" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Reference to any credit available and to be applied to the payment requested with this transaction. Any credit identified here is applied first, any remaining balance is then charged to credit card provided</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="CreditReference" maxOccurs="unbounded">
              <xsd:annotation>
                <xsd:documentation>This can be a voucher, payment ID, credit reference or confirmation number associated to the amount listed under FOPTotal Example: 3665341</xsd:documentation>
              </xsd:annotation>
              <xsd:complexType>
                <xsd:simpleContent>
                  <xsd:extension base="xsd:string">
                    <xsd:attribute name="CreditAmount">
                      <xsd:annotation>
                        <xsd:documentation>The amount of credit available. If entered, the amount is passed to vendor. An error response is possible if amount does not match amount of record</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                    <xsd:attribute name="BookingReference">
                      <xsd:annotation>
                        <xsd:documentation>This could be an additional reference, e.g. RecLoc or confirmation number associated to this credit</xsd:documentation>
                      </xsd:annotation>
                    </xsd:attribute>
                  </xsd:extension>
                </xsd:simpleContent>
              </xsd:complexType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:choice minOccurs="0">
        <xsd:element name="CreditCard">
          <xsd:annotation>
            <xsd:documentation>Credit card group</xsd:documentation>
          </xsd:annotation>
          <xsd:complexType>
            <xsd:sequence>
              <xsd:element name="CCCode">
                <xsd:annotation>
                  <xsd:documentation>Credit card code. Example: VI</xsd:documentation>
                </xsd:annotation>
                <xsd:simpleType>
                  <xsd:restriction base="xsd:string">
                    <xsd:length value="2"/>
                  </xsd:restriction>
                </xsd:simpleType>
              </xsd:element>
              <xsd:element name="CCNumber" type="xsd:string">
                <xsd:annotation>
                  <xsd:documentation>Credit card number. Example: 4011236654652341</xsd:documentation>
                </xsd:annotation>
              </xsd:element>
              <xsd:element name="CCExpiration">
                <xsd:annotation>
                  <xsd:documentation>Credit card expiration group</xsd:documentation>
                </xsd:annotation>
                <xsd:complexType>
                  <xsd:sequence>
                    <xsd:element name="Month">
                      <xsd:annotation>
                        <xsd:documentation>Credit card expiration month. Example: 02</xsd:documentation>
                      </xsd:annotation>
                      <xsd:simpleType>
                        <xsd:restriction base="xsd:string">
                          <xsd:length value="2"/>
                        </xsd:restriction>
                      </xsd:simpleType>
                    </xsd:element>
                    <xsd:element name="Year">
                      <xsd:annotation>
                        <xsd:documentation>Last two digits of the credit card expiration year. Example: 06</xsd:documentation>
                      </xsd:annotation>
                      <xsd:simpleType>
                        <xsd:restriction base="xsd:string">
                          <xsd:length value="2"/>
                          <xsd:pattern value="[0-9][0-9]"/>
                        </xsd:restriction>
                      </xsd:simpleType>
                    </xsd:element>
                  </xsd:sequence>
                </xsd:complexType>
              </xsd:element>
              <xsd:element name="SecurityID" type="xsd:string" minOccurs="0">
                <xsd:annotation>
                  <xsd:documentation>Credit card security number for online transactions (referred to also as CVV2, CVC2, CSC or CID). This is a 3-digit (Visa, Master, Discover) or 4-digit (Amex) number.</xsd:documentation>
                </xsd:annotation>
              </xsd:element>
              <xsd:element ref="Authorization" minOccurs="0"/>
              <xsd:element name="ApprovalCode" type="xsd:string" minOccurs="0">
                <xsd:annotation>
                  <xsd:documentation>MANUAL credit card approval code. If a code exists here no authorization request will be performed. Example: 996456</xsd:documentation>
                </xsd:annotation>
              </xsd:element>
              <xsd:choice minOccurs="0">
                <xsd:sequence>
                  <xsd:element ref="CardholderFirstName" minOccurs="0"/>
                  <xsd:element ref="CardholderLastName"/>
                </xsd:sequence>
                <xsd:element name="CardholderFullName">
                  <xsd:annotation>
                    <xsd:documentation>Credit cardholder full name as it appears on the card</xsd:documentation>
                  </xsd:annotation>
                  <xsd:simpleType>
                    <xsd:restriction base="xsd:string">
                      <xsd:minLength value="1"/>
                    </xsd:restriction>
                  </xsd:simpleType>
                </xsd:element>
              </xsd:choice>
              <xsd:element name="CCAddressGroup" minOccurs="0">
                <xsd:annotation>
                  <xsd:documentation>Card holders address</xsd:documentation>
                </xsd:annotation>
                <xsd:complexType>
                  <xsd:sequence>
                    <xsd:element ref="Address" maxOccurs="2"/>
                    <xsd:element ref="City"/>
                    <xsd:element ref="PostalCode"/>
                    <xsd:element ref="StateCode" minOccurs="0"/>
                    <xsd:element ref="CountryCode">
                      <xsd:annotation>
                        <xsd:documentation>ISO Country code. This element is introduced as mandatory although GDS implementation will not require its presence until 30MAR2008. Example: US</xsd:documentation>
                      </xsd:annotation>
                    </xsd:element>
                  </xsd:sequence>
                </xsd:complexType>
              </xsd:element>
            </xsd:sequence>
          </xsd:complexType>
        </xsd:element>
        <xsd:element name="Other">
          <xsd:annotation>
            <xsd:documentation>Other payment type. Possible values: CASH, CHECK.</xsd:documentation>
          </xsd:annotation>
          <xsd:simpleType>
            <xsd:restriction base="xsd:string">
              <xsd:enumeration value="CASH"/>
              <xsd:enumeration value="CHECK"/>
              <xsd:enumeration value=""/>
            </xsd:restriction>
          </xsd:simpleType>
        </xsd:element>
      </xsd:choice>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / FormOfPayment / FOPTotal
Namespace No namespace
Annotations
Total amount to be charged or refunded (negative amount) with this request against this FOP
Diagram
Diagram ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_FOPTotal_Total
Properties
content: complex
Attributes
QName Type Fixed Default Use Annotation
Total xsd:integer required
Total amount to be debited or credited (negative amount) with this request against this FOP.

Example: 10675
Source
<xsd:element name="FOPTotal">
  <xsd:annotation>
    <xsd:documentation>Total amount to be charged or refunded (negative amount) with this request against this FOP</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:attribute name="Total" type="xsd:integer" use="required">
      <xsd:annotation>
        <xsd:documentation>Total amount to be debited or credited (negative amount) with this request against this FOP. Example: 10675</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / FormOfPayment / PaymentReference
Namespace No namespace
Annotations
ONLY used if this request is a REFUND request.

This is a reference back to the original payment made (and required by some airlines)
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
minOccurs: 0
Facets
minLength 1
Source
<xsd:element name="PaymentReference" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>ONLY used if this request is a REFUND request. This is a reference back to the original payment made (and required by some airlines)</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / FormOfPayment / ServiceElementNumber
Namespace No namespace
Annotations
Element number of the service from the referenced PNR may be referenced directly to this FOP as well.  Note that any items mapped here must also be mapped under Traveler/ServiceElementNumber.

Example: 1
Diagram
Diagram
Properties
minOccurs: 0
maxOccurs: unbounded
Source
<xsd:element name="ServiceElementNumber" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>Element number of the service from the referenced PNR may be referenced directly to this FOP as well. Note that any items mapped here must also be mapped under Traveler/ServiceElementNumber. Example: 1</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / FormOfPayment / PreviousCredits
Namespace No namespace
Annotations
Reference to any credit available and to be applied to the payment requested with this transaction.

Any credit identified here is applied first, any remaining balance is then charged to credit card provided
Diagram
Diagram ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_PreviousCredits_CreditReference
Properties
content: complex
minOccurs: 0
Model CreditReference+
Children CreditReference
Instance
<PreviousCredits>
  <CreditReference BookingReference="" CreditAmount="">{1,unbounded}</CreditReference>
</PreviousCredits>
Source
<xsd:element name="PreviousCredits" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Reference to any credit available and to be applied to the payment requested with this transaction. Any credit identified here is applied first, any remaining balance is then charged to credit card provided</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="CreditReference" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>This can be a voucher, payment ID, credit reference or confirmation number associated to the amount listed under FOPTotal Example: 3665341</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="CreditAmount">
                <xsd:annotation>
                  <xsd:documentation>The amount of credit available. If entered, the amount is passed to vendor. An error response is possible if amount does not match amount of record</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
              <xsd:attribute name="BookingReference">
                <xsd:annotation>
                  <xsd:documentation>This could be an additional reference, e.g. RecLoc or confirmation number associated to this credit</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / FormOfPayment / PreviousCredits / CreditReference
Namespace No namespace
Annotations
This can be a voucher, payment ID, credit reference or confirmation number associated to the amount listed under FOPTotal

Example: 
3665341
Diagram
Diagram ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_PreviousCredits_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_PreviousCredits_CreditReference_CreditAmount ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_PreviousCredits_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_PreviousCredits_CreditReference_BookingReference
Type extension of xsd:string
Properties
content: complex
maxOccurs: unbounded
Attributes
QName Type Fixed Default Use Annotation
BookingReference optional
This could be an additional reference, e.g. RecLoc or confirmation number associated to this credit
CreditAmount optional
The amount of credit available.  If entered, the amount is passed to vendor.  An error response is possible if amount does not match amount of record
Source
<xsd:element name="CreditReference" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>This can be a voucher, payment ID, credit reference or confirmation number associated to the amount listed under FOPTotal Example: 3665341</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="CreditAmount">
          <xsd:annotation>
            <xsd:documentation>The amount of credit available. If entered, the amount is passed to vendor. An error response is possible if amount does not match amount of record</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
        <xsd:attribute name="BookingReference">
          <xsd:annotation>
            <xsd:documentation>This could be an additional reference, e.g. RecLoc or confirmation number associated to this credit</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / FormOfPayment / CreditCard
Namespace No namespace
Annotations
Credit card group
Diagram
Diagram ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_CreditCard_CCCode ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_CreditCard_CCNumber ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_CreditCard_CCExpiration ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_CreditCard_SecurityID ProcessPaymentRQ.tmp#Authorization ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_CreditCard_ApprovalCode ProcessPaymentRQ.tmp#CardholderFirstName ProcessPaymentRQ.tmp#CardholderLastName ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_CreditCard_CardholderFullName ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_CreditCard_CCAddressGroup
Properties
content: complex
Model CCCode , CCNumber , CCExpiration , SecurityID{0,1} , Authorization{0,1} , ApprovalCode{0,1} , ((CardholderFirstName{0,1} , CardholderLastName) | CardholderFullName) , CCAddressGroup{0,1}
Children ApprovalCode, Authorization, CCAddressGroup, CCCode, CCExpiration, CCNumber, CardholderFirstName, CardholderFullName, CardholderLastName, SecurityID
Instance
<CreditCard>
  <CCCode>{1,1}</CCCode>
  <CCNumber>{1,1}</CCNumber>
  <CCExpiration>{1,1}</CCExpiration>
  <SecurityID>{0,1}</SecurityID>
  <Authorization Type="">{0,1}</Authorization>
  <ApprovalCode>{0,1}</ApprovalCode>
  <CardholderFirstName>{0,1}</CardholderFirstName>
  <CardholderLastName>{1,1}</CardholderLastName>
  <CardholderFullName>{1,1}</CardholderFullName>
  <CCAddressGroup>{0,1}</CCAddressGroup>
</CreditCard>
Source
<xsd:element name="CreditCard">
  <xsd:annotation>
    <xsd:documentation>Credit card group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="CCCode">
        <xsd:annotation>
          <xsd:documentation>Credit card code. Example: VI</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:length value="2"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
      <xsd:element name="CCNumber" type="xsd:string">
        <xsd:annotation>
          <xsd:documentation>Credit card number. Example: 4011236654652341</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="CCExpiration">
        <xsd:annotation>
          <xsd:documentation>Credit card expiration group</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="Month">
              <xsd:annotation>
                <xsd:documentation>Credit card expiration month. Example: 02</xsd:documentation>
              </xsd:annotation>
              <xsd:simpleType>
                <xsd:restriction base="xsd:string">
                  <xsd:length value="2"/>
                </xsd:restriction>
              </xsd:simpleType>
            </xsd:element>
            <xsd:element name="Year">
              <xsd:annotation>
                <xsd:documentation>Last two digits of the credit card expiration year. Example: 06</xsd:documentation>
              </xsd:annotation>
              <xsd:simpleType>
                <xsd:restriction base="xsd:string">
                  <xsd:length value="2"/>
                  <xsd:pattern value="[0-9][0-9]"/>
                </xsd:restriction>
              </xsd:simpleType>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="SecurityID" type="xsd:string" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Credit card security number for online transactions (referred to also as CVV2, CVC2, CSC or CID). This is a 3-digit (Visa, Master, Discover) or 4-digit (Amex) number.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element ref="Authorization" minOccurs="0"/>
      <xsd:element name="ApprovalCode" type="xsd:string" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>MANUAL credit card approval code. If a code exists here no authorization request will be performed. Example: 996456</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:choice minOccurs="0">
        <xsd:sequence>
          <xsd:element ref="CardholderFirstName" minOccurs="0"/>
          <xsd:element ref="CardholderLastName"/>
        </xsd:sequence>
        <xsd:element name="CardholderFullName">
          <xsd:annotation>
            <xsd:documentation>Credit cardholder full name as it appears on the card</xsd:documentation>
          </xsd:annotation>
          <xsd:simpleType>
            <xsd:restriction base="xsd:string">
              <xsd:minLength value="1"/>
            </xsd:restriction>
          </xsd:simpleType>
        </xsd:element>
      </xsd:choice>
      <xsd:element name="CCAddressGroup" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Card holders address</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element ref="Address" maxOccurs="2"/>
            <xsd:element ref="City"/>
            <xsd:element ref="PostalCode"/>
            <xsd:element ref="StateCode" minOccurs="0"/>
            <xsd:element ref="CountryCode">
              <xsd:annotation>
                <xsd:documentation>ISO Country code. This element is introduced as mandatory although GDS implementation will not require its presence until 30MAR2008. Example: US</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / FormOfPayment / CreditCard / CCCode
Namespace No namespace
Annotations
Credit card code.  Example: VI
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
length 2
Source
<xsd:element name="CCCode">
  <xsd:annotation>
    <xsd:documentation>Credit card code. Example: VI</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="2"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / FormOfPayment / CreditCard / CCNumber
Namespace No namespace
Annotations
Credit card number.  Example: 4011236654652341
Diagram
Diagram
Type xsd:string
Properties
content: simple
Source
<xsd:element name="CCNumber" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Credit card number. Example: 4011236654652341</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / FormOfPayment / CreditCard / CCExpiration
Namespace No namespace
Annotations
Credit card expiration group
Diagram
Diagram ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_CreditCard_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_CreditCard_CCExpiration_Month ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_CreditCard_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_ProcessPaymentRQ_ProcessPaymentRQ_FormOfPayment_CreditCard_CCExpiration_Year
Properties
content: complex
Model Month , Year
Children Month, Year
Instance
<CCExpiration>
  <Month>{1,1}</Month>
  <Year>{1,1}</Year>
</CCExpiration>
Source
<xsd:element name="CCExpiration">
  <xsd:annotation>
    <xsd:documentation>Credit card expiration group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Month">
        <xsd:annotation>
          <xsd:documentation>Credit card expiration month. Example: 02</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:length value="2"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
      <xsd:element name="Year">
        <xsd:annotation>
          <xsd:documentation>Last two digits of the credit card expiration year. Example: 06</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:length value="2"/>
            <xsd:pattern value="[0-9][0-9]"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / FormOfPayment / CreditCard / CCExpiration / Month
Namespace No namespace
Annotations
Credit card expiration month.  Example: 02
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
length 2
Source
<xsd:element name="Month">
  <xsd:annotation>
    <xsd:documentation>Credit card expiration month. Example: 02</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="2"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / FormOfPayment / CreditCard / CCExpiration / Year
Namespace No namespace
Annotations
Last two digits of the credit card expiration year.  Example: 06
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
length 2
pattern [0-9][0-9]
Source
<xsd:element name="Year">
  <xsd:annotation>
    <xsd:documentation>Last two digits of the credit card expiration year. Example: 06</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="2"/>
      <xsd:pattern value="[0-9][0-9]"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / FormOfPayment / CreditCard / SecurityID
Namespace No namespace
Annotations
Credit card security number for online transactions (referred to also as CVV2, CVC2, CSC or CID). This is a 3-digit (Visa, Master, Discover) or 4-digit (Amex) number.
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="SecurityID" type="xsd:string" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Credit card security number for online transactions (referred to also as CVV2, CVC2, CSC or CID). This is a 3-digit (Visa, Master, Discover) or 4-digit (Amex) number.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Authorization
Namespace No namespace
Annotations
Credit card authorization
Diagram
Diagram ProcessPaymentRQ.tmp#Authorization_Type ProcessPaymentRQ.tmp#Authorization_MerchantCode
Properties
content: complex
Used by
Model MerchantCode
Children MerchantCode
Instance
<Authorization Type="">
  <MerchantCode>{1,1}</MerchantCode>
</Authorization>
Attributes
QName Type Fixed Default Use Annotation
Type restriction of xsd:string required
Credit card authorization type. Values are: 
A = request authorization only
S = request authorization and store returned approval code in the PNR 
D = request authorization and verify the address associated with this credit card; store the verification status and approval code in PNR. If no address associated - error message will be returned. 

Example: A
Source
<xsd:element name="Authorization">
  <xsd:annotation>
    <xsd:documentation>Credit card authorization</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="MerchantCode">
        <xsd:annotation>
          <xsd:documentation>Merchant ID. This is the merchant ID needed when authorization/card verification is incolved. This can be an airline, agency or 3rd party merchant ID/number Note: not needed if the merchant processes authprization.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="Type" use="required">
      <xsd:annotation>
        <xsd:documentation>Credit card authorization type. Values are: A = request authorization only S = request authorization and store returned approval code in the PNR D = request authorization and verify the address associated with this credit card; store the verification status and approval code in PNR. If no address associated - error message will be returned. Example: A</xsd:documentation>
      </xsd:annotation>
      <xsd:simpleType>
        <xsd:restriction base="xsd:string">
          <xsd:length value="1"/>
          <xsd:enumeration value="A"/>
          <xsd:enumeration value="S"/>
          <xsd:enumeration value="D"/>
        </xsd:restriction>
      </xsd:simpleType>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Authorization / MerchantCode
Namespace No namespace
Annotations
Merchant ID.  This is the merchant ID needed when authorization/card verification is incolved.

This can be an airline, agency or 3rd party merchant ID/number

Note: not needed if the merchant processes authprization.
Diagram
Diagram
Source
<xsd:element name="MerchantCode">
  <xsd:annotation>
    <xsd:documentation>Merchant ID. This is the merchant ID needed when authorization/card verification is incolved. This can be an airline, agency or 3rd party merchant ID/number Note: not needed if the merchant processes authprization.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / FormOfPayment / CreditCard / ApprovalCode
Namespace No namespace
Annotations
MANUAL credit card approval code.  

If a code exists here no authorization request will be performed.

Example: 996456
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="ApprovalCode" type="xsd:string" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>MANUAL credit card approval code. If a code exists here no authorization request will be performed. Example: 996456</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element CardholderFirstName
Namespace No namespace
Annotations
Credit card holder's first name.  Example: JOHN
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
Used by
Source
<xsd:element name="CardholderFirstName">
  <xsd:annotation>
    <xsd:documentation>Credit card holder's first name. Example: JOHN</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element CardholderLastName
Namespace No namespace
Annotations
Credit card holder's last name.  This is only required for Sabre.  Example: SMITH
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
Used by
Source
<xsd:element name="CardholderLastName">
  <xsd:annotation>
    <xsd:documentation>Credit card holder's last name. This is only required for Sabre. Example: SMITH</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / FormOfPayment / CreditCard / CardholderFullName
Namespace No namespace
Annotations
Credit cardholder full name as it appears on the card
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
Source
<xsd:element name="CardholderFullName">
  <xsd:annotation>
    <xsd:documentation>Credit cardholder full name as it appears on the card</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / FormOfPayment / CreditCard / CCAddressGroup
Namespace No namespace
Annotations
Card holders address
Diagram
Diagram ProcessPaymentRQ.tmp#Address ProcessPaymentRQ.tmp#City ProcessPaymentRQ.tmp#PostalCode ProcessPaymentRQ.tmp#StateCode ProcessPaymentRQ.tmp#CountryCode
Properties
content: complex
minOccurs: 0
Model Address{1,2} , City , PostalCode , StateCode{0,1} , CountryCode
Children Address, City, CountryCode, PostalCode, StateCode
Instance
<CCAddressGroup>
  <Address>{1,2}</Address>
  <City>{1,1}</City>
  <PostalCode>{1,1}</PostalCode>
  <StateCode>{0,1}</StateCode>
  <CountryCode>{1,1}</CountryCode>
</CCAddressGroup>
Source
<xsd:element name="CCAddressGroup" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Card holders address</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="Address" maxOccurs="2"/>
      <xsd:element ref="City"/>
      <xsd:element ref="PostalCode"/>
      <xsd:element ref="StateCode" minOccurs="0"/>
      <xsd:element ref="CountryCode">
        <xsd:annotation>
          <xsd:documentation>ISO Country code. This element is introduced as mandatory although GDS implementation will not require its presence until 30MAR2008. Example: US</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Address
Namespace No namespace
Annotations
Street or PO Box address.  Example: 1234 Main Street
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 2
Used by
Source
<xsd:element name="Address">
  <xsd:annotation>
    <xsd:documentation>Street or PO Box address. Example: 1234 Main Street</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="2"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element City
Namespace No namespace
Annotations
City name.  Example: NY
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 2
Used by
Source
<xsd:element name="City">
  <xsd:annotation>
    <xsd:documentation>City name. Example: NY</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="2"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element PostalCode
Namespace No namespace
Annotations
Postal code or zip code.  Example: 12345
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 2
Used by
Source
<xsd:element name="PostalCode">
  <xsd:annotation>
    <xsd:documentation>Postal code or zip code. Example: 12345</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="2"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element StateCode
Namespace No namespace
Annotations
State code.  Example: NY
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 2
Used by
Source
<xsd:element name="StateCode">
  <xsd:annotation>
    <xsd:documentation>State code. Example: NY</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="2"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element CountryCode
Namespace No namespace
Annotations
Country code.  Example: US
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 2
maxLength 2
Used by
Source
<xsd:element name="CountryCode">
  <xsd:annotation>
    <xsd:documentation>Country code. Example: US</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:maxLength value="2"/>
      <xsd:minLength value="2"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / FormOfPayment / Other
Namespace No namespace
Annotations
Other payment type. Possible values: CASH, CHECK.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
enumeration CASH
enumeration CHECK
enumeration
Source
<xsd:element name="Other">
  <xsd:annotation>
    <xsd:documentation>Other payment type. Possible values: CASH, CHECK.</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:enumeration value="CASH"/>
      <xsd:enumeration value="CHECK"/>
      <xsd:enumeration value=""/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element ProcessPaymentRQ / PymtTotal
Namespace No namespace
Annotations
Total amount to be charged or refunded with this request (sum of all FOPs)
Diagram
Diagram ProcessPaymentRQ.tmp#ProcessPaymentRQ_ProcessPaymentRQ_PymtTotal_Total
Properties
content: complex
minOccurs: 0
Attributes
QName Type Fixed Default Use Annotation
Total xsd:integer optional
Total amount to be debited or credited with this request.

Example: 10675
Source
<xsd:element name="PymtTotal" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Total amount to be charged or refunded with this request (sum of all FOPs)</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:attribute name="Total" type="xsd:integer">
      <xsd:annotation>
        <xsd:documentation>Total amount to be debited or credited with this request. Example: 10675</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Amount
Namespace No namespace
Annotations
Monetary amount.  This is the real amount without the decimal point.  An amount of 7500 means 75.00 if Currency Code has 2 decimals. 

Example:  100
Diagram
Diagram
Type xsd:integer
Properties
content: simple
Source
<xsd:element name="Amount" type="xsd:integer">
  <xsd:annotation>
    <xsd:documentation>Monetary amount. This is the real amount without the decimal point. An amount of 7500 means 75.00 if Currency Code has 2 decimals. Example: 100</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element ForInfo
Namespace No namespace
Annotations
Information group
Diagram
Diagram ProcessPaymentRQ.tmp#Source ProcessPaymentRQ.tmp#SourceRef ProcessPaymentRQ.tmp#Text
Properties
content: complex
Used by
Element InfoGroup
Model Text+
Children Text
Instance
<ForInfo Source="" SourceRef="">
  <Text>{1,unbounded}</Text>
</ForInfo>
Attributes
QName Type Fixed Default Use Annotation
Source restriction of xsd:string optional
Identifies the source of this  element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. Example: 1A, 1V, or other.
SourceRef restriction of xsd:string optional
PNR Record Locator associated to Source attribute.
Source
<xsd:element name="ForInfo">
  <xsd:annotation>
    <xsd:documentation>Information group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="Text" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>Information text or error text. Example: Free flow text. Example: Invalid flight number</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute ref="Source" use="optional">
      <xsd:annotation>
        <xsd:documentation>Identifies the source of this element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. Example: 1A, 1V, or other.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute ref="SourceRef" use="optional"/>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Text
Namespace No namespace
Annotations
Information text or error text. Example: Free flow text.
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Elements Error, ForInfo
Source
<xsd:element name="Text" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Information text or error text. Example: Free flow text.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Error
Namespace No namespace
Annotations
Error group
Diagram
Diagram ProcessPaymentRQ.tmp#Error_ErrorType ProcessPaymentRQ.tmp#Source ProcessPaymentRQ.tmp#SourceRef ProcessPaymentRQ.tmp#Code ProcessPaymentRQ.tmp#Text ProcessPaymentRQ.tmp#CustomRequest
Properties
content: complex
Used by
Element InfoGroup
Model Code{0,1} , Text+ , CustomRequest{0,1}
Children Code, CustomRequest, Text
Instance
<Error ErrorType="" Source="" SourceRef="">
  <Code>{0,1}</Code>
  <Text>{1,unbounded}</Text>
  <CustomRequest>{0,1}</CustomRequest>
</Error>
Attributes
QName Type Fixed Default Use Annotation
ErrorType xsd:string required
Type of error.  Example: Air
Source restriction of xsd:string optional
Identifies the source of this  element. In other words where the content originates from. Not limited to GDS, applicable to direct connect as well. Example: 1A, 1V, or other.
SourceRef restriction of xsd:string optional
PNR Record Locator associated to Source attribute.
Source
<xsd:element name="Error">
  <xsd:annotation>
    <xsd:documentation>Error group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="Code" minOccurs="0"/>
      <xsd:element ref="Text" maxOccurs="unbounded"/>
      <xsd:element ref="CustomRequest" minOccurs="0"/>
    </xsd:sequence>
    <xsd:attribute name="ErrorType" type="xsd:string" use="required">
      <xsd:annotation>
        <xsd:documentation>Type of error. Example: Air</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute ref="Source"/>
    <xsd:attribute ref="SourceRef"/>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Code
Namespace No namespace
Annotations
Error code or equipment type code.  Example: 0104 (error code), 747 (equipment code)
Diagram
Diagram
Type xsd:string
Properties
content: simple
Used by
Element Error
Source
<xsd:element name="Code" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Error code or equipment type code. Example: 0104 (error code), 747 (equipment code)</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element CustomRequest
Namespace No namespace
Annotations
Mostly used when source specific additional input is needed and/or when QC (Quality Control) edits are processed and the POS needs instructions/options how to proceed.

Multiple sources may return a separate 'Error' node with their own CustomRequest request.

the UI must display one screen at a time and respond to each with a separate message.
Diagram
Diagram ProcessPaymentRQ.tmp#CustomRequest_DialogTitle ProcessPaymentRQ.tmp#CustomRequest_Instructions ProcessPaymentRQ.tmp#Control ProcessPaymentRQ.tmp#CustomRequest_Button ProcessPaymentRQ.tmp#CustomRequest_OrigMsg ProcessPaymentRQ.tmp#CustomRequest_Reference
Properties
content: complex
Used by
Element Error
Model DialogTitle , Instructions{0,1} , Control+ , Button+ , OrigMsg , Reference{0,1}
Children Button, Control, DialogTitle, Instructions, OrigMsg, Reference
Instance
<CustomRequest>
  <DialogTitle>{1,1}</DialogTitle>
  <Instructions>{0,1}</Instructions>
  <Control GUILabel="" Mandatory="" MaxChar="" MinChar="" MouseOverText="" Pattern="" PNRLabel="" SameLine="" Type="" Width="">{1,unbounded}</Control>
  <Button ButtonLabel="" MouseOverText="" Validate="" Width="">{1,unbounded}</Button>
  <OrigMsg>{1,1}</OrigMsg>
  <Reference>{0,1}</Reference>
</CustomRequest>
Source
<xsd:element name="CustomRequest">
  <xsd:annotation>
    <xsd:documentation>Mostly used when source specific additional input is needed and/or when QC (Quality Control) edits are processed and the POS needs instructions/options how to proceed. Multiple sources may return a separate 'Error' node with their own CustomRequest request. the UI must display one screen at a time and respond to each with a separate message.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="DialogTitle">
        <xsd:annotation>
          <xsd:documentation>Freeflow Text to be displayed in the Title Bar of the pop-up window</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="Instructions" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Freeflow lines of text to be displayed inside of the pop-up window to explain or instruct the user of the necessary action(s)</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:sequence>
            <xsd:element name="Text" maxOccurs="unbounded">
              <xsd:annotation>
                <xsd:documentation>Individual line of freeflow text</xsd:documentation>
              </xsd:annotation>
            </xsd:element>
          </xsd:sequence>
        </xsd:complexType>
      </xsd:element>
      <xsd:element ref="Control" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>Control(s) needed for this pop-up. Important: The UI is asked to build the Pop-Up controls in sequential order. Possible types are: TextBox ListBox DropDown w/values ComboBox OptionGroup CheckBox DateInput TimeInput TextArea</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="Button" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>The 1st button defined will be the default button for the window. All buttons will be positioned at the bottom of the forms and arranged from left to right (centered)</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:attribute name="ButtonLabel" use="required">
            <xsd:annotation>
              <xsd:documentation>The label to be used for the button. Example: Submit</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
          <xsd:attribute name="Validate">
            <xsd:annotation>
              <xsd:documentation>Possible values Y or N (default) If "Y" this button will trigger the validation needed by the GUI prior to processing the screen. Note: Only a single button can have this attribute set to "Y". If multiple, the first instance will be used.</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
          <xsd:attribute name="MouseOverText">
            <xsd:annotation>
              <xsd:documentation>Freeflow informational text designed to use as a 'mouseover' text or similar</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
          <xsd:attribute name="Width">
            <xsd:annotation>
              <xsd:documentation>GUI normally autosizes based on width of label. A certain width may be defined here in pixels.</xsd:documentation>
            </xsd:annotation>
          </xsd:attribute>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="OrigMsg" type="MessageStructure">
        <xsd:annotation>
          <xsd:documentation>This is the message originally received by Company</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="Reference" type="MessageStructure" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Reference node to be returned with CustomResponse node - mostly used as a linking reference between CustomRequest and CustomResponse</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element CustomRequest / DialogTitle
Namespace No namespace
Annotations
Freeflow Text to be displayed in the Title Bar of the pop-up window
Diagram
Diagram
Source
<xsd:element name="DialogTitle">
  <xsd:annotation>
    <xsd:documentation>Freeflow Text to be displayed in the Title Bar of the pop-up window</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element CustomRequest / Instructions
Namespace No namespace
Annotations
Freeflow lines of text to be displayed inside of the pop-up window to explain or instruct the user of the necessary action(s)
Diagram
Diagram ProcessPaymentRQ.tmp#CustomRequest_CustomRequest_Instructions_Text
Properties
content: complex
minOccurs: 0
Model Text+
Children Text
Instance
<Instructions>
  <Text>{1,unbounded}</Text>
</Instructions>
Source
<xsd:element name="Instructions" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Freeflow lines of text to be displayed inside of the pop-up window to explain or instruct the user of the necessary action(s)</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Text" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>Individual line of freeflow text</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element CustomRequest / Instructions / Text
Namespace No namespace
Annotations
Individual line of freeflow text
Diagram
Diagram
Properties
maxOccurs: unbounded
Source
<xsd:element name="Text" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>Individual line of freeflow text</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element Control
Namespace No namespace
Annotations
The control(s) needed for this pop-up.a) Textbox

Possible types are:
a) TextBox
b) DropDown w/values
c) OptionGroup
Diagram
Diagram ProcessPaymentRQ.tmp#Control_Type ProcessPaymentRQ.tmp#Control_GUILabel ProcessPaymentRQ.tmp#Control_PNRLabel ProcessPaymentRQ.tmp#Control_MouseOverText ProcessPaymentRQ.tmp#Control_Mandatory ProcessPaymentRQ.tmp#Control_Width ProcessPaymentRQ.tmp#Control_SameLine ProcessPaymentRQ.tmp#Control_Pattern ProcessPaymentRQ.tmp#Control_MinChar ProcessPaymentRQ.tmp#Control_MaxChar ProcessPaymentRQ.tmp#Control_Value
Properties
content: complex
Used by
Element CustomRequest
Model Value*
Children Value
Instance
<Control GUILabel="" Mandatory="" MaxChar="" MinChar="" MouseOverText="" Pattern="" PNRLabel="" SameLine="" Type="" Width="">
  <Value>{0,unbounded}</Value>
</Control>
Attributes
QName Type Fixed Default Use Annotation
GUILabel required
Label to describe this control. 
This label is usually placed in front or above the respective control. In case of a 'Button' it is the name of the button.
Mandatory optional
Allowed Values: Y or N

If 'Y' the UI needs to identify the control as mandatory input/selection, e.g. with an asteriks or different colored background
MaxChar optional
Maximum characters
MinChar optional
Minimum characters
MouseOverText optional
Freeflow informational text designed to use as a 'mouseover' text or similar
PNRLabel required
Description to be used to enter the returned value into a PNR General Remark element, if needed or desired.

This label is usually placed in front of the returned value as remark text.

Example:
"ProjectID: 105514"
Pattern optional
use a regular expression string
SameLine optional
Allowed Values: Y or N

If 'Y' the UI needs to position this control to the right of and on the same line as the preceding control.
Type required
Possible Values:

TextBox
ListBox
DropDown w/values
ComboBox
OptionGroup(radio)
CheckBox
DateInput
TimeInput
TextArea
Width optional
Width in pixels
Source
<xsd:element name="Control">
  <xsd:annotation>
    <xsd:documentation>The control(s) needed for this pop-up.a) Textbox Possible types are: a) TextBox b) DropDown w/values c) OptionGroup</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Value" minOccurs="0" maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>Applicable to these control types: ListBox DropDown ComboBox OptionGroup CheckBox The provided values are used to provide a dynamically built list and/or single choice (OptionGroup) or multi-choice (CheckBox) labels. In case of 'OptionGroup' and 'CheckBox' the value is the description/label for each checkbox or radio button.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
    <xsd:attribute name="Type" use="required">
      <xsd:annotation>
        <xsd:documentation>Possible Values: TextBox ListBox DropDown w/values ComboBox OptionGroup(radio) CheckBox DateInput TimeInput TextArea</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="GUILabel" use="required">
      <xsd:annotation>
        <xsd:documentation>Label to describe this control. This label is usually placed in front or above the respective control. In case of a 'Button' it is the name of the button.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="PNRLabel" use="required">
      <xsd:annotation>
        <xsd:documentation>Description to be used to enter the returned value into a PNR General Remark element, if needed or desired. This label is usually placed in front of the returned value as remark text. Example: "ProjectID: 105514"</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="MouseOverText">
      <xsd:annotation>
        <xsd:documentation>Freeflow informational text designed to use as a 'mouseover' text or similar</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="Mandatory">
      <xsd:annotation>
        <xsd:documentation>Allowed Values: Y or N If 'Y' the UI needs to identify the control as mandatory input/selection, e.g. with an asteriks or different colored background</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="Width">
      <xsd:annotation>
        <xsd:documentation>Width in pixels</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="SameLine">
      <xsd:annotation>
        <xsd:documentation>Allowed Values: Y or N If 'Y' the UI needs to position this control to the right of and on the same line as the preceding control.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="Pattern">
      <xsd:annotation>
        <xsd:documentation>use a regular expression string</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="MinChar">
      <xsd:annotation>
        <xsd:documentation>Minimum characters</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="MaxChar">
      <xsd:annotation>
        <xsd:documentation>Maximum characters</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Control / Value
Namespace No namespace
Annotations
Applicable to these control types:

ListBox
DropDown
ComboBox
OptionGroup
CheckBox

The provided values are used to provide a dynamically built list and/or single choice (OptionGroup) or multi-choice (CheckBox) labels.

In case of 'OptionGroup' and 'CheckBox' the value is the description/label for each checkbox or radio button.
Diagram
Diagram
Properties
minOccurs: 0
maxOccurs: unbounded
Source
<xsd:element name="Value" minOccurs="0" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>Applicable to these control types: ListBox DropDown ComboBox OptionGroup CheckBox The provided values are used to provide a dynamically built list and/or single choice (OptionGroup) or multi-choice (CheckBox) labels. In case of 'OptionGroup' and 'CheckBox' the value is the description/label for each checkbox or radio button.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element CustomRequest / Button
Namespace No namespace
Annotations
The 1st button defined will be the default button for the window.

All buttons will be positioned at the bottom of the forms and arranged from left to right (centered)
Diagram
Diagram ProcessPaymentRQ.tmp#CustomRequest_CustomRequest_Button_ButtonLabel ProcessPaymentRQ.tmp#CustomRequest_CustomRequest_Button_Validate ProcessPaymentRQ.tmp#CustomRequest_CustomRequest_Button_MouseOverText ProcessPaymentRQ.tmp#CustomRequest_CustomRequest_Button_Width
Properties
content: complex
maxOccurs: unbounded
Attributes
QName Type Fixed Default Use Annotation
ButtonLabel required
The label to be used for the button.

Example: Submit
MouseOverText optional
Freeflow informational text designed to use as a 'mouseover' text or similar
Validate optional
Possible values Y or N (default)

If "Y" this button will trigger the validation needed by the GUI prior to processing the screen.

Note:  Only a single button can have this attribute set to "Y".  If multiple, the first instance will be used.
Width optional
GUI normally autosizes based on width of label.  A certain width may be defined here in pixels.
Source
<xsd:element name="Button" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>The 1st button defined will be the default button for the window. All buttons will be positioned at the bottom of the forms and arranged from left to right (centered)</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:attribute name="ButtonLabel" use="required">
      <xsd:annotation>
        <xsd:documentation>The label to be used for the button. Example: Submit</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="Validate">
      <xsd:annotation>
        <xsd:documentation>Possible values Y or N (default) If "Y" this button will trigger the validation needed by the GUI prior to processing the screen. Note: Only a single button can have this attribute set to "Y". If multiple, the first instance will be used.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="MouseOverText">
      <xsd:annotation>
        <xsd:documentation>Freeflow informational text designed to use as a 'mouseover' text or similar</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
    <xsd:attribute name="Width">
      <xsd:annotation>
        <xsd:documentation>GUI normally autosizes based on width of label. A certain width may be defined here in pixels.</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element CustomRequest / OrigMsg
Namespace No namespace
Annotations
This is the message originally received by Company
Diagram
Diagram ProcessPaymentRQ.tmp#MessageStructure
Type MessageStructure
Properties
content: complex
Model ANY element from ANY namespace
Attributes
QName Type Fixed Default Use Annotation
ANY attribute from ANY namespace
Source
<xsd:element name="OrigMsg" type="MessageStructure">
  <xsd:annotation>
    <xsd:documentation>This is the message originally received by Company</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element CustomRequest / Reference
Namespace No namespace
Annotations
Reference node to be returned with CustomResponse node - mostly used as a linking reference between CustomRequest and CustomResponse
Diagram
Diagram ProcessPaymentRQ.tmp#MessageStructure
Type MessageStructure
Properties
content: complex
minOccurs: 0
Model ANY element from ANY namespace
Attributes
QName Type Fixed Default Use Annotation
ANY attribute from ANY namespace
Source
<xsd:element name="Reference" type="MessageStructure" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Reference node to be returned with CustomResponse node - mostly used as a linking reference between CustomRequest and CustomResponse</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element InfoGroup
Namespace No namespace
Annotations
Error and information group
Diagram
Diagram ProcessPaymentRQ.tmp#ForInfo ProcessPaymentRQ.tmp#Error
Properties
content: complex
Model ForInfo{0,1} , Error*
Children Error, ForInfo
Instance
<InfoGroup>
  <ForInfo Source="" SourceRef="">{0,1}</ForInfo>
  <Error ErrorType="" Source="" SourceRef="">{0,unbounded}</Error>
</InfoGroup>
Source
<xsd:element name="InfoGroup">
  <xsd:annotation>
    <xsd:documentation>Error and information group</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element ref="ForInfo" minOccurs="0"/>
      <xsd:element ref="Error" minOccurs="0" maxOccurs="unbounded"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FiledIn
Namespace No namespace
Annotations
This group represents fares filed in a currency different from the currency of a point of sale. The content elements represent the original currency and amount as filed.
Diagram
Diagram ProcessPaymentRQ.tmp#CurrencyCode ProcessPaymentRQ.tmp#FiledIn_Amount
Properties
content: complex
Used by
Complex Type BaseFareType
Model ALL(CurrencyCode Amount)
Children Amount, CurrencyCode
Instance
<FiledIn>
  <CurrencyCode NumberOfDecimals="">{1,1}</CurrencyCode>
  <Amount BulkMask="">{1,1}</Amount>
</FiledIn>
Source
<xsd:element name="FiledIn">
  <xsd:annotation>
    <xsd:documentation>This group represents fares filed in a currency different from the currency of a point of sale. The content elements represent the original currency and amount as filed.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:all>
      <xsd:element ref="CurrencyCode"/>
      <xsd:element name="Amount">
        <xsd:annotation>
          <xsd:documentation>Base Fare Amount as originally filed.</xsd:documentation>
        </xsd:annotation>
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:integer">
              <xsd:attribute name="BulkMask">
                <xsd:annotation>
                  <xsd:documentation>This mask applies to IT/BT tickets where the masked value may be "BT" or "IT" instead of the true amount. Note: this mask is ALWAYS used for the passenger ticket image.</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
    </xsd:all>
  </xsd:complexType>
</xsd:element>
[ top ]
Element CurrencyCode
Namespace No namespace
Annotations
Currency code.  Example: USD
Diagram
Diagram ProcessPaymentRQ.tmp#CurrencyCodeType_NumberOfDecimals ProcessPaymentRQ.tmp#CurrencyCodeType ProcessPaymentRQ.tmp#CurrencyCode_NumberOfDecimals
Type restriction of CurrencyCodeType
Type hierarchy
Properties
content: complex
Used by
Element FiledIn
Attributes
QName Type Fixed Default Use Annotation
NumberOfDecimals xsd:integer required
Decimal position in fare amount.  Example: 2
Source
<xsd:element name="CurrencyCode">
  <xsd:annotation>
    <xsd:documentation>Currency code. Example: USD</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:restriction base="CurrencyCodeType">
        <xsd:pattern value="[A-Z0-9]{3}"/>
        <xsd:attribute name="NumberOfDecimals" type="xsd:integer" use="required">
          <xsd:annotation>
            <xsd:documentation>Decimal position in fare amount. Example: 2</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:restriction>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element FiledIn / Amount
Namespace No namespace
Annotations
Base Fare Amount as originally filed.
Diagram
Diagram ProcessPaymentRQ.tmp#FiledIn_FiledIn_Amount_BulkMask
Type extension of xsd:integer
Properties
content: complex
Attributes
QName Type Fixed Default Use Annotation
BulkMask optional
This mask applies to IT/BT tickets where the masked value may be "BT" or "IT" instead of the true amount.

Note: this mask is ALWAYS used for the passenger ticket image.
Source
<xsd:element name="Amount">
  <xsd:annotation>
    <xsd:documentation>Base Fare Amount as originally filed.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:integer">
        <xsd:attribute name="BulkMask">
          <xsd:annotation>
            <xsd:documentation>This mask applies to IT/BT tickets where the masked value may be "BT" or "IT" instead of the true amount. Note: this mask is ALWAYS used for the passenger ticket image.</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element NVA
Namespace No namespace
Annotations
Identifies "not valid after" date for a fare.Date in ISO 8601 format (yyyy-mm-dd).  Example: 2001-12-25
Diagram
Diagram
Type xsd:date
Properties
content: simple
Source
<xsd:element name="NVA" type="xsd:date">
  <xsd:annotation>
    <xsd:documentation>Identifies "not valid after" date for a fare.Date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element NVB
Namespace No namespace
Annotations
Identifies "not valid befoe" date for a fare. Date in ISO 8601 format (yyyy-mm-dd).  Example: 2001-12-25
Diagram
Diagram
Type xsd:date
Properties
content: simple
Source
<xsd:element name="NVB" type="xsd:date">
  <xsd:annotation>
    <xsd:documentation>Identifies "not valid befoe" date for a fare. Date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element HistoricalPricingInfo
Namespace No namespace
Annotations
DEPRECATED.
Please use definitions in PricingInfo: ReservationsDateTime, HistoricPricingDate, AltTicketingDate.

Historical pricing group. Required if OriginDestination group includes past date segments.
Diagram
Diagram ProcessPaymentRQ.tmp#HistoricalPricingInfo_ReservationDateTime ProcessPaymentRQ.tmp#HistoricalPricingInfo_TicketedDateTime ProcessPaymentRQ.tmp#HistoricalPricingInfo_RecordLocator
Properties
content: complex
Model (ReservationDateTime{0,1} , TicketedDateTime) | RecordLocator{0,0}
Children RecordLocator, ReservationDateTime, TicketedDateTime
Instance
<HistoricalPricingInfo>
  <ReservationDateTime>{0,1}</ReservationDateTime>
  <TicketedDateTime>{1,1}</TicketedDateTime>
  <RecordLocator>{0,0}</RecordLocator>
</HistoricalPricingInfo>
Source
<xsd:element name="HistoricalPricingInfo">
  <xsd:annotation>
    <xsd:documentation>DEPRECATED. Please use definitions in PricingInfo: ReservationsDateTime, HistoricPricingDate, AltTicketingDate. Historical pricing group. Required if OriginDestination group includes past date segments.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:choice>
      <xsd:sequence>
        <xsd:element name="ReservationDateTime" minOccurs="0">
          <xsd:annotation>
            <xsd:documentation>This timestamp indetifies when PNR was created client application requests historical pricing for.</xsd:documentation>
          </xsd:annotation>
          <xsd:complexType>
            <xsd:sequence>
              <xsd:element name="Date" type="Date">
                <xsd:annotation>
                  <xsd:documentation>Specifies departure or arrival date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
                </xsd:annotation>
              </xsd:element>
              <xsd:element name="Time" type="Time" minOccurs="0">
                <xsd:annotation>
                  <xsd:documentation>Departure or arrival time in ISO 8601 twenty-four hour clock format. Example: 14:00</xsd:documentation>
                </xsd:annotation>
              </xsd:element>
            </xsd:sequence>
          </xsd:complexType>
        </xsd:element>
        <xsd:element name="TicketedDateTime">
          <xsd:annotation>
            <xsd:documentation>Timestamp of ticket issuance for past date segments in OriginDestination section.</xsd:documentation>
          </xsd:annotation>
          <xsd:complexType>
            <xsd:sequence>
              <xsd:element name="Date" type="Date">
                <xsd:annotation>
                  <xsd:documentation>Specifies departure or arrival date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
                </xsd:annotation>
              </xsd:element>
              <xsd:element name="Time" type="Time" minOccurs="0">
                <xsd:annotation>
                  <xsd:documentation>Departure or arrival time in ISO 8601 twenty-four hour clock format. Example: 14:00</xsd:documentation>
                </xsd:annotation>
              </xsd:element>
            </xsd:sequence>
          </xsd:complexType>
        </xsd:element>
      </xsd:sequence>
      <xsd:element name="RecordLocator" type="xsd:string" minOccurs="0" maxOccurs="0">
        <xsd:annotation>
          <xsd:documentation>FUTURE USE. NOT SUPPORTED.</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:choice>
  </xsd:complexType>
</xsd:element>
[ top ]
Element HistoricalPricingInfo / ReservationDateTime
Namespace No namespace
Annotations
This timestamp indetifies when PNR was created client application requests historical pricing for.
Diagram
Diagram ProcessPaymentRQ.tmp#HistoricalPricingInfo_HistoricalPricingInfo_ReservationDateTime_Date ProcessPaymentRQ.tmp#HistoricalPricingInfo_HistoricalPricingInfo_ReservationDateTime_Time
Properties
content: complex
minOccurs: 0
Model Date , Time{0,1}
Children Date, Time
Instance
<ReservationDateTime>
  <Date>{1,1}</Date>
  <Time>{0,1}</Time>
</ReservationDateTime>
Source
<xsd:element name="ReservationDateTime" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>This timestamp indetifies when PNR was created client application requests historical pricing for.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Date" type="Date">
        <xsd:annotation>
          <xsd:documentation>Specifies departure or arrival date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="Time" type="Time" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Departure or arrival time in ISO 8601 twenty-four hour clock format. Example: 14:00</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element HistoricalPricingInfo / ReservationDateTime / Date
Namespace No namespace
Annotations
Specifies departure or arrival date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25
Diagram
Diagram ProcessPaymentRQ.tmp#Date
Type Date
Properties
content: simple
Source
<xsd:element name="Date" type="Date">
  <xsd:annotation>
    <xsd:documentation>Specifies departure or arrival date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element HistoricalPricingInfo / ReservationDateTime / Time
Namespace No namespace
Annotations
Departure or arrival time in ISO 8601 twenty-four hour clock format. Example: 14:00
Diagram
Diagram ProcessPaymentRQ.tmp#Time
Type Time
Properties
content: simple
minOccurs: 0
Facets
length 5
pattern ([0-1][0-9]|2[0-3]):[0-5][0-9]
Source
<xsd:element name="Time" type="Time" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Departure or arrival time in ISO 8601 twenty-four hour clock format. Example: 14:00</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element HistoricalPricingInfo / TicketedDateTime
Namespace No namespace
Annotations
Timestamp of ticket issuance  for past date segments in OriginDestination section.
Diagram
Diagram ProcessPaymentRQ.tmp#HistoricalPricingInfo_HistoricalPricingInfo_TicketedDateTime_Date ProcessPaymentRQ.tmp#HistoricalPricingInfo_HistoricalPricingInfo_TicketedDateTime_Time
Properties
content: complex
Model Date , Time{0,1}
Children Date, Time
Instance
<TicketedDateTime>
  <Date>{1,1}</Date>
  <Time>{0,1}</Time>
</TicketedDateTime>
Source
<xsd:element name="TicketedDateTime">
  <xsd:annotation>
    <xsd:documentation>Timestamp of ticket issuance for past date segments in OriginDestination section.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Date" type="Date">
        <xsd:annotation>
          <xsd:documentation>Specifies departure or arrival date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
      <xsd:element name="Time" type="Time" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Departure or arrival time in ISO 8601 twenty-four hour clock format. Example: 14:00</xsd:documentation>
        </xsd:annotation>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element HistoricalPricingInfo / TicketedDateTime / Date
Namespace No namespace
Annotations
Specifies departure or arrival date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25
Diagram
Diagram ProcessPaymentRQ.tmp#Date
Type Date
Properties
content: simple
Source
<xsd:element name="Date" type="Date">
  <xsd:annotation>
    <xsd:documentation>Specifies departure or arrival date in ISO 8601 format (yyyy-mm-dd). Example: 2001-12-25</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element HistoricalPricingInfo / TicketedDateTime / Time
Namespace No namespace
Annotations
Departure or arrival time in ISO 8601 twenty-four hour clock format. Example: 14:00
Diagram
Diagram ProcessPaymentRQ.tmp#Time
Type Time
Properties
content: simple
minOccurs: 0
Facets
length 5
pattern ([0-1][0-9]|2[0-3]):[0-5][0-9]
Source
<xsd:element name="Time" type="Time" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Departure or arrival time in ISO 8601 twenty-four hour clock format. Example: 14:00</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element HistoricalPricingInfo / RecordLocator
Namespace No namespace
Annotations
FUTURE USE.
NOT SUPPORTED.
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
maxOccurs: 0
Source
<xsd:element name="RecordLocator" type="xsd:string" minOccurs="0" maxOccurs="0">
  <xsd:annotation>
    <xsd:documentation>FUTURE USE. NOT SUPPORTED.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element NegoRateCode
Namespace No namespace
Annotations
Negotiated rate code.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
Source
<xsd:element name="NegoRateCode">
  <xsd:annotation>
    <xsd:documentation>Negotiated rate code.</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element Latitude
Namespace No namespace
Annotations
Geographical information for latitude. If sign attribute is missing, positive values stand for North, negative values for South. Example: 49.9856
Diagram
Diagram ProcessPaymentRQ.tmp#Latitude_Sign
Type extension of xsd:decimal
Properties
content: complex
Used by
Element GeoCoded
Attributes
QName Type Fixed Default Use Annotation
Sign restriction of xsd:string optional
Latitude Indicator.  Values are: N = North of Equator S = South of Equator  Example: S
Source
<xsd:element name="Latitude">
  <xsd:annotation>
    <xsd:documentation>Geographical information for latitude. If sign attribute is missing, positive values stand for North, negative values for South. Example: 49.9856</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:decimal">
        <xsd:attribute name="Sign">
          <xsd:annotation>
            <xsd:documentation>Latitude Indicator. Values are: N = North of Equator S = South of Equator Example: S</xsd:documentation>
          </xsd:annotation>
          <xsd:simpleType>
            <xsd:restriction base="xsd:string">
              <xsd:enumeration value="S"/>
              <xsd:enumeration value="N"/>
            </xsd:restriction>
          </xsd:simpleType>
        </xsd:attribute>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Longitude
Namespace No namespace
Annotations
Geographical information for longitude. If sign attribute is missing, positive values stand for East, negative values for West. Example: 9.1220
Diagram
Diagram ProcessPaymentRQ.tmp#Longitude_Sign
Type extension of xsd:decimal
Properties
content: complex
Used by
Element GeoCoded
Attributes
QName Type Fixed Default Use Annotation
Sign restriction of xsd:string optional
Longitude indicator.  Values are: E = East of Meridian, W = West of Meridian  Example: E
Source
<xsd:element name="Longitude">
  <xsd:annotation>
    <xsd:documentation>Geographical information for longitude. If sign attribute is missing, positive values stand for East, negative values for West. Example: 9.1220</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:decimal">
        <xsd:attribute name="Sign">
          <xsd:annotation>
            <xsd:documentation>Longitude indicator. Values are: E = East of Meridian, W = West of Meridian Example: E</xsd:documentation>
          </xsd:annotation>
          <xsd:simpleType>
            <xsd:restriction base="xsd:string">
              <xsd:enumeration value="E"/>
              <xsd:enumeration value="W"/>
            </xsd:restriction>
          </xsd:simpleType>
        </xsd:attribute>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element GeoCoded
Namespace No namespace
Annotations
Geographical position information. 
Allows search by geographical longitude and latitude and to define a search radius around the specified geo location.
Diagram
Diagram ProcessPaymentRQ.tmp#Radius ProcessPaymentRQ.tmp#DistanceUnit ProcessPaymentRQ.tmp#Longitude ProcessPaymentRQ.tmp#Latitude
Properties
content: complex
Model ALL(Longitude Latitude)
Children Latitude, Longitude
Instance
<GeoCoded DistanceUnit="K" Radius="">
  <Longitude Sign="">{1,1}</Longitude>
  <Latitude Sign="">{1,1}</Latitude>
</GeoCoded>
Attributes
QName Type Fixed Default Use Annotation
DistanceUnit restriction of xsd:string K optional
Unit of distance.
Values:
M = Miles
K = Kilometers
Example: K
Radius xsd:unsignedLong optional
Radius around the specified location, within which results should be included.
Example: 0.5
Source
<xsd:element name="GeoCoded">
  <xsd:annotation>
    <xsd:documentation>Geographical position information. Allows search by geographical longitude and latitude and to define a search radius around the specified geo location.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:all>
      <xsd:element ref="Longitude"/>
      <xsd:element ref="Latitude"/>
    </xsd:all>
    <xsd:attribute ref="Radius"/>
    <xsd:attribute ref="DistanceUnit" default="K">
      <xsd:annotation>
        <xsd:documentation>Unit of distance in which Radius is specified. Values: M = Miles K = Kilometers Defaults to kilometers, if left out. Example: M</xsd:documentation>
      </xsd:annotation>
    </xsd:attribute>
  </xsd:complexType>
</xsd:element>
[ top ]
Element TravelerIDRef
Namespace No namespace
Annotations
Unique association ID reference of the traveler associated to this item. No comma separeted lists and no ranges allowed.        Example: T1
Diagram
Diagram
Type xsd:string
Properties
content: simple
Source
<xsd:element name="TravelerIDRef" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Unique association ID reference of the traveler associated to this item. No comma separeted lists and no ranges allowed. Example: T1</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element SegmentIDRef
Namespace No namespace
Annotations
ID reference used to asscociate this item to a segment.  No comma separeted lists and no ranges supported.    Example: F1
Diagram
Diagram
Type xsd:string
Properties
content: simple
Source
<xsd:element name="SegmentIDRef" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>ID reference used to asscociate this item to a segment. No comma separeted lists and no ranges supported. Example: F1</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element FareRefKey
Namespace No namespace
Annotations
Unique fare reference key. If present in pricing response messages, must be included in FareRulesRQ.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
Source
<xsd:element name="FareRefKey">
  <xsd:annotation>
    <xsd:documentation>Unique fare reference key. If present in pricing response messages, must be included in FareRulesRQ.</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element HotelRating
Namespace No namespace
Annotations
Rating of this hotel. Note that this element will eventually supercede the AAARating element definition. The latter will be deprecated soon.
Example: NTM3  CROWN
Diagram
Diagram ProcessPaymentRQ.tmp#HotelRating_RatingSystem
Type extension of xsd:string
Properties
content: complex
Attributes
QName Type Fixed Default Use Annotation
RatingSystem restriction of xsd:string optional
Identifies the rating system used to rate the hotel. Values are: 
AAA - AAA in US
GUESTS - Guest rating
HRS - Hotel Reservation System 'stars' rating
NTM - North Star Media 'crown' rating.
HBC - Booking.com rating
UNK - unknown.
Source
<xsd:element name="HotelRating">
  <xsd:annotation>
    <xsd:documentation>Rating of this hotel. Note that this element will eventually supercede the AAARating element definition. The latter will be deprecated soon. Example: NTM3 CROWN</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:string">
        <xsd:attribute name="RatingSystem">
          <xsd:annotation>
            <xsd:documentation>Identifies the rating system used to rate the hotel. Values are: AAA - AAA in US GUESTS - Guest rating HRS - Hotel Reservation System 'stars' rating NTM - North Star Media 'crown' rating. HBC - Booking.com rating UNK - unknown.</xsd:documentation>
          </xsd:annotation>
          <xsd:simpleType>
            <xsd:restriction base="xsd:string">
              <xsd:enumeration value="AAA"/>
              <xsd:enumeration value="GUESTS"/>
              <xsd:enumeration value="HRS"/>
              <xsd:enumeration value="NTM"/>
              <xsd:enumeration value="UNK"/>
              <xsd:enumeration value="HBC"/>
            </xsd:restriction>
          </xsd:simpleType>
        </xsd:attribute>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element POIDistance
Namespace No namespace
Annotations
Distance to a point of interest. Will somewhen replace DistanceToAirport. Example: 5.5
Diagram
Diagram ProcessPaymentRQ.tmp#POIDistance_POIType ProcessPaymentRQ.tmp#POIDistance_POIName
Type extension of xsd:decimal
Properties
content: complex
Attributes
QName Type Fixed Default Use Annotation
POIName xsd:string optional
Point of interest name.
Example: FRANKFURT/MAIN
POIType restriction of xsd:string required
Point of interest type. Example: AIRPORT
Source
<xsd:element name="POIDistance">
  <xsd:annotation>
    <xsd:documentation>Distance to a point of interest. Will somewhen replace DistanceToAirport. Example: 5.5</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:decimal">
        <xsd:attribute name="POIType" use="required">
          <xsd:annotation>
            <xsd:documentation>Point of interest type. Example: AIRPORT</xsd:documentation>
          </xsd:annotation>
          <xsd:simpleType>
            <xsd:restriction base="xsd:string">
              <xsd:enumeration value="AIRPORT"/>
              <xsd:enumeration value="TRAIN STATION"/>
              <xsd:enumeration value="CITY CENTER"/>
              <xsd:enumeration value="HIGHWAY"/>
              <xsd:enumeration value="SHOPPING"/>
              <xsd:enumeration value="PETROL STATION"/>
              <xsd:enumeration value="THEATER"/>
              <xsd:enumeration value="CINEMA"/>
              <xsd:enumeration value="CAR RENTAL STATION"/>
              <xsd:enumeration value="UNKNOWN"/>
              <xsd:enumeration value="LOCATION"/>
            </xsd:restriction>
          </xsd:simpleType>
        </xsd:attribute>
        <xsd:attribute name="POIName" type="xsd:string">
          <xsd:annotation>
            <xsd:documentation>Point of interest name. Example: FRANKFURT/MAIN</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element CarLocation / CityCode
Namespace No namespace
Annotations
IATA 3-letter city/airport code for location. In case of non-airport location Category and Number need to be present. Example: NYC
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
length 3
Source
<xsd:element name="CityCode">
  <xsd:annotation>
    <xsd:documentation>IATA 3-letter city/airport code for location. In case of non-airport location Category and Number need to be present. Example: NYC</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="3"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element CarLocation / Category
Namespace No namespace
Annotations
Location category:
T = Airport terminal
O = Off-airport
C = City location 
P = Port 
X = Rail
N = North suburban
E = East suburban
S = South suburban
W = West suburban
A = All suburban locations 
R = Resort location
Example: C
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
length 1
Source
<xsd:element name="Category">
  <xsd:annotation>
    <xsd:documentation>Location category: T = Airport terminal O = Off-airport C = City location P = Port X = Rail N = North suburban E = East suburban S = South suburban W = West suburban A = All suburban locations R = Resort location Example: C</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element CarLocation / Number
Namespace No namespace
Annotations
Location number used to identify specific rental location within a location category.  Example: 001
Diagram
Diagram
Type xsd:string
Properties
content: simple
Source
<xsd:element name="Number" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Location number used to identify specific rental location within a location category. Example: 001</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element RequestForCarLocation / CityCode
Namespace No namespace
Annotations
IATA 3-letter city/airport code for location. In case of non-airport location Category need to be present (Number for particular locaction). Example: NYC
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
length 3
Source
<xsd:element name="CityCode">
  <xsd:annotation>
    <xsd:documentation>IATA 3-letter city/airport code for location. In case of non-airport location Category need to be present (Number for particular locaction). Example: NYC</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="3"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element RequestForCarLocation / Category
Namespace No namespace
Annotations
Location category:
T = Airport terminal
O = Off-airport
C = City location 
P = Port 
X = Rail
N = North suburban
E = East suburban
S = South suburban
W = West suburban 
D = default location for the city.
R = Resort location
Example: C
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
length 1
Source
<xsd:element name="Category">
  <xsd:annotation>
    <xsd:documentation>Location category: T = Airport terminal O = Off-airport C = City location P = Port X = Rail N = North suburban E = East suburban S = South suburban W = West suburban D = default location for the city. R = Resort location Example: C</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:length value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element RequestForCarLocation / Number
Namespace No namespace
Annotations
Location number used to identify specific rental location within a location category.  Example: 001
Diagram
Diagram
Type xsd:string
Properties
content: simple
minOccurs: 0
Source
<xsd:element name="Number" type="xsd:string" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Location number used to identify specific rental location within a location category. Example: 001</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element BasicEndorsement / Text
Namespace No namespace
Annotations
Endorsement text.
Diagram
Diagram ProcessPaymentRQ.tmp#FreeFormTextField
Type FreeFormTextField
Properties
content: simple
Facets
minLength 1
Source
<xsd:element name="Text" type="FreeFormTextField">
  <xsd:annotation>
    <xsd:documentation>Endorsement text.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element BaseFareType / Surcharges
Namespace No namespace
Annotations
Surcharges group
Diagram
Diagram ProcessPaymentRQ.tmp#SurchargesType_Amount ProcessPaymentRQ.tmp#SurchargesType_Surcharge ProcessPaymentRQ.tmp#SurchargesType
Type SurchargesType
Properties
content: complex
minOccurs: 0
Model Surcharge+
Children Surcharge
Instance
<Surcharges Amount="">
  <Surcharge Amount="" Segment="">{1,unbounded}</Surcharge>
</Surcharges>
Attributes
QName Type Fixed Default Use Annotation
Amount xsd:integer required
Total surcharges amount.  Example: 2000
Source
<xsd:element name="Surcharges" type="SurchargesType" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Surcharges group</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element SurchargesType / Surcharge
Namespace No namespace
Annotations
Surcharges break down information.
Diagram
Diagram ProcessPaymentRQ.tmp#SurchargeTypeBasic_Amount ProcessPaymentRQ.tmp#SurchargeTypeBasic_Designator ProcessPaymentRQ.tmp#SurchargeTypeBasic_Description ProcessPaymentRQ.tmp#SurchargeTypeBasic ProcessPaymentRQ.tmp#SurchargeType_Segment ProcessPaymentRQ.tmp#SurchargeType
Type SurchargeType
Type hierarchy
Properties
content: complex
maxOccurs: unbounded
Model Designator , Description{0,1}
Children Description, Designator
Instance
<Surcharge Amount="" Segment="">
  <Designator>{1,1}</Designator>
  <Description>{0,1}</Description>
</Surcharge>
Attributes
QName Type Fixed Default Use Annotation
Amount xsd:integer required
Individual surcharge amount.  Example: 270
Segment xsd:integer required
Segment number to which the surcharge applies.  Example: 1
Source
<xsd:element name="Surcharge" type="SurchargeType" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>Surcharges break down information.</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element SurchargeTypeBasic / Designator
Namespace No namespace
Annotations
Surcharge designator.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
Facets
minLength 1
Source
<xsd:element name="Designator">
  <xsd:annotation>
    <xsd:documentation>Surcharge designator.</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element SurchargeTypeBasic / Description
Namespace No namespace
Annotations
Surcharge descriptions as free form text.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
minOccurs: 0
Facets
minLength 1
Source
<xsd:element name="Description" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Surcharge descriptions as free form text.</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:minLength value="1"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element Children / Child
Namespace No namespace
Annotations
Child elements - one per requested child.
Diagram
Diagram ProcessPaymentRQ.tmp#Children_Children_Child_Age ProcessPaymentRQ.tmp#Children_Children_Child_ExtraBed
Properties
content: complex
maxOccurs: unbounded
Model Age , ExtraBed{0,1}
Children Age, ExtraBed
Instance
<Child>
  <Age>{1,1}</Age>
  <ExtraBed>{0,1}</ExtraBed>
</Child>
Source
<xsd:element name="Child" maxOccurs="unbounded">
  <xsd:annotation>
    <xsd:documentation>Child elements - one per requested child.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="Age">
        <xsd:annotation>
          <xsd:documentation>Age of child in years (allowed values are 0-17).</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:int">
            <xsd:minInclusive value="0"/>
            <xsd:maxInclusive value="17"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
      <xsd:element name="ExtraBed" minOccurs="0">
        <xsd:annotation>
          <xsd:documentation>Defines if child will need its own bed ('Y') or sleep in parents bed ('N'). If omitted no extra bed is required.</xsd:documentation>
        </xsd:annotation>
        <xsd:simpleType>
          <xsd:restriction base="xsd:string">
            <xsd:enumeration value="Y"/>
            <xsd:enumeration value="N"/>
          </xsd:restriction>
        </xsd:simpleType>
      </xsd:element>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
[ top ]
Element Children / Child / Age
Namespace No namespace
Annotations
Age of child in years (allowed values are 0-17).
Diagram
Diagram
Type restriction of xsd:int
Properties
content: simple
Facets
maxInclusive 17
minInclusive 0
Source
<xsd:element name="Age">
  <xsd:annotation>
    <xsd:documentation>Age of child in years (allowed values are 0-17).</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:int">
      <xsd:minInclusive value="0"/>
      <xsd:maxInclusive value="17"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element Children / Child / ExtraBed
Namespace No namespace
Annotations
Defines if child will need its own bed ('Y') or sleep in parents bed ('N'). If omitted no extra bed is required.
Diagram
Diagram
Type restriction of xsd:string
Properties
content: simple
minOccurs: 0
Facets
enumeration Y
enumeration N
Source
<xsd:element name="ExtraBed" minOccurs="0">
  <xsd:annotation>
    <xsd:documentation>Defines if child will need its own bed ('Y') or sleep in parents bed ('N'). If omitted no extra bed is required.</xsd:documentation>
  </xsd:annotation>
  <xsd:simpleType>
    <xsd:restriction base="xsd:string">
      <xsd:enumeration value="Y"/>
      <xsd:enumeration value="N"/>
    </xsd:restriction>
  </xsd:simpleType>
</xsd:element>
[ top ]
Element MediaType / Url
Namespace No namespace
Annotations
Hyperlink defining the location of the referenced media (e.g. location of a JPG file).
Diagram
Diagram
Type xsd:string
Properties
content: simple
Source
<xsd:element name="Url" type="xsd:string">
  <xsd:annotation>
    <xsd:documentation>Hyperlink defining the location of the referenced media (e.g. location of a JPG file).</xsd:documentation>
  </xsd:annotation>
</xsd:element>
[ top ]
Element MediaType / Width
Namespace No namespace
Annotations
Width of media content in specified units.
Diagram
Diagram ProcessPaymentRQ.tmp#MediaType_MediaType_Width_Unit
Type extension of xsd:int
Properties
content: complex
Attributes
QName Type Fixed Default Use Annotation
Unit MediaSizeUnitType required
Unit used to specify dimensions of media content.

Example:
mm (millimeter) 
px (pixel)
Source
<xsd:element name="Width">
  <xsd:annotation>
    <xsd:documentation>Width of media content in specified units.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:int">
        <xsd:attribute name="Unit" type="MediaSizeUnitType" use="required">
          <xsd:annotation>
            <xsd:documentation>Unit used to specify dimensions of media content. Example: mm (millimeter) px (pixel)</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element MediaType / Height
Namespace No namespace
Annotations
Height of media content in specified units.
Diagram
Diagram ProcessPaymentRQ.tmp#MediaType_MediaType_Height_Unit
Type extension of xsd:int
Properties
content: complex
Attributes
QName Type Fixed Default Use Annotation
Unit MediaSizeUnitType required
Unit used to specify dimensions of media content.

Example:
mm (millimeter) 
px (pixel)
Source
<xsd:element name="Height">
  <xsd:annotation>
    <xsd:documentation>Height of media content in specified units.</xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:simpleContent>
      <xsd:extension base="xsd:int">
        <xsd:attribute name="Unit" type="MediaSizeUnitType" use="required">
          <xsd:annotation>
            <xsd:documentation>Unit used to specify dimensions of media content. Example: mm (millimeter) px (pixel)</xsd:documentation>
          </xsd:annotation>
        </xsd:attribute>
      </xsd:extension>
    </xsd:simpleContent>
  </xsd:complexType>
</xsd:element>
[ top ]
Element MediaType / Type
Namespace No namespace
Annotations
Type of media content. 

Example:
image
webcam
video 
360 (panorama view)
Diagram
Diagram ProcessPaymentRQ.tmp#MediaTypeType
Type MediaTypeType
Properties
content: