Payer Authentication Exemption Test Cases
On This Page
- 1a: First Recurring Transaction: Fixed Amount
- 2a: Card Authentication Failed
- 2b: Suspected Fraud
- 2c: Cardholder Not Enrolled in Service
- 2d: Transaction Timed Out at the ACS
- 2e: Non-Payment Transaction Not Supported
- 2f: 3RI Transaction Not Supported
- 3a: Transaction Risk Analysis Exemption—Low Value: Mastercard EMV 3-D Secure 2.1 and 2.2
- 3b: Transaction Risk Analysis—Low Value: Visa
- 3c: Transaction Risk Analysis—Low Value: Discover
- 3d: Acquirer Transaction Risk Analysis: Cartes Bancaires
- 4a: Trusted Beneficiary Prompt for Trustlist
- 4b: Utilize Trusted Beneficiary Exemption
- 5a-1: Identity Check Insights (ScoreRequest = N)
- 5a-2: Identity Check Insights (ScoreRequest = Y)
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.
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
subscription purchases. For more information, see Requester Initiated Payments.
Card Type | Test Card Number |
|---|---|
Mastercard Card Type = 002 | 520000 00 0000 2805 |
Required Fields for Check Enrollment
Message category =
01
Device channel =
APP
(01), 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
Status
= PENDING_AUTHENTICATION
VERes enrolled =
Y
PARes status =
C
CAVV = (No value provided)
ECI =
00
Results for the Validation Authentication Service
Status
= AUTHENTICATION_SUCCESSFUL
Authentication is validated.
PARes status =
Y
CAVV = <CAVV>
ECI =
07
Card Network and Version Specifications
Visa Secure 2.1 does not support this use case. Visa Secure 2.2 test cards are in
development.
For Mastercard Identity Check 2.1, 3RI is not supported for Payer Authentication.
Only the initial transaction is supported for recurring payments.
If you attempt to run a Device Channel of 3RI within Mastercard Identity Check 2.1,
you receive a transStatusReason=21 (3RI Transaction not Supported) reason and a
transaction status of
U
rather than Y
.In EMV 3-D Secure 2.2, Mastercard allocated a new ECI value, ECI 07, for 3RI
transactions. It is present on a Mastercard response message for this particular 3RI
scenario. For EMV 3-D Secure 2.1, Mastercard will continue to use ECI 02.
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. When
this cardholder information is returned, you must display this information within
your checkout experience. Card Type | Test Card Number |
|---|---|
Visa Card Type = 001 | 400000 00 0000 2040 |
Results for the Check Enrollment Service
Status
= AUTHENTICATION_SUCCESSFUL
VERes enrolled =
Y
PARes status =
N
CAVV = (No value provided)
Cardholder Info = <cardholder information>
ECI =
07
Reason code =
01
2b: Suspected Fraud
This test case scenario checks for suspected fraud.
Card Type | Test Card Number |
|---|---|
Visa Card Type = 001 | 400000 00 0000 2149 |
Results for the Check Enrollment Service
Status
= AUTHENTICATION_SUCCESSFUL
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.
Card Type | Test Card Number |
|---|---|
Visa Card Type = 001 | 400000 00 0000 2164 |
Results for the Check Enrollment Service
Status
= AUTHENTICATION_FAILED
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.
Card Type | Test Card Number |
|---|---|
Visa Card Type = 001 | 400000 00 0000 2172 |
Results for the Check Enrollment Service
Status
= AUTHENTICATION_SUCCESSFUL
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.
Card Type | Test Card Number |
|---|---|
Visa Card Type = 001 | 400000 00 0000 2230 |
Results for the Check Enrollment Service
Status
= AUTHENTICATION_SUCCESSFUL
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.
Card Type | Test Card Number |
|---|---|
Visa Card Type = 001 | 400000 00 0000 2248 |
Required Fields for Check Enrollment
Message category =
02
Device channel =
3RI (03)
Three RI Indicator =
01
Results for the Check Enrollment Service
Status
= AUTHENTICATION_SUCCESSFUL
VERes enrolled =
Y
PARes status =
U
CAVV = (No value provided)
ECI =
07
Reason code =
21
3a: Transaction Risk Analysis 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 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 3-D Secure versions.
Card Type | Test Card Number |
|---|---|
Mastercard Card Type = 002 | (version 2.1.0) 5200 00 00 0000 1161 (version 2.2.0) 5200 00 00 0000 2052 |
Required Fields for Check Enrollment
Challenge code =
05
Results for the Check Enrollment Service
Status
= AUTHENTICATION_SUCCESSFUL
Version 2.1.0
VERes enrolled =
Y
PARes status =
N
CAVV = <CAVV value>
ECI =
06
Reason code =
81
For Mastercard Identity Check, the Challenge Indicator should be passed as
05
.Version 2.2.0
VERes enrolled =
Y
PARes status =
I
CAVV = <CAVV value>
ECI =
06
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.
3b: Transaction Risk Analysis—Low Value: Visa
The merchant has performed a proprietary risk assessment based on fraud thresholds
established with the network. You are requesting an exemption for a low risk or low
value Visa transaction.
Card Type | Test Card Number |
|---|---|
Visa Card Type = 001 | 400000 00 0000 2024 |
Required Fields for Check Enrollment
Challenge code =
05
(no challenge requested)Results for the Check Enrollment Service
Status
= AUTHENTICATION_SUCCESSFUL
VERes enrolled =
Y
PARes status =
I
CAVV = <CAVV value>
ECI =
07
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.
3c: Transaction Risk Analysis—Low Value: Discover
The merchant has performed a proprietary risk assessment based on fraud thresholds
established with the network. You are requesting an exemption for a low risk or low
value Discover transaction.
Card Type | Test Card Number |
|---|---|
Discover Card Type = 004 | 601100 00 0000 1002 |
Required Fields for Check Enrollment
Challenge code =
04
(challenge requested)Results for the Check Enrollment Service
Status
= AUTHENTICATION_SUCCESSFUL
VERes enrolled =
Y
PARes status =
Y
CAVV = <CAVV value>
ECI =
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.
3d: Acquirer Transaction Risk Analysis: Cartes Bancaires
The merchant has performed a proprietary risk assessment based on fraud thresholds
established with the network. You are requesting an exemption for a low risk or low
value Cartes Bancaires transaction.
Card Type | Test Card Number |
|---|---|
Cartes Bancaires Visa Card Type = 036 | 400000 00 0000 3006 |
Cartes Bancaires Mastercard Card Type =036 | 520000 00 0000 3001 |
Required Fields for Check Enrollment
Challenge code =
05
(no challenge requested)Results for the Check Enrollment Service
Status
= AUTHENTICATION_SUCCESSFUL
VERes enrolled =
Y
PARes status =
Y
CAVV = <CAVV value> (The CAVV value is not returned during testing but
can be returned in production based on issuer rules surrounding co-branding with
Visa or Mastercard BINs.)
ECI = (no value provided)
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.
Card Type | Test Card Number |
|---|---|
Visa Card Type = 001 | 400000 00 0000 2008 |
Mastercard Card Type = 002 | 520000 00 0000 2003 |
Required Fields for Check Enrollment
Challenge code =
09
(challenge requested)Results for the Check Enrollment Service
With the Cardinal Cruise API, the response will also include a StepUpUrl.
VERes enrolled =
Y
PARes status =
C
CAVV = (No value provided)
ECI =
- Visa =07
- Mastercard =00
Results for the Authenticate Response
PARes status =
Y
CAVV = <CAVV value>
ECI =
- Visa =05
- Mastercard =02
WhiteListStatus = <WhiteListStatus value>
WhiteListStatusSource = <WhiteListStatusSource value>
Action
You should append the CAVV and ECI values to the authorization message.
4b: Utilize Trusted Beneficiary Exemption
There is a successful frictionless authentication transaction with a pre-whitelisted
indication and an accepted exemption result.
Card Type | Test Card Number |
|---|---|
Visa Card Type = 001 | 400000 00 0000 2016 |
Mastercard Card Type = 002 | 520000 00 0000 2011 |
Required Fields for Check Enrollment
Challenge code =
08
(No challenge requested)Results for the Check Enrollment Service
Status
= AUTHENTICATION_SUCCESSFUL
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-1: Identity Check Insights (ScoreRequest = N)
This request is for Mastercard Data Only authentication.
Card Type | Test Card Number |
|---|---|
Mastercard Card Type = 002 | 520000 00 0000 1005 |
Required Fields for Check Enrollment
MessageCategory =
80
Results for the Check Enrollment Service
Status
= AUTHENTICATION_SUCCESSFUL
PAResStatus =
U
CAVV = <CAVV value>
ECI =
04
StatusReason =
80
ThreeDSVersion = <ThreeDSVersion value>
Status
= AUTHENTICATION_SUCCESSFUL
Action
Append the ECI and Directory Server transaction ID values to the authorization
message.
5a-2: Identity Check Insights (ScoreRequest = Y)
This request is for Mastercard Data Only authentication.
Card Type | Test Card Number |
|---|---|
Mastercard Card Type = 002 | 520000 00 0000 1005 |
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
Status
= AUTHENTICATION_SUCCESSFUL
PAResStatus =
U
CAVV = <CAVV value>
ECI =
04
StatusReason =
80
ThreeDSVersion = <ThreeDSVersion value>
Optional Results for the Check Enrollment Service (if ScoreRequest =
Y
)IDCI_Score =
9
IDCI_Decisions =
not low risk
IDCI_ReasonCode1 =
A
IDCI_ReasonCode2 =
GG
Results for the Authentication Result
Status
= AUTHENTICATION_SUCCESSFUL
Action
Append the ECI and Directory Server transaction ID values to the authorization
message.