My Profile_


Testing 3-D Secure (MPI) Solutions

Test Case Description PAN to Use Status Merchant Action ECI
#1 Successful Frictionless Authentication 345123377100973 (Amex)
4606633870436092 (VISA)
5230568531336508 (MC)
Y Merchant should add the Cavv and ECI Flag values to the authorization message ECI Value = 5
#2 Failed Frictionless Authentication  345382387492412 (Amex)
4932396190056256 (VISA)
4362475556648911 (MC)
N Merchant can still authorize a failed 3DS as a non-authenticated transaction ECI Value = 7
#3 Stand-In Frictionless Authentication  377832655974658 (Amex)
4082745347214523 (VISA)
5259767577332563 (MC)
A Merchant should add Cavv and ECI Flag to the authorization message ECI Value = 6

#4 Unavailable Frictionless Authentication from the Issuer  379101644522095 (Amex)
4776012964731 (VISA)
5237684141956495 (MC)
U Merchant should proceed with the authorization message ECI Value = 7

#5 Rejected Frictionless Authentication by the Issuer  374588895473074 (Amex)
4814556895159 (VISA)
5405903043090336 (MC)
R Merchant should NOT continue with authorization. Merchant should prompt for another form of payment and is not permitted to submit this transaction for authorization ECI Value = 7

#6 Authentication Not Available on Lookup  3400200000001000046 (Amex)
4000200000001000046 (VISA)
5100200000001000046 (MC)
U Merchant should proceed with the authorization message ECI Value = 7
#7 Timeout on cmpi_lookup Transaction  It is NOT card range driven. Instead UL made it so it times out when certain message extension is received in AReq. The exact message extension is shown below:
{
    "id": "mock-acs.instruction",
    "name": "mock-acs.instruction",
    "criticalityIndicator": false,
    "data": { "simulate_timeout": true }
}

So, the customer is advised to use the AReqEditor feature of Merchant Simulator in order to include a message extension like that in AReq. That'll cause the DS to time out.
BLANK Merchant should proceed with the authorization message ECI Value = 7

#8 Successful Step Up Authentication 375385736970742 (Amex)
4740611374762707 (VISA)
5114555023664993 (MC)
C - Lookup
Y - Authentication
Merchant should add the Cavv and ECI Flag values to the authorization message ECI Value = 7

#9 Failed Step Up Authentication 348516906814237 (Amex)
4414503750667698 (VISA)
5149970949503408 (MC)
C - Lookup
N - Authentication
Merchant should NOT continue with authorization. Merchant should prompt for another form of payment and is not permitted to submit this transaction for authorization ECI Value = 7

#10 Step Up Authentication is Unavailable 348080741557444 (Amex)
4992469070373 (VISA)
5421968653805752 (MC)
C - Lookup
U - Authentication
Merchant can retry authentication or process authorization as merchant liability ECI Value = 7

#11 Require MethodURL  It is message extension driven, to force ACS to check whether the prior 3DS method should have have taken place and fail otherwise, the following message extension is advised to be made using the AReqEditor feature:
{
    "id": "mock-acs.instruction",
    "name": "mock-acs.instruction",
    "criticalityIndicator": false,
    "data": { "require_threeds_method": true }

So, the customer is advised to use the AReqEditor feature of Merchant Simulator in order to include a message extension like that in AReq. That'll cause the DS to time out.
Y Merchant should proceed with the authorization message ECI Value = 7