...
To be removed / modified / added to the specification.
| Table of Contents |
|---|
Payment Service Directive (PSD2)
...
SiteMinder is targeting an update to the SiteConnect and pmsXchangev2 specifications to support new payment workflows brought about because of the PSD2 : Secure Customer Authentication (SCA) directive in the EEA. To find out more about SiteMinder's position for connectivity partners please see the following link - https://www.siteminder.com/payment-services-directive/
...
/ Strong Customer Authentication (SCA)
Release Date: TBC
| Note |
|---|
This change will include a WSDL schema update. |
OTA_HotelResNotifRQ
Guarantee and Deposit Payments
Element | Number | Type | Description |
|---|---|---|---|
| ResGlobalInfo / Guarantee / GuaranteesAccepted / GuaranteeAccepted PaymentCard | 0..1 | Guarantee provided with the reservation. This element is used if there is no deposit payed for the reservation. | |
| @CardType | 0..1 | Always 1 to indicate credit card | |
| @CardCode | 1 | The 2 character code of the credit card issuer. Please see the OTA Payment Card Provider Codes table for reference | |
| @CardNumber | 0..1 | This is actual number of the credit card used for deposit/prepayment. | |
| @SeriesCode | 0..1 | The SeriesCode attribute is used (Optionally) for the security number of the card. NOTE: While this attribute is supported in the reservation XML, the details of this attribute are not stored or passed through to the hotel due to PCI-DSS requirements. | |
| @ExpireDate | 0..1 | This is the expiry date of the credit card used for deposit/prepayment. Format MMyy. | |
| PaymentCard / CardHolderName | 0..1 | The name of the card holder. | |
| PaymentCard / ThreeDomainSecurity / Results | 0..1 | Transaction results. IMPORTANT NOTE: SCA / 3DS details will only be passed through to hoteliers integrated with a 3DS compatible property management system. If the hotelier is not integrated with a property management system or the property management system does not support SCA, information within the 'ThreeDomainSecurity' element will not be visible in The Channel Manager. | |
| @ThreeDSVersion | 1 | The 3DS version used for authentication | |
| @ECI | 1 | Electronic Commerce Indicator. Please see Electronic Commerce Indicator Codes table for reference. | |
| @CAVV | 0..1 | Cardholder Authentication Verification Value (CAVV); Authentication Verification Value (AVV); Universal Cardholder Authentication Field (UCAF) | |
| @PAResStatus | 0..1 | Transactions status result identifier. Please see Transactions Status Result Identifier Codes table for reference. | |
| @SignatureVerification | 0..1 | Transaction Signature status identifier. Please see Transaction Signature Status Codes table for reference. | |
| @XID | 0..1 | Transaction identifier resulting from authentication processing | |
| @Enrolled | 0..1 | Status of Authentication eligibility. Please see Status of Authentication Codes table for reference. | |
| @DSTransactionID | 0..1 | Unique transaction identifier assigned by the Directory Server (DS) to identify a single transaction | |
| ResGlobalInfo / DepositPayments /GuaranteePayment | 0..1 | Deposit provided with the reservation. | |
| GuaranteePayment / AcceptedPayments / AcceptedPayment | 0..1 | Deposit payment information. | |
| AcceptedPayment / PaymentCard | 1 | Mandatory if AcceptedPayment is sent. The card to which the deposit or prepayment is charged. | |
| @CardType | 0..1 | Always 1 to indicate credit card | |
| @CardCode | 1 | The 2 character code of the credit card issuer. Please see the OTA Payment Card Provider Codes table for reference | |
| @CardNumber | 0..1 | This is actual number of the credit card used for deposit/prepayment. | |
| @SeriesCode | 0..1 | The SeriesCode attribute is used (Optionally) for the security number of the card. NOTE: While this attribute is supported in the reservation XML, the details of this attribute are not stored or passed through to the hotel due to PCI-DSS requirements. | |
| @ExpireDate | 0..1 | This is the expiry date of the credit card used for deposit/prepayment. Format MMyy. | |
| PaymentCard / CardHolderName | 0..1 | The name of the card holder. | |
| PaymentCard / ThreeDomainSecurity / Results | 0..1 | Transaction results. IMPORTANT NOTE: SCA / 3DS details will only be passed through to hoteliers integrated with a 3DS compatible property management system. If the hotelier is not integrated with a property management system or the property management system does not support SCA, information within the 'ThreeDomainSecurity' element will not be visible in The Channel Manager. | |
| @ThreeDSVersion | 1 | The 3DS version used for authentication | |
| @ECI | 1 | Electronic Commerce Indicator. Please see Electronic Commerce Indicator Codes table for reference. | |
| @CAVV | 0..1 | Cardholder Authentication Verification Value (CAVV); Authentication Verification Value (AVV); Universal Cardholder Authentication Field (UCAF) | |
| @PAResStatus | 0..1 | Transactions status result identifier. Please see Transactions Status Result Identifier Codes table for reference. | |
| @SignatureVerification | 0..1 | Transaction Signature status identifier. Please see Transaction Signature Status Codes table for reference. | |
| @XID | 0..1 | Transaction identifier resulting from authentication processing | |
| @Enrolled | 0..1 | Status of Authentication eligibility. Please see Status of Authentication Codes table for reference. | |
| @DSTransactionID | 0..1 | Unique transaction identifier assigned by the Directory Server (DS) to identify a single transaction | |
| GuaranteePayment / AmountPercent | 1 | Mandatory if something is passed in the DepositPayment element. | |
| @Amount | 1 | Amount charged as deposit | |
| @CurrencyCode | 1 | Currency of the deposit payment |
Reference Table Updates
Secure Customer Authentication
Status of Authentication Code
Value | Definition |
|---|---|
Y | Yes, Bank is participating in 3-D Secure protocol and will return the ACSUrl |
N | No, Bank is not participating in 3-D Secure protocol |
U | Unavailable, The DS or ACS is not available for authentication at the time of the request |
B | Bypass, Merchant authentication rule is triggered to bypass authentication in this use case |
Transactions Status Result Identifier Code
Value | Definition |
|---|---|
Y | Successful Authentication |
N | Failed Authentication |
U | Unable to Complete Authentication |
A | Successful Attempts Transaction |
| B | You can proceed to authorisation using the information received |
| R | Authentication Rejected (Merchant must not submit for authorisation) |
Transaction Signature Status Code
Value | Definition |
|---|---|
Y | Indicates that the signature of the PARes has been validated successfully and the message contents can be trusted. |
N | Indicates that the PARes could not be validated. This result could be for a variety of reasons; tampering, certificate expiration, etc., and the result should not be trusted. |
null | If not sent then null |
Electronic Commerce Indicator Code
Value | Definition |
|---|---|
02 or 05 | Fully Authenticated Transaction |
01 or 06 | Attempted Authentication Transaction |
00 or 07 | Non 3-D Secure Transaction |
| 02, 01, 00 | Mastercard |
| 05, 06, 07 | Visa |
| 05, 06, 07 | Amex |
| 05, 06, 07 | JCB |
| 05, 06, 07 | Diners |
...
Error Handling
Release Date: TBC
pmsXchange is migrating from the current legacy system to a microservices based new world architecture hosted in AWS. This pmsXchange internal upgradation comes with a set of advantages in terms of performance, scalability, robustness, faster development times, security and flexibility. This document lists the changes related to pmsXchange migration which will impact the PMS partners and an account of how some existing functionalities would behave in the new world.
...