---
title: LexisNexis DDP Update Review node
description: The LexisNexis DDP Update Review node sends retrospective truth data from an authentication event back to the LexisNexis Dynamic Decision Platform to improve policy tuning and fraud detection accuracy.
component: auth-node-ref
version: latest
page_id: auth-node-ref:cloud:lexis-ddp-update-review
canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/cloud/lexis-ddp-update-review.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", "Step-up Authentication"]
page_aliases: ["threat-metrix-update-review.adoc"]
section_ids:
  example: Example
  availability: Availability
  inputs: Inputs
  dependencies: Dependencies
  configuration: Configuration
  outputs: Outputs
  callbacks: Callbacks
  outcomes: Outcomes
  errors: Errors
---

# LexisNexis DDP Update Review node

The LexisNexis DDP Update Review node associates retrospective truth data with a DDP API event using the request ID from the DDP query API response. Truth data is beneficial for tuning policies and overall fraud detection. The typical authentication journey performs a DDP query and, if step-up authentication is involved, integrates this node to provide additional details on the event.

## 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.request_id`: the request ID associated with the DDP query API, which the node uses to add truth data to the risk event.

## Dependencies

The node requires a LexisNexis DDP Query node in the journey to provide the `ddp.request_id` value.

To use this node, you should have already set up integration with the LexisNexis DDP portal.

## Configuration

| Property       | Usage                                                                                                                                                                                                                                                                                                                         |
| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Org ID         | The unique ID associated with DDP for your organization.                                                                                                                                                                                                                                                                      |
| API Key        | The unique API key generated by the DDP portal and associated with the Org ID.                                                                                                                                                                                                                                                |
| Base URL       | The domain URL for the DDP region where API requests are sent. The default is the global region.                                                                                                                                                                                                                              |
| Event Tag      | Represents the event disposition and outcome of the DDP query API event. Generally, the `challenge_init` tag is configured before sending a step-up authentication request, in case the transaction is abandoned. Following a step-up authentication, either the `challenge_pass` or `challenge_fail` tag is sent to the DDP. |
| Step-Up Method | The authentication challenge method used within the authentication journey to report retrospective truth data for the overall transaction.                                                                                                                                                                                    |
| Notes          | An optional parameter that allows you to append any textual detail, such as the reason for updating the review status.                                                                                                                                                                                                        |

## Outputs

This node writes the following to the shared state:

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

## Callbacks

This node doesn't send any callbacks.

## Outcomes

* `Next`

  The DDP update API completed successfully.

* `Error`

  The API resulted in a non-success, or 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.