Additional Test Cases

These test cases cover payer authentication scenarios that can occur outside of typical testing. These special use cases might require including additional API fields to accommodate different data that is necessary for that test.

The test card numbers provided are formatted with Xs for zeroes in the card number. When testing with the card numbers, replace an X with a 0 (zero).

1a: First Recurring Transaction: Fixed Amount

The merchant initiates a 3RI recurring transaction of a fixed amount for a specified number of transactions or with no set number of transactions such as occurs with Requester Initiated Payments.

Required Fields for Check Enrollment:

• Message category = 01
• Device channel = APP (01) or BROWSER (02)
• Three RI Indicator = 01
• Challenge code = 03
• Authentication code = 02
• Purchase date = <yyyyMMDDHHMMSS>
• Recurring frequency = <1 to 31>
• Recurring end = <yyyyMMDD>

Results for the Check Enrollment Service:

• Response flag = PENDING_AUTHENTICATION
• VERes enrolled = Y
• PARes status = C
• CAVV = (No value provided)
• ECI = 00

Results for the Validation Authentication Service:

• PARes status = Y
• CAVV = <CAVV>

2a: Card Authentication Failed

This scenario tests how your system reacts to various Trans Status Reasons (failed, suspected fraud, and similar instances). When PAResStatus = N, the CardholderInfo field can be returned by the card issuer.

Results for the Check Enrollment Service:

• VERes enrolled = Y
• PARes status = N
• CAVV = (No value provided)
• ECI = 07
• Reason code = 01

2b: Suspected Fraud

This test case scenario checks for suspected fraud.

Results for the Check Enrollment Service:

• VERes enrolled = Y
• PARes status = U
• CAVV = (No value provided)
• ECI = 07
• Reason code = 11

2c: Cardholder Not Enrolled in Service

This test case scenario verifies whether the cardholder is enrolled in the service.

Results for the Check Enrollment Service:

• VERes enrolled = Y
• PARes status = R
• CAVV = (No value provided)
• ECI = 07
• Reason code = 13

2d: Transaction Timed Out at the ACS

This test case scenario verifies whether a transaction will time out at the Access Control Server (ACS). This test case is valid for both payer authentication and non-payer authentication transactions.

Results for the Check Enrollment Service:

• VERes enrolled = Y
• PARes status = U
• CAVV = (No value provided)
• ECI = 07
• Reason code = 14

2e: Non-Payment Transaction Not Supported

This test case scenario checks whether a non-payment transaction can occur. This test case is valid for both payer authentication and non-payer authentication transactions.

Results for the Check Enrollment Service:

• VERes enrolled = Y
• PARes status = U
• CAVV = (No value provided)
• ECI = 07
• Reason code = 20

2f: 3RI Transaction Not Supported

This test case scenario verifies whether the merchant can initiate a recurring 3RI transaction, such as with subscriptions.

Required Fields for Check Enrollment:

• Message category = 02
• Device channel = 3RI (03)
• Three RI Indicator = 01

Results for the Check Enrollment Service:

• VERes enrolled = Y
• PARes status = U
• CAVV = (No value provided)
• ECI = 07
• Reason code = 21

3a: TRA Exemption: Low Value: Mastercard EMV 3-D Secure 2.1 and 2.2

You have performed a proprietary risk assessment based on fraud thresholds established with the network. You are requesting an exemption from transaction risk analysis (TRA) because the Mastercard transaction is low risk or low value. Be sure to use the correct test card number for your version of EMV 3-D Secure. The PARes Status will differ between the EMV versions.

Required Fields for Check Enrollment:

• Challenge code = 05

Results (version 2.1.0):

• VERes enrolled = Y
• PARes status = N
• CAVV = <CAVV value>
• ECI = 06
• Reason code = 81

Results (version 2.2.0):

• VERes enrolled = Y
• PARes status = I
• CAVV = <CAVV value>
• ECI = 06

For Mastercard Identity Check, the Challenge Indicator should be passed as 05.

Action: Proceed to authorization. You can also request the transaction risk analysis exemption directly during authorization if the region and your agreements with your acquirer and the networks support it.

4a: Trusted Beneficiary Prompt for Trustlist

You have a successful traditional step-up (challenge) authentication transaction with a prompt for the Trustlist and an accepted exemption result.

Required Fields for Check Enrollment:

• Challenge code = 09 (challenge requested)

Results for the Check Enrollment Service: With the Direct API, the response also includes a StepUpUrl.

• VERes enrolled = Y
• PARes status = C
• CAVV = (No value provided)

Results for the Authenticate Response:

• PARes status = Y
• CAVV = <CAVV value>
• ECI: Visa = 05, Mastercard = 02
• WhiteListStatus = <WhiteListStatus value>
• WhiteListStatusSource = <WhiteListStatusSource value>

Action: Append the CAVV and ECI values to the authorization message.

4b: Use Trusted Beneficiary Exemption

There is a successful frictionless authentication transaction with a pre-approved indication and an accepted exemption result.

Required Fields for Check Enrollment:

• Challenge code = 08 (No challenge requested)

Results for the Check Enrollment Service:

• PARes status = Y
• CAVV = <CAVV value>
• ECI: Visa = 05, Mastercard = 02
• WhiteListStatus = <WhiteListStatus value>
• WhiteListStatusSource = <WhiteListStatusSource value>
• ThreeDSVersion = <ThreeDSVersion value>

Action: Append the CAVV and ECI values to the authorization message.

5a: Visa Data Only

This request is for Visa Data Only authentication. This is a frictionless experience — to share additional data with issuers before authorization, 3-D Secure Data Only provides a frictionless experience with EMV 3-D Secure.

Required Fields for Check Enrollment:

• ChallengeIndicator = 06

Results for the Check Enrollment Service:

• PAResStatus = I
• CAVV = <CAVV value>
• ECI = 07

Action: Append the ECI and Directory Server transaction ID values to the authorization message.

5b: Identity Check Insights (ScoreRequest = Y)

This request is for Mastercard Data Only authentication.

Required Fields for Check Enrollment:

• Message Category = 80

Optional Fields for Check Enrollment: Score Request = Y, Merchant Reason Code = A

Results for the Check Enrollment Service:

• PAResStatus = U
• CAVV = <CAVV value>
• ECI = 04
• StatusReason = 80
• ThreeDSVersion = <ThreeDSVersion value>

Optional Results (if ScoreRequest = Y):

• IDCI_Score = 9
• IDCI_Decisions = not low risk
• IDCI_ReasonCode1 = A
• IDCI_ReasonCode2 = GG

Action: Append the ECI and Directory Server transaction ID values to the authorization message.