TestLabs
The GPayments TestLabs consists of a live Directory Server and Access Control Server. It has different cardholder scenarios setup for clients to perform functional testing with their ActiveServer instance. All card schemes supported by ActiveServer are supported by TestLabs.
Integrating with ActiveServer
For information on integrating with ActiveServer to make a test transaction, you can refer to the integration guides.
TestLabs setup¶
For all TestLabs transactions, the default merchant (Test Merchant, with Merchant ID 123456789012345) must be used. This includes using the client certificate available in it's merchant profile.
The following fields must also be used when performing a transaction:
- Card holder name - value must either be
Test Card
or an empty value - Expiry date (YYMM) - value must either be
2508
or an empty value
Warning
Not setting the above values correctly will cause the transaction to fail.
TestLabs scenarios¶
The below scenarios can be initiated by using the listed card numbers when performing a transaction with the GPayments TestLabs:
Authentication success - frictionless¶
- Description - Transaction will complete without any challenge from the ACS.
- ARes result:
- Transaction Status = Y
- ECI = 05 or 02 (Mastercard)
- Authentication Value is present
Card numbers:
Visa Mastercard JCB American Express Discover 4100000000000100 5100000000000107 3528000000000106 340000000000108 6440000000000104
Authentication success - challenge¶
- Description - Transaction will step up to a challenge using a password. Enter the password "123456" and submit to complete the transaction.
- ARes result:
- Transaction Status = C
- RReq result:
- Transaction Status = Y
- ECI = 05 or 02 (Mastercard)
- Authentication Value is present
Card numbers:
Visa Mastercard JCB American Express Discover 4100000000005000 5100000000005007 3528000000005006 340000000005008 6440000000005004
Authentication attempt¶
- Description - Transaction will attempt to perform authentication, before returning an attempts response.
- ARes result:
- Transaction Status = A
- ECI = 06 or 01 (Mastercard)
- Authentication Value is present
Card numbers:
Visa Mastercard JCB American Express Discover 4100000000100009 5100000000100006 3528000000100005 340000000100007 6440000000100003
Card not enrolled¶
- Description - Transaction is performed using a card that is not enrolled in 3DS2, that will return a not authenticated response.
- ARes result:
- Transaction Status = N
- Transaction Status Reason = 08 (No card record)
- ECI is not present
- Authentication Value is not present
Card numbers:
Visa Mastercard JCB American Express Discover 4100000000200007 5100000000200004 3528000000200003 340000000200005 6440000000200001
Authentication failed¶
- Description - Transaction will step up to a challenge using a password. Enter the password "111111" and submit to simulate the cardholder not being authenticated.
- ARes result:
- Transaction Status = C
- RReq result:
- Transaction Status = N
- ECI = 00
- Authentication Value is not present
Card numbers:
Visa Mastercard JCB American Express Discover 4100000000300005 5100000000300002 3528000000300001 340000000300003 6440000000300009
Authentication unavailable¶
- Description - Transaction will end with authentication unavailable, due to a simulated technical error with the ACS.
- ARes result:
- Transaction Status = U
- ECI is not present
- Authentication Value is not present
Card numbers:
Visa Mastercard JCB American Express Discover 4100000000400003 5100000000400000 3528000000400009 340000000400001 6440000000400007
Authentication rejected¶
- Description - Transaction will end with the authentication being rejected by the ACS.
- ARes result:
- Transaction Status = R
- ECI is not present
- Authentication Value is not present
Card numbers:
Visa Mastercard JCB American Express Discover 4100000000500000 5100000000500007 3528000000500006 340000000500008 6440000000500004