Recent Revisions to This Document

24.06

Added Use Cases for Transactions Using Tokens

Added a section on use cases for transactions that use TMS tokens, Flex Micro Form tokens, and for tokenized cards. For more information, see Token Use Cases.

Added Use Cases for 3RI Transactions

Added a section on use cases for all types of 3RI transactions. For more information, see Merchant Initiated Transactions.

Added Non-Payment Authentication Use Case

Updated the use cases to include Non-Payment Authentication (NPA). For more information, see Use Case: Non-Payment Authentication.

Updated Content in the Testing Section about the ECI Raw Value

Updated the wording describing the ECI raw values for test cases 2.6, 2.7, 2.8, and 2.9 to note to point out that unlike the other test scenarios in this section, those tests do not return an ECI raw value. See Test Case 2.6: Authentication Not Available on Lookup.

Updated Use Case Example Payloads

Updated the payload code samples to eliminate the use of the field

clientReferenceInformation.code

field in the use cases since this is not a required field and does not need to be in the example code.

Updated Test Card Data

Updated card type values for mada and JCB J/Secure cards and verified and updated some test card numbers used in test cases. See Test Cases for 3-D Secure 2.x

24.05

Updated List of Browser Fields

The browser value fields listed for the check enrollment service were updated. See Step 3: Payer Authentication Check Enrollment Service.

Updated

Added new API field,

consumerAuthenticationInformation.authenticationBrand

that is used with mada transactions to indicate which directory server was used during authentication. This field was added to the optional fields for checking enrollment and validation. See Optional Fields for

Updated Content in the Testing Section about the ECI Raw Value

Updated the wording describing the ECI raw values for test cases 2.6, 2.7, 2.8, and 2.9 to note to point out that unlike the other test scenarios in this section, those tests do not return an ECI raw value. See Test Case 2.6: Authentication Not Available on Lookup.

Updated Use Case Example Payloads

Updated the payload code samples to eliminate the use of the field

clientReferenceInformation.code

field in the use cases since this is not a required field and does not need to be in the example code.

Updated Test Card Data

Updated card type values for mada and JCB J/Secure cards and verified and updated some test card numbers used in test cases. See Test Cases for 3-D Secure 2.x

24.04

Corrected Test Case Card Number

For Test Case 2.5: Rejected Frictionless Authentication by the Issurer, the test card numbers for Mastercard 2.2.0 and Mastercard (mada) were updated. See Test Case 2.5: Rejected Frictionless Authentication.

Added list of HTTP Status Codes

Added a list of HTTP status codes to the testing section. For more information, see HTTP Status Codes.

Added use cases for setup and enrollment check with tokens.

Updated the use cases to include using tokens during payer authentication. For more information, see Use Case: Collecting Device Data Collection Using Stored Payment Credential (TMS Token) and Use Case: Checking Enrollment When Using a TMS Token.

Added Support for Test cases for mada

Updated the test cases for the 3-D Secure 2.x section to include test results for the mada card. For more information, see Test Cases for 3-D Secure 2.x.

Highlighted API fields specific to Meeza card usage

Added API fields to the country-specific section for the setup and check enrollment use cases that are required when using the Meeza card. For more information, see Use Case: Setting Up Payer Authentication and Use Case: Checking Enrollment in Payer Authentication.

24.03

24.02

24.01