Recent Revisions to This Document

Card numbers were added for testing authentication with China UnionPay. See Test Cases for 3-D Secure 2.x.

Fixed spacing error for documentation hub link. See the introduction.

Several dead links were fixed.

Some of the use case examples were reorganized to fix a spacing issue occurring in the HTML version. See Authentication Examples Using Primary Account Numbers.

A 3-D Secure test case for verifying system behavior when a system error prevents authentication. See 2.13: Authentication Is Bypassed.

The EFTPOS card type was added to the 3-D Secure test cases. See Test Cases for 3-D Secure 2.x.

For test case 2.4: Unavailable Frictionless Authentication, the expected AVV value returned in the test was updated to indicate that no value should be returned. See 2.4: Unavailable Frictionless Authentication. For test case 2.5: Rejected Frictionless Authentication,the expected AVV returned in the test was also updated to indicate that no value should be returned. See 2.5: Frictionless Authentication Is Rejected.

Various editorial changes were made throughout the guide. These changes did not include technical updates.

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

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

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

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

Updated the payload code samples to eliminate the use of the

clientReferenceInformation.code

field because it is not a required field and does not need to be in the code example.

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

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

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 when checking enrollment and validation. For more information, see Optional Fields.

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 2.6: Authentication Is Not Available.

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 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.

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 2.5: Frictionless Authentication Is Rejected.

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

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 Checking Enrollment When Using a TMS Token.

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.

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.