Testing 3DS2 Enabled Payment Gateway:

Make sure you have created a test payment gateway with 3DS2 enabled before attempting to test. Directions are available on Configuring A Payment Gateway With 3DS2. Stripe Payment Gateways require a different type of testing workflow. Directions are available on Configuring A Stripe Payment Gateway With 3DS2.

When your Merchant Profile is ready, you can start testing your test payment gateway with 3DS2 enabled. You will utilize a test credit card provided by Spreedly to perform tests. Testing with this card requires specific amounts in the Order Total at checkout in your Community Portal to generate different test scenarios.

The amounts for test scenarios must be exact in order to generate the desired scenario. If they are off by even a cent, the desired test result will not generate. You will want to create your own set of testing items for each scenario. Be sure to take into mind Shipping and Tax fees for items when performing a test.

Information on creating Items can be found here. Remember the requirements for SCA transactions. Transactions made on the backend will not be challenged by 3DS2. Other out-of-scope transactions are listed on Meeting SCA Requirements With 3DS2.

Test Credit Card

Use this test credit card from Spreedly to run your test scenarios.

Card Number

CVV

Expiration

Type

5555555555554444

123

10/2029

3D Secure Enrolled Card

Amounts For Test Scenarios:

Checking out from your Community Portal with these specific amounts will generate the corresponding test scenarios results. Each scenario allows you to test a different kind of gateway success or failure and any corresponding challenges to authentication.

Spreedly’s information on testing is available here.

Amount

Response Status

Flow

Result

00.04

Y

Frictionless

Authentication and account are verified.

1000.00

C

Challenge

Authentication requires a Challenge by the issuing bank. This is handled by Lifecycle.

99.96

A

Frictionless

ACS could not be reached, but authentication and account verification was performed by the issuing bank.

99.97

U

Denied

Authentication and account verification could not be performed. The transaction fails.

99.98

N

Denied

Not authenticated and account not verified. The transaction fails.

99.99

R

Denied

Authentication and account verification is rejected. The transaction fails.

Challenge Page:

When presented with a challenge, a test ACS challenge page from Spreedly will open. Entering the code 123456 will result in a successful authentication.

Spreedly’s 3DS2 solution partners are in Spain, so this test challenge page may display in Spanish. This will only occur when working in the test Spreedly gateway. For real 3DS2 authentications, the acquiring bank’s challenge page will display instead. Enter 123456 in Código de verifación: and click Continuar.