NuDetect Risk Provider

Perform a Create Session operation to obtain a session ID. Once you create a session, you can update the session with the request fields and values you wish to store in the session.

Create Session API Reference[REST][NVP]

On your payment page, reference the Risk JS API (risk.js) from the gateway servers. This will place a risk object into the window/global namespace.

https://ap-gateway.mastercard.com/static/risk-core/1.0.0/risk.min.js

risk.js Reference[JavaScript]

Inserting the Form Hidden Input Element

Note that upon completing the configuration using Risk.configure( ) method, the Risk JS SDK creates the following hidden input element inside the <form> element on the payment page, which is usually a wrapper for card details. The Risk JS SDK generates fingerprint data inside the hidden input element when the payer starts interacting with the payment page, for example, key strokes, moving or clicking mouse, etc.

<input name="nds-pmd" type="hidden">

If your payment page does not have a <form> element, you must manually insert the hidden input element, for example, <input name="nds-pmd" type="hidden"> before executing Risk.configure( ) method.

Risk JS Initialization Request

Once you have created a session, initialize the API using the Risk.configure( ) method. This method should be called during the page load or when the DOM is in ready state. It should be called only once for the page load. After calling this method, Risk JS will provide configuration values as member variables.

Provide the following mandatory fields as arguments to the riskConfig object:

• merchantId: Your merchant identifier on the gateway.
• sessionId: The session Id that you created using the Create Session call.
• apiVersion: (Optional) The API version of the request. If you do not provide a value, the apiVersion defaults to 56.
• riskProvider: (Optional) The identifier of the risk service provider on the gateway. Currently, only NUDETECT risk service provider is supported via Risk JS API. If you do not provide a risk service provider, the Risk JS API will make a Payment Options Inquiry request to determine the supported risk provider.

Callback Function

You can provide an optional callback function in the Risk.configure() method, which will be invoked with the response object as an argument upon completion of the method. The response object will contain message and status properties to indicate whether the configuration was successful or failed due to an error.

If the configuration was successful:

{ status: "SUCCESS", message: "Risk SDK is configured successfully."}

If the configuration failed:

{ status: "ERROR", message: "Error message"}

Risk.configure({
        merchantId: "TESTMERCHANT",
        sessionId: "SESSION0002899787259G30902270H6",
        apiVersion: 56,
        riskProvider: "NUDETECT"
    },
    function(response) {
        // Handle Risk.configure() response */

        console.log(response.message)
        // Configuration message: 'Risk SDK is configured successfully.'

        console.log(response.status)
        // Configuration status: 'SUCCESS' or 'ERROR'
    }
);

You can add or update fields in the session you created in Step 1 using the Update Session call. It allows you to add payment and payer data into a session that can subsequently become the input to a Verify, Authorize or Pay operation to determine the risk associated with a payer. Perform Update Session when the payer clicks the "Pay Now" button.

Mandatory Fields

• device.fingerprint: Provide the value of the hidden input element as described in step 2. The hidden input element contains the payer fingerprint data as captured by the Risk JS SDK.
• sourceOfFunds.provided.card.*: Details of the card being used for the payment.
• order.amount
• order.currency: The currency of the order.
• transaction.id: A unique identifier for this payment authentication.
• order.id: A unique identifier for this order.

Please note that you cannot remove fields from a session but can only overwrite values for existing fields.

Update Session API Reference[REST][NVP]

If Update Session was successful, the returned session will contain the payer's payment details from the interaction. Use the returned session to present an order confirmation page or to submit a payment to the gateway. See Perform an Operation Using the Session..