Skip to content

DS Profiles

ActiveServer supports DS Profiles which allows a single instance to connect to both card scheme Production Directory Servers and the GPayments TestLabs:

  • Production Directory Servers: The card schemes (Visa, Mastercard, JCB, American Express and Discover) directory servers that were set on the Directory Servers page.
  • 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.

TestLabs setup

If ongoing access to the TestLabs is required, additional ports must be opened for TestLabs DS communications. This will allow testing with TestLabs in parallel with using the production card scheme Directory Servers. The additional ports should be externally accessible from the GPayments TestLabs Directory Server. The settings should be added to your application-prod.properties, with example properties shown below:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
##-----------------------------------------------------------------
## GPayments TestLabs DS ports
##
## DS ports used to connect from GPayments TestLabs directory servers
##-----------------------------------------------------------------

## Visa TestLabs
as.testlab.visa.port=9800
## Set to false to disable DS HTTPS listening port
# as.testlab.visa.enabled=false

## Mastercard TestLabs
as.testlab.mastercard.port=9801
## Set to false to disable DS HTTPS listening port
# as.testlab.jcb.enabled=false

## American Express TestLabs
as.testlab.amex.port=9802
## Set to false to disable DS HTTPS listening port
# as.testlab.amex.enabled=false

## Discover TestLabs
as.testlab.discover.port=9803
## Set to false to disable DS HTTPS listening port
# as.testlab.discover.enabled=false

## JCB TestLabs
as.testlab.jcb.port=9804
## Set to false todisable DS HTTPS listening port
# as.testlab.jcb.enabled=false

For full information on setting the application-prod.properties, refer to the quickstart guide.

Transaction type parameter

To utilize DS Profiles, a trans-type query parameter is needed in the authentication url for switching between Production Directory Servers and TestLabs. By default, all authentication requests will be sent to the GPayments TestLabs directory server, for testing purposes. When moving into production, to send API requests to the card scheme directory servers, the trans-type=prod query parameter must be appended to the API URL.

Why is the trans-type=prod query parameter needed?

Adding the parameter trans-type in the API url is to make sure the authentication requests will not be accidentally sent to card scheme directory server before all testing has been completed and all configuration has been completed.

If you want to send the authentication requests to the production Directory Server, you need to add the trans-type=prod parameter in:

  • InitAuth processes for BRW transaction
  • Auth processes for App and 3RI transaction
  • Enrol endpoint.

For example, InitAuth will be called with following URL https://api.testlab.3dsecure.cloud/api/v2/auth/brw/init?trans-type=prod for production directory server.

As mentioned above, if this parameter is not provided, the authentication requests will be sent to the GPayments TestLabs. Check the API document for more API usage details.

Why the trans-type parameter doesn't work as expected?

Please make sure the server side configuration as.auth.allowed-trans-type has not been set which overrides the API parameter. Check the details in the quickstart guide.