...
...
...
...
...
...
...
...
...
...
...
...
| Note |
|---|
Please check this page regularly for upcoming functionality and feature updates to pmsXchange v2. |
To be removed removed / modified modified / added to added to the specification.
| Table of Contents |
|---|
Payment Service Directive (PSD2) / Strong Customer Authentication (SCA)
Release Date: TBC
| Note |
|---|
This change will include a WSDL schema update. |
OTA_ResRetrieveRS
GuaranteeType
...
...
...
...
Guarantee / GuaranteesAccepted / GuaranteeAccepted / PaymentCard
...
0..1
...
Contains payment card information
...
@CardCode
...
0..1
...
The 2 character code of the credit card issuer. Please see the OTA Payment Card Provider Codes table for reference
...
The type of payment card, refer to the OTA Card Type code table for reference. Common usages are:
1: Credit
2: Debit
...
@CardNumber
...
0..1
...
The number embossed on the payment card
...
@ExpireDate
...
0..1
...
This is the expiry date of the payment card used in the format MMyy
...
Transaction results.
IMPORTANT NOTE: SCA / 3DS details will only be provided if received from an SCA / 3DS compatible booking agent. Information within the 'ThreeDomainSecurity' element will not be visible in The Channel Manager.
...
The type of payment information, this can be one of
PaymentGatewayName: The name of the payment gateway
PaymentGatewayAuthCode: The authorization code of the payment gateway
PaymentReferenceId: If a reference was provided for any payment, it will be included here
The comment Name will always be included if a Comment node is present here
...
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
...
N
...
Failed Authentication
...
U
...
Unable to Complete Authentication
...
A
...
Successful Attempts Transaction
...
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
...
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
...
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.
What's happening now?
For the following error scenarios, wherein when OTA_HotelAvailNotif OR OTA_HotelAvailNotif RQ message from PMS provider is not processed successfully, pmsXchange responds back with a failure RS message which has the details of the error. P.S. refer Notes for the full list of error codes supported by pmsXchange.
Error Scenarios (Error Type = 3) -
- Room Type not mapped
- Channel Code not mapped
...
Error Type
...
Error Code
...
Error Reason
...
Error Message
...
3
...
249
...
Invalid Rate Code
...
Could not find any roomTypes for ‘Hotel XXXX’ matching InvTypeCode ‘XXXX’ and RatePlanCode ‘XXXX’
...
3
...
402
...
Invalid Room Code
...
Could not find any roomTypes for ‘Hotel XXXX’ matching InvTypeCode ‘XXXX’ and RatePlanCode ‘XXXX’
...
3
...
783
...
Room or Rate not found
...
Could not find any roomTypes for ‘Hotel XXXX’ matching InvTypeCode ‘XXXX’ and RatePlanCode ‘XXXX’
...
3
...
n/a
...
Booking Agent Mapping missing
...
Booking agent mapping missing for HotelCode 'XXXX' and BookingAgentCode 'XXXX' and InvTypeCode 'XXXX'
What's going to change?
For the following error scenarios, wherein when OTA_HotelAvailNotif OR OTA_HotelAvailNotif RQ message from PMS provider is not processed successfully, PmsXchange would still respond back with a success RS message with no details of the error.
Error Scenarios -
- Invalid Rate Code
- Invalid Room Code
- Room or Rate not found
- Booking Agent Mapping missing
However, pmsXchange will send the details of the error(s) via an automated email to the partner PMS and affected hotels. Details are as follows -
- An email would be generated twice a day at 8.00 am & 4.00 pm (timezone of the PMS partner)
Notes
...
Error Code
...
Error Reason
...
Error Message
...
245
...
Invalid Confirmation Number
...
Could not find Notifications to confirm with notification id XXXX
...
392
...
Invalid Hotel Code
...
Hotel with HotelCode XXXX does not exist
...
375
...
Hotel not Active
...
Hotel with HotelCode XXXX is not enabled for inventory updates
...
249
...
Invalid Rate Code
...
Could not find any roomTypes for ‘Hotel XXXX’ matching InvTypeCode ‘XXXX’ and RatePlanCode ‘XXXX’
...
402
...
Invalid Room Code
...
Could not find any roomTypes for ‘Hotel XXXX’ matching InvTypeCode ‘XXXX’ and RatePlanCode ‘XXXX’
...
783
...
Room or Rate not found
...
No room exists with InvTypeCode XXXX and RatePlanCode XXXX for hotelier XXXX
...
448
...
System error
...
450
...
Unable to process
...
Each RatePlan must have a unique name
...
Description cannot be more than 512 characters long
...
| Child pages (Children Display) |
|---|