Versions Compared

Key

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



Note

Please check this page regularly for upcoming functionality and feature updates to pmsXchange v2.

To be removed / modified / 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

...

Element

...

Number

...

Description

...

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

...