Revised Payment Services Directive (PSD2) Info

Beginning March 2021 Hilton will begin supporting PSD2 requirements

The Revised Payment Services Directive (PSD2) is based off European Union directives requiring travel partners who meet certain conditions to support strong customer authentication.
If you are a travel partner who sends Hilton a retail bookings that meet the below criteria then it is expected your interface should support PSD2 and send in the necessary fields on booking requests to Hilton.

  • The booking is for a Hilton property located in the European Union/UK,
  • The issuing bank of the credit card is within European Union/UK, and
  • The customer entered the credit card information. Merchant bookings, virtual credit cards do not apply.

If all of the above is true then the travel partner booking interface should handle Strong Customer Authentication (SCA). The resulting authentication response (SCA) data should then be passed to Hilton within the SecureCustomerAuthenticationInfo object on DCRes JSON request.

Commonly Asked Questions

Do I need to pass in SCA elements on a modify request?
Yes. When the booking amount changes from the previously authenticated amount it will require a new SCA. For modifies not requiring rate changes such as updating reservation comments the original SCA should be passed in.

What happens if I do not pass in SCA elements for a booking that falls within PSD2 directives?
If authentication elements are not passed to Hilton, the booking should still succeed, although it may make it more difficult for property to charge.

When passing SCA elements do I need to populate all SecureCustomerAuthenticationInfo elements supported by Hilton?
While all fields in the SecureCustomerAuthenticationInfo JSON object are optional it is recommended that you accurately populate as many as possible based on what your interface can support. Your interface may also support SCA fields beyond what Hilton has defined within SecureCustomerAuthenticationInfo JSON object. The additional fields can be left unmapped as Hilton does not require them.

Can Hilton reject a booking due to data passed within SCA elements?
If the SCA elements passed meet the regex pattern found within the DCRes JSON swagger then the request should not fail. While the SCA elements are expected to follow the ‘Accepted Values’ column in table below, Hilton will not fail the request as long as it meets the JSON regex.

If you are a consumer of Hilton’s DirectConnect API and have further questions regarding Hilton’s support of PSD2 then please reach out to your point of contact at Hilton.

Below is an overview of Secure Customer Authentication elements that Hilton supports. Exact details of the SecureCustomerAuthenticationInfo object found within the swagger here.

Field Name DirectConnect Res JSON Field Accepted Values Sample Data
Electronic Commerce Indicator

eCommerceIndicator

type: string

01, 02, 03, 04, 05, 06, 07, 08, 09 05
Cardholder authentication verification value/cryptogram

cavv

type: string

Base 64 encoded string AQIDBAUGBwgJCgsMDQ4PEBESExQ=
Unique transaction identifier (3DSv1: xid, 3DSv2: dsTransID)

transactionId

type: string

Alpha-Numeric (dsTransID) or Base 64 encoded (xid) string ODgzNTk4MzA3NTE3MDIySAAAAAA=40a89da0-3cff-4ef4-9a11-b9eef70cec79
Indicates the 3DS authentication status (3DSv1: PARes Status, 3DSv2: TransStatus)

threeDAuthenticatedResponse

type: string

Y (Success), N (Failure), U (Unavailable) Y
3D Secure version

threeDSVersion

type: string

1 (3DSv1), 2 (3DSv2) 1
2
2.1.1
Indicates directory transaction qualification/account verification

threeDOfferedResponsetype

type: string

Y (Success), N (Failed), U (Unavailable), A (Attempted), C (Challenge Reqd), R (Rejected) C
Specifies the Exemption Code (2 characters) & CAVV algorithm (single digit) that was used for authentication

cavvAlgorithm

type: string

Exemption Codes:
LV (Low Value), SC (Secure Corporate), TB (Trusted Beneficiary), TR (Transaction Risk Analysis), DA (Delegated Authentication), AO (Authentication Outage)
SC0
LV1
Network transaction / Trace ID Internal ID not likely to be necessary for most third parties

networkTxnRefTraceId

type: string

Alpha-Numeric string (length varies by card scheme) MCC8645257566