---
title: Terms and Conditions Decision node
description: Configure the Terms and Conditions Decision node to verify that a user has accepted the active terms and conditions before proceeding in a journey.
component: auth-node-ref
version: 8.1
page_id: auth-node-ref::terms-and-conditions-decision
canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/terms-and-conditions-decision.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-08-18T00:00:00Z
keywords: ["Nodes & Trees", "Journeys", "Authentication", "Terms & Conditions"]
page_aliases: ["auth-node-terms-and-conditions-decision.adoc"]
section_ids:
  availability: Availability
  callbacks: Callbacks
  outcomes: Outcomes
  configuration: Configuration
---

# Terms and Conditions Decision node

Verifies the user has accepted the active set of terms and conditions.

Use this node to verify the user has accepted terms and conditions before proceeding, for example, during login or progressive profile data collection.

You can use this node with the [Accept Terms and Conditions node](accept-terms-and-conditions.html).

## Availability

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

1 This functionality requires that you configure AM as part of a [Ping Identity Platform deployment](https://docs.pingidentity.com/platform/8.1/sample-setup/).

## Callbacks

This node doesn't send any callbacks.

## Outcomes

* `True`

* `False`

## Configuration

| Property           | Usage                                                                                           |
| ------------------ | ----------------------------------------------------------------------------------------------- |
| Identity Attribute | The attribute used to identify the managed object in the underlying identity service (PingIDM). |