Skip to content

Manage DS settings

All the settings for card schemes supported by ActiveServer can be managed from the Directory Servers page under the Settings tab. The tab has two sub menu items:

  • Production: card schemes (American Express, Discover, JCB, Mastercard, UnionPay and Visa) production directory servers
  • TestLab: GPayments TestLabs which 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. Majority of these settings cannot be edited as they are a preset configuration to support TestLabs. For more information, see the TestLabs guide.

User Access

A user requires the System admin role to manage DS settings.

Directory Server - Settings tab

To edit a card scheme's settings:

Select the appropriate card scheme tab at the top of the page to display its details.


The following settings can be edited:

  • Cache refresh interval - interval in which the PRes cache refreshes for all available card schemes. The PReq/PRes messages are utilised by ActiveServer to cache information about the Protocol Version Numbers(s) supported by available ACSs, the DS, and also any URL to be used for the 3DS Method call. The data will be organised by card range as configured by a DS. The information provided on the Protocol Version Number(s) supported by ACSs and the DS can be utilised in the App-based, Browser-based and 3RI flows. It is a 3DS2 specification requirement that this exchanges happens at least once every 24 hours and at most every hour. (unit: hours)
  • 3DS Server Operator ID - DS assigned 3DS Server identifier. Each DS can provide a unique ID to each 3DS Server on an individual basis, usually during or at the end of the card scheme compliance process. Requirements for the presence of this field in the AReq and PReq messages are DS specific.
  • HTTPS listening port - port that AS is listening on for HTTPS communications during authentications. This value is read from the configuration file for the corresponding DS setting and is used to listen for RReq requests.
  • Cache update - This is a switch to enable or disable the PReq/PRes process performed at an interval with the Directory Server. During the PReq/PRes process, ActiveServer caches the card ranges given in the PRes. The card range tab shows the card ranges that ActiveServer currently has in its cache for each Directory Server provider.
  • 3DS Server URL - fully qualified URL of the 3DS Server to which the DS will send the RReq message after the challenge has completed.

    • If there is no value set for a 3DS Server URL, a default URL will be populated. The default URL is populated by using the domain name from the External URL (or the API URL if present), and the corresponding DS port from the file.
    • For Production Directory Servers, the 3DS Server URL is fully customisable to your environment/load balancing setup and can be different to the server External URL.
    • For TestLabs, the 3DS Server URL must have the same domain as the server External URL (or the API URL if present).


    For the 3DS Server URL, URL validation is performed to ensure that the system functions will perform correctly. The validation checks to ensure no paths or query strings are included in the URL.

    E.g. https://domainname<:port> is allowed, whereas https://domainname<:port>/path?queryString would be rejected.


The following settings can be edited:

  • Preparation Response (PRes) - timeout interval for the PRes message
  • Authentication Response (ARes) - timeout interval for the ARes message

Server URLs

In the Server URLs section, the DS URLs can be input for the addresses of the card scheme DS.

The Default URL is used for AReq and PReq message communications with the DS provider.

The PReq URL can optionally be filled in if the DS provider has a separate PReq endpoint for those requests. If a value is entered in this field, it will override the Default URL. If this value is empty, ActiveServer will send PReq messages to the Default URL if it entered.


If you would like to disable the sending of messages for a card scheme, remove the URL for Default URL and PReq URL. This will disable sending of authentication requests to that card scheme and PReq/PRes processing will be disabled.