English
Welcome to Testlabs. Please not that the information on this page is no longer current. If you would like to access the most up-to-date content on our 3D Secure Testing solution, we encourage you to explore our new Testing page accessible via our website menu or click the button below.
Stay Current: Visit Our New Testing Page
TestLabs is an end-to-end 3D Secure authentication testing environment. TestLabs can be used by anyone looking to implement an existing 3D Secure solution, or build their own 3D Secure product. TestLabs can be used to test any 3DS 1 or 2 component, or to perform product integration testing.
Unlike many test tools that utilise simulators, TestLabs comprises live and fully developed 3D Secure components: ActiveServer (a 3DS2 3DS Server), ActiveMerchant (a 3DS1 MPI), ActiveAccess (an Access Control Server), and ActiveDS (a Directory Server). This provides our users with more realistic test results, as well as the flexibility to specify custom test cases.
You can use TestLabs to make sure all your test scenarios output the correct results before you start card scheme certification. This will help you to pass card scheme certification much faster, and potentially save you money on time-based costs, during certification testing.
By subscribing to TestLabs, you can periodically run test cases to make sure all authentication scenarios in your payment system are working as intended. This is particularly useful after any configuration changes or product version upgrades.
For more than 15 years, GPayments products have been trusted by major banks, payment gateways, and large merchants from all around the world to be stable, high performing, and easy to use.
TestLabs includes a wide range of pre-defined test cases for both 3DS2 and 3DS1 to enable testing for your 3DS Server (3DSS) or Merchant Plug-In (MPI) respectively. You can test many permutations of card schemes, authentication channels and test scenarios. All major testing scenarios are covered, however customisation of merchant/acquirer data is also possible.
3DS Server/MPI testing is initiated by the merchant or gateway using their test systems or merchant site. The TestLabs’ ACS and DS are setup with the test card numbers for various scenarios and acquirer and merchant details. GPayments software comes pre-configured with TestLabs connectivity information, however it is also possible to connect software from other vendors as well.
There are many ways TestLabs can support your testing needs:
Once a 3DS solution has been installed and configured, TestLabs can be used to verify that the application has the correct connectivity and configuration setup. This process will verify the necessary 3DS configurations of the application as well as the implementer's network settings, which is required for connectivity to other components of the 3DS ecosystem.
After successful implementation and testing of 3DS components but prior to production rollout, the card schemes require implementers to undertake compliance testing; for example, Visa requires testing on its VSTS environment. As TestLabs includes all the necessary components of 3DS, it can be utilised for compliance testing of any 3DS components, before card scheme testing is conducted.
By first using TestLabs to ensure correct integration, implementers can significantly reduce the time and cost required for card scheme testing. Fees apply for testing with some card schemes, and if the testing is not completed successfully within a certain time period, testing has to be rescheduled and re-test fees can be incurred.
Implementers may wish to test the responses received by their 3DS components during 3DS transactions, using different scenarios. This is especially useful for testing corner cases such as timeouts and other error scenarios.
TestLabs provides the ability to test 3DS components using test cards for different card schemes and scenarios, as shown in the table to the right.
3DSS/MPI implementers can utilise TestLabs to perform ongoing functional testing, to ensure the stability and integrity of their 3DS components, or for testing updated specifications and requirements, received from the card schemes.
TestLabs can also be used to allow new merchant clients, of a payment gateway, to test during their initial setup and onboarding process.
With the large amount of possible card configurations in an ACS, TestLabs can help issuing banks to test whether those cards are correctly configured, and produce the intended results, under each scenario. Additionally, TestLabs can be used, similarly, to test card scenarios when upgrading to a newer version ACS.
For ACS testing, TestLabs 3DS Server and Directory Server are configured with the card range of the test cards, acquirer and merchant details, and the URL of the tester’s ACS. The test cards for the various scenarios are set up on the tester’s ACS.
The tester uses the test cards to make purchases through any of the three device channels (browser-based, 3RI, or app-based) on a fully-featured 3DS Requestor. The PAN received by the tester’s ACS, in the message sent from GPayments DS, is used to determine the required interactions and make a corresponding response.
There are many ways TestLabs can support your testing needs:
Once a 3DS solution has been installed and configured, TestLabs can be used to verify that the application has the correct connectivity and configuration setup. This process will verify the necessary 3DS configurations of the application as well as the implementer's network settings, which is required for connectivity to other components of the 3DS ecosystem.
Prior to production rollout, after successful implementation and testing of 3DS components, the card schemes require implementers to undertake compliance testing; for example, Visa requires testing on its VSTS environment. As TestLabs includes all the necessary components of 3DS, it can be utilised for compliance testing of any 3DS components, including the ACS, before card scheme testing is conducted.
By first using TestLabs to ensure correct integration, implementers can significantly reduce the time and cost required for card scheme testing. Fees apply for testing with some card schemes, and if the testing is not completed successfully within a certain time period, testing has to be rescheduled and re-test fees can be incurred.
ACS implementers may wish to test the responses received by their ACS during 3DS transactions, for different scenarios.
TestLabs provides the ability to test the ACS by performing transactions with test cards that have been setup for different scenarios and for different card schemes.
ACS implementers can utilise TestLabs to perform ongoing functional/performance testing to ensure the stability and integrity of their 3DS components.
Testing for:
TestLabs includes a wide range of pre-defined test cases for both 3DS2 and 3DS1 to enable testing for your 3DS Server (3DSS) or Merchant Plug-In (MPI) respectively. You can test many permutations of card schemes, authentication channels and test scenarios. All major testing scenarios are covered, however customisation of merchant/acquirer data is also possible.
3DS Server/MPI testing is initiated by the merchant or gateway using their test systems or merchant site. The TestLabs’ ACS and DS are setup with the test card numbers for various scenarios and acquirer and merchant details. GPayments software comes pre-configured with TestLabs connectivity information, however it is also possible to connect software from other vendors as well.
There are many ways TestLabs can support your testing needs:
Once a 3DS solution has been installed and configured, TestLabs can be used to verify that the application has the correct connectivity and configuration setup. This process will verify the necessary 3DS configurations of the application as well as the implementer's network settings, which is required for connectivity to other components of the 3DS ecosystem.
After successful implementation and testing of 3DS components but prior to production rollout, the card schemes require implementers to undertake compliance testing; for example, Visa requires testing on its VSTS environment. As TestLabs includes all the necessary components of 3DS, it can be utilised for compliance testing of any 3DS components, before card scheme testing is conducted.
By first using TestLabs to ensure correct integration, implementers can significantly reduce the time and cost required for card scheme testing. Fees apply for testing with some card schemes, and if the testing is not completed successfully within a certain time period, testing has to be rescheduled and re-test fees can be incurred.
Implementers may wish to test the responses received by their 3DS components during 3DS transactions, using different scenarios. This is especially useful for testing corner cases such as timeouts and other error scenarios.
TestLabs provides the ability to test 3DS components using test cards for different card schemes and scenarios, as shown in the table to the right.
3DSS/MPI implementers can utilise TestLabs to perform ongoing functional testing, to ensure the stability and integrity of their 3DS components, or for testing updated specifications and requirements, received from the card schemes.TestLabs can also be used to allow new merchant clients, of a payment gateway, to test during their initial setup and onboarding process.
TestLabs includes a wide range of pre-defined test cases for both 3DS2 and 3DS1 to enable testing for your 3DS Server (3DSS) or Merchant Plug-In (MPI) respectively. You can test many permutations of card schemes, authentication channels and test scenarios. All major testing scenarios are covered, however customisation of merchant/acquirer data is also possible.
3DS Server/MPI testing is initiated by the merchant or gateway using their test systems or merchant site. The TestLabs’ ACS and DS are setup with the test card numbers for various scenarios and acquirer and merchant details. GPayments software comes pre-configured with TestLabs connectivity information, however it is also possible to connect software from other vendors as well.
There are many ways TestLabs can support your testing needs:
Once a 3DS solution has been installed and configured, TestLabs can be used to verify that the application has the correct connectivity and configuration setup. This process will verify the necessary 3DS configurations of the application as well as the implementer's network settings, which is required for connectivity to other components of the 3DS ecosystem.
After successful implementation and testing of 3DS components but prior to production rollout, the card schemes require implementers to undertake compliance testing; for example, Visa requires testing on its VSTS environment. As TestLabs includes all the necessary components of 3DS, it can be utilised for compliance testing of any 3DS components, before card scheme testing is conducted.By first using TestLabs to ensure correct integration, implementers can significantly reduce the time and cost required for card scheme testing. Fees apply for testing with some card schemes, and if the testing is not completed successfully within a certain time period, testing has to be rescheduled and re-test fees can be incurred.
Implementers may wish to test the responses received by their 3DS components during 3DS transactions, using different scenarios. This is especially useful for testing corner cases such as timeouts and other error scenarios.TestLabs provides the ability to test 3DS components using test cards for different card schemes and scenarios, as shown in the table to the right.
3DSS/MPI implementers can utilise TestLabs to perform ongoing functional testing, to ensure the stability and integrity of their 3DS components, or for testing updated specifications and requirements, received from the card schemes.TestLabs can also be used to allow new merchant clients, of a payment gateway, to test during their initial setup and onboarding process.
As a sister company of GPayments, MemberCheck is dedicated to delivering cutting-edge services that empower your business to proactively manage risk and comply with regulatory requirements. Imagine blending MemberCheck with GPayments' solutions; a powerhouse duo engineered to strengthen your fraud prevention and risk management strategies. As GPayments' solutions help you combat chargebacks, false declines, and maintain compliance with regulations like SCA and PSD2, MemberCheck strides alongside to keep you aligned with AML/CTF regulations while safeguarding your reputation.
Visit membercheck.com for More Information
Sales/ Other Requests
Our AML Risk &
Compliance Solution
Fraud prevention solutions from a market leader of over 20 years, safeguarding the payment ecosystem end‑to‑end through industry standards such as EMVCo 3D Secure and global card scheme authentication programs.
