---
title: LexisNexis DDP Review Status node
description: "The LexisNexis DDP Review Status node analyzes the DDP Query response and routes the journey based on the review status: Pass, Challenge, Review, or Reject."
component: auth-node-ref
version: latest
page_id: auth-node-ref:cloud:lexis-ddp-review-status
canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/cloud/lexis-ddp-review-status.html
llms_txt: https://docs.pingidentity.com/auth-node-ref/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: 2026-09-17T14:22:55Z
keywords: ["Nodes & Trees", "Journeys", "Authentication", "LexisNexis DDP", "Device Intelligence", "Review Status"]
page_aliases: ["threat-metrix-review-status.adoc"]
section_ids:
  example: Example
  availability: Availability
  inputs: Inputs
  dependencies: Dependencies
  configuration: Configuration
  outputs: Outputs
  callbacks: Callbacks
  outcomes: Outcomes
  errors: Errors
---

# LexisNexis DDP Review Status node

The LexisNexis DDP Review Status node analyzes the response from the [LexisNexis DDP Query node](lexis-ddp-query.html) and routes the journey based on the `review_status` API response. If an unknown session occurred as a result of profiling and the DDP API response contains the unknown session condition, the node follows the configured unknown session action.

## Example

Read the [Example LexisNexis DDP journey](lexis-ddp.html#lexis-ddp-example).

## Availability

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

## Inputs

This node reads the following from the shared state:

* `ddp.query_api_response`: the full API response from the LexisNexis DDP Query node.

## Dependencies

The node requires a LexisNexis DDP Query node in the journey to provide the query API response.

## Configuration

| Property                     | Usage                                                                                                                                                                       |
| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Unknown Session Action       | If an unknown session is encountered at runtime, this property defines the behavior. Unknown sessions occur for a variety of reasons where the device profiling has failed. |
| Store DDP Query API Response | If enabled, the DDP query API response remains in the shared state. If disabled, the node removes the `ddp.query_api_response` value from the shared state.                 |

## Outputs

This node writes the following to the shared state:

* `ddp.query_api_response`: the full query API response, if you enabled Store DDP Query API Response. Otherwise, the node removes this value from the shared state.

* `ddp.query_reason_codes`: the reason codes from the DDP policy, for all outcomes.

* `ddp.request_id`: the request ID associated with the DDP query API. The [LexisNexis DDP Update Review node](lexis-ddp-update-review.html) uses this value to add truth data to a risk event, and other LexisNexis product APIs can use it as an identifier.

* `ddp.failure_reason`: text associated with the error condition, if an error outcome is triggered.

## Callbacks

This node doesn't send any callbacks.

## Outcomes

* `Pass`

  The `review_status` attribute in the DDP query API response is `pass`.

* `Challenge`

  The `review_status` API response attribute is `challenge`.

* `Review`

  The `review_status` API response attribute is `review`.

* `Reject`

  The `review_status` API response attribute is `reject`.

* `Error`

  There is an integration error. Check the debug log files for any integration issues. If the configuration looks accurate, open a support case with LexisNexis.

## Errors

This node doesn't log any error or warning messages of its own.