Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • SecurePayerAuthenticationVersion: 3DS Version

  • SecurePaymentVersion1: Data for 3DS 1.x

  • SecurePaymentVersion2: Data for 3DS 2.x

  • SecureProgram: Name of the secure payment program

  • SellerOwnCardInd: Indicator for whether the Credit Card belongs to the Travel Agent or the customer.

...

Element

SecurePayerAuthenticationVersion

Xpath

/IATA_OrderCreateRQ/Request/PaymentFunctions/PaymentMethodCriteria/PaymentCardCriteria/SecurePayerAuthenticationVersion (XSD Viewer)

Description

Used by Seller if 3D-Secure is supported. Seller can specify which version of 3D-Secure is supported. Note: 3D-Secure context should be used when the Customer-Seller interaction type is web and/or mobile.

Sub-elements

  • CardEnrollmentVersionText - Version of 3D-Secure for which the card is enrolled.

  • SupportedVersionText - Specifies the exact supported 3D-Secure version.

Element

SecurePaymentVersion1

Xpath

/IATA_OrderCreateRQ/Request/PaymentFunctions/PaymentProcessingDetails/PaymentMethod/PaymentCard/SecurePaymentVersion1 (XSD Viewer)

Description

Contains the indicators and fields that convey the result of the 3D Secure authentication transaction. Applicable for 3D Secure Version V 1.0.

Sub-elements

  • PayerAuthenticationResponseText - The authentication response for the 3-D Secure transaction. It is used to determine whether or not the customer has been authenticated by the card issuer. It must be included in the final authorization request. Example: eJzVWFmzosgSfudXdPQ8Gt1sbkzYRhQ7KCjI/sYOsimgoL/+lp7Tp5c5t2d67tMw8yv/WqiluJXS8WyyVFEQT28qz

Info

This field is the text from the PARes in Base64. (More information about PARes can be found in: PARes (3DS 1.x))

Element

SecurePaymentVersion2

Xpath

/IATA_OrderCreateRQ/Request/PaymentFunctions/PaymentProcessingDetails/PaymentMethod/PaymentCard/SecurePaymentVersion2 (XSD Viewer)

Description

Contains all information for the result of 3D-Secure authentication process.

Sub-elements

  • AuthenticationMerchantName - Name of the merchant

  • AuthenticationValue - Authentication value

  • DirectoryServerTrxID - DS (Directory Server) transaction ID

  • ElectronicCommerceInd - ECI (electronic commerce indicator)

Info

More information about ECI can be found in: (ECI)

  • ProgramProtocolText - Program Protocol

  • TrxStatusReasonText - outcome of authentication coming from the DS - see EMVCO documentation for list of possible values.

  • TrxStatusText - outcome of authentication - see EMVCO documentation

Info

More information about the meaning of the fields can be found in (3DS 2.x Reference)

Element

SecureProgram

Xpath

/IATA_OrderCreateRQ/Request/PaymentFunctions/PaymentProcessingDetails/PaymentMethod/PaymentCard/SecureProgram (XSD Viewer)

Description

Contains enrolment information of the Payment Card. e.g. Verified by Visa.

Sub-elements

  • EnrollmentStatusText - 3D Secure Program Enrollment Status. Examples: CardNotEnrolled, CardEnrolled, CardMayBeEnrolled, Unknown

  • SecurePaymentProgramName - Name of the secure payment program. E.g. Verified by Visa.

Element

SellerOwnCardInd

Xpath

/IATA_OrderCreateRQ/Request/PaymentFunctions/PaymentProcessingDetails/PaymentMethod/PaymentCard/SellerOwnCardInd (XSD Viewer)

Description

When TRUE, indicates the seller is using their own card. If FALSE, customer card is being used.

Info

This is not specific to 3DS although we are going to use the functionality.

Sub-elements

NDC 17.2

The IATA 17.2 version does not support 3DS 2.x, and although is does partially support 3DS 1.x the structure of the information is very different to previous versions.

...

Code Block
languagexml
<AugPoint Owner="IB">
   <PaymentCardSecureInfo ObjectKey="this_is_the_key_of_the_payment_card_secure_info">
      <PaymentFunctions>
         ...
      </PaymentFunctions>
   </PaymentCardSecureInfo>
</AugPoint>

Name

Description

File

Backport_IberiaSecurePayment_17.2.xsd

Additional schema for the extension of the OrderCreateRQ y OrderChangeRQ messages.

View file
nameBackport_IberiaSecurePayment_17.2.xsd

OrderCreateRQ_17.2_Augmented_3DS1.xml

Example of an OrderCreateRQ 17.2 with CreditCard payment, with the contents of a 3DS 1.x authentication in the AugmentationPoint and with the schemas referenced to validate the document.

The addition parts with respect to a standard OrderCreate are marked with a comment:

<!-- ########################### -->

View file
nameOrderCreateRQ_17.2_Augmented_3DS1.xml

OrderCreateRQ_17.2_Augmented_3DS2.xml

Example of an OrderCreateRQ 17.2 with CreditCard payment, with the contents of a 3DS 2.x authentication in the AugmentationPoint and with the schemas referenced to validate the document.

The addition parts with respect to a standard OrderCreate are marked with a comment:

########################### -->

View file
nameOrderCreateRQ_17.2_Augmented_3DS2.xml

More information

Page Tree
root@self

...

New NDC Footer.pngImage Added