---
title: LexisNexis OTP Decision node
description: The LexisNexis OTP Decision node compares the OTP code entered by the user with the one in the shared state.
component: auth-node-ref
version: latest
page_id: auth-node-ref:cloud:lexis-otp-decision
canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/cloud/lexis-otp-decision.html
keywords: ["Authenticator", "LexisNexis OTP", "OTP Decision"]
page_aliases: ["auth-node-lexis-otp-decision.adoc"]
section_ids:
  example: Example
  availability: Availability
  inputs: Inputs
  dependencies: Dependencies
  configuration: Configuration
  outputs: Outputs
  outcomes: Outcomes
  troubleshooting: Troubleshooting
---

# LexisNexis OTP Decision node

The LexisNexis OTP Decision node compares the OTP code entered by the user with the one in the shared state.

## Example

Read the [Example LexisNexis OTP journey](lexis-otp.html#lexis-otp-example).

## Availability

| Product                               | Available? |
| ------------------------------------- | ---------- |
| PingOne Advanced Identity Cloud       | Yes        |
| PingAM (self-managed)                 | Yes        |
| Ping Identity Platform (self-managed) | Yes        |

## Inputs

None. This node doesn't read shared state data.

## Dependencies

Requires [LexisNexis OTP Sender node](lexis-otp-sender.html) and [LexisNexis OTP Collector node](lexis-otp-collector.html) to be configured in the journey. Typically, the LexisNexis OTP Collector node precedes this node in an authentication journey. The collector node places the OTP submitted by the user in shared state. Additionally, the LexisNexis OTP Sender node precedes the LexisNexis Collector node, which places the characteristics of the OTP into shared state.

## Configuration

| Property    | Usage                                                                                   |
| ----------- | --------------------------------------------------------------------------------------- |
| **Org ID**  | The unique ID associated with your organization in the Dynamic Decision Platform (DDP). |
| **API Key** | The unique API key generated by the DDP portal and associated with the `Org ID`.        |

## Outputs

In case of an `Error` outcome, the error message is output to the shared state.

## Outcomes

* `Pass`

  The OTP code submitted by the user is valid, and MFA using OTP is successful.

* `Challenge`

  The OTP code submitted by the user failed validation, and the permitted retry limit has not been reached. This outcome must be linked to the [LexisNexis OTP Collector node](lexis-otp-collector.html).

* `Review`

  The user submitted blank OTP code. This outcome must be linked to the [LexisNexis OTP Collector node](lexis-otp-collector.html).

* `Reject`

  The user submitted OTP code is invalid and the retry limit has been reached.

* `Error`

  There is an integration error. Check the debug log files for any integration issues.

## Troubleshooting

If this node logs an error, review the log messages to find the reason for the error. If the configuration looks accurate, open a support case with LexisNexis.