NDM Simulator Integration with the 3DS Server

3DS Server 2.x

Once the Netcetera Demo Merchant Simulator is up and running, the following endpoints of the NDM Simulator should be configured in the 3DS Server Timeout Configuration:

  • The Results Response Notification Url - fully-qualified-url-of-simulator/requestor/results-notification
  • The Notification Url - fully-qualified-url-of-simulator/requestor/challenge-notification
  • The ThreeDS Requestor Url - fully-qualified-url-of-simulator/shop

Scheme Directory Server configuration

Since the NDM Simulator simulates a Directory Server, Scheme(s) should be configured in the 3DS Server Configuration having the NDM Simulator endpoints as Directory Server endpoints.

For handling authentication requests the NDM Simulator exposes the following endpoint:

  • fully-qualified-url-of-simulator/ds/authentication

This endpoint should be configured as primary endpoint of the Directory Server (in the url property).

For handling preparation requests the NDM Simulator exposes the following endpoints (all simulate different responses):

  • fully-qualified-url-of-simulator1/ds/valid-pres-configured-card-range-data
  • fully-qualified-url-of-simulator/ds/valid-pres-add-card-range-data
    • The returned Preparation Response includes the following card ranges having action indicator ADD: [4000001000000000, 4000001999999999], [4000003000000000, 4000003999999999], [4000007000000000, 4000007999999999] and [5000001000000000, 5000007999999999].
    • Furthermore, there are a few optional query parameters available for you to customize the card ranges according to your requirements:
      • rangesCount - determines the number of new card ranges
      • bin - specifies the bin, with a default value of 400000
      • panLength - sets the card length, with a default value of 16
      • numOfRangesPerElement - determines the number of card ranges per element, with a default value of 1
  • fully-qualified-url-of-simulator/ds/valid-pres-custom-card-range-data
    • Designed for customization and includes the following optional query parameters:
      • actionInd - the action indicator, by default is "ADD"
      • rangesCount - determines the number of new card ranges, by default has length of 10000
      • bin - specifies the bin, with a default value of 400000
      • panLength - sets the card length, with a default value of 16
      • numOfRangesPerElement - determines the number of card ranges per element, with a default value of 1
  • fully-qualified-url-of-simulator/ds/pres-error-request-validation-failed
    • The returned Preparation Response indicates validation error (invalid threeDSServerRefNumber) in the preparation request.
  • fully-qualified-url-of-simulator/ds/pres-error-request-missing-data
    • The returned Preparation Response indicates missing data in the preparation request.
  • fully-qualified-url-of-simulator/ds/pres-error-request-invalid-serial-num
    • The returned Preparation Response indicates invalid serial number in the preparation request.
  • fully-qualified-url-of-simulator/ds/pres-error-request-sent-messages-limit-exceeded
    • The returned Preparation Response indicates the limit is exceeded for sending preparation request messages.
  • fully-qualified-url-of-simulator/ds/valid-pres-delete-card-range-data
    • The returned Preparation Response includes the following card ranges having action indicator DELETE: [4000003000000000, 4000003999999999].
  • fully-qualified-url-of-simulator/ds/timeout-pres
    • The returned Preparation Response is returned with a timeout of 5 seconds.
  • fully-qualified-url-of-simulator/ds/invalid-pres-missing-data
    • The returned Preparation Response is empty.
  • fully-qualified-url-of-simulator/ds/valid-pres-card-range-data-file-url
    • The returned Preparation Response includes fully qualified URL of the DS File containing the Card Range Data for download if the cardRangeDataDownloadInd is Y in the Preparation Request, otherwise the returned Preparation Response will include some configured card ranges. This behavior is supported since 2.3.1 protocol version.

Any of the these endpoints could be configured as a preparation endpoint of the Directory Server (in the preparationUrl property).

Best practise would be to configure multiple Schemes, like the example below. At the startup of the 3DS Server it will send preparation requests to all directory servers' preparation endpoints and different types of preparation responses will be simulated from the NDM Simulator.