Challenges of the Risk Management Component

Intelligent Adaptive Authentication with the Risk Management component can challenge the user in multiple aspects during login and adaptive authentication, event validation, or transaction activities.

Risk Management component challenges

When Intelligent Adaptive Authentication validates adaptive authentication and transaction requests, the response of this request to the Risk Management component includes the authentication or transaction validation challenge (specified in the riskResponseCode field). These challenges can then be used in the remaining processing flow. Risk management challenges provides a list of these challenges.

Matched Risk Management component rules

Intelligent Adaptive Authentication also provides information about which of the rules defined in the Risk Management component for monetary and non-monetary events matched. The adaptive authentication or transaction validation returns identifiers based on the API field in the output. You can check these identifiers in the event lookup to see all details associated with this event and verify which of the Risk Management component rules have matched. Names of matched rules from the Risk Management component provides a list of these identifiers.

To retrieve information about matched rules for an event

• Issue a request to retrieve the event ID with events/{eventID}.

  • Method: GET

  • Response body: eventID

    The response body contains one or several of the values identified as non-monetary event in the Non-monetary event column of Names of matched rules from the Risk Management component.

You can check events for matched rules during adaptive authentication and event validation with the following endpoints:

• POST /users/{userID@domain}/events/validate

• POST /users/{userID@domain}/login

  The responses of these endpoints also include the (optional) eventID field.

To retrieve information about matched rules for a transaction

• Issue a request to retrieve the transaction ID with transactions/{transactionID}.

  • Method: GET

  • Response body: transactionID

    The response body contains one or several of the values identified as transaction (i.e., monetary event) in the Transaction (monetary event) column of Names of matched rules from the Risk Management component.

You can check events for matched rules during adaptive transaction validation with the following endpoint:

• POST /users/{userID@domain}/transactions/validate

  The response of this endpoint also includes the (optional) transactionID field.