---
title: OOTB - Financial Services - Account Settings Subflow
description: Learn about the OOTB - Financial Services - Account Settings Subflow flow, including its purpose, structure, inputs, outputs, and variables.
component: pingone-solutions
page_id: pingone-solutions:financial-services:flow-reference/financial-services-account-settings-subflow
canonical_url: https://docs.pingidentity.com/pingone-solutions/financial-services/flow-reference/financial-services-account-settings-subflow.html
revdate: July 1, 2025
section_ids:
  purpose: Purpose
  structure: Structure
  input-schema: Input schema
  output-schema: Output schema
  variables-and-parameters: Variables and parameters
---

# OOTB - Financial Services - Account Settings Subflow

The **OOTB - Financial Services - Account Settings Subflow** lets users update account settings.

## Purpose

The **OOTB - Financial Services - Account Settings Subflow** presents users with a form that lets them change their account settings including payment limits and whether online transactions are enabled. The user's updated settings are saved by PingOne.

## Structure

This flow is divided into sections using teleport nodes:

* **OOTB - Financial Services - Account Settings Subflow**

  A function node sets flow variables, and a PingOne node verifies that the user exists. An HTML node then presents the user with account management options.

  If the user cancels, the flow progresses to the **Return Success** section.

  If the user submits the form, a function node validates the responses, and a PingOne node verifies that the user exists. The flow then branches based on the user's selection:

  * If the user enabled online transactions, a PingOne node saves the user attributes, and a success message displays. The flow then progresses to the **Return Success** section.

  * If the user disabled online transactions, a PingOne node saves the user attributes, and a warning message displays indicating that online transactions are disabled. The flow then progresses to the **Return Success** section.

* **Return Success**

  Sends a success JSON response, indicating that the flow completed successfully.

* **Return Error**

  Uses a function node to enrich the error details, then sends an error JSON response indicating that the flow completed unsuccessfully.

## Input schema

This flow has the following inputs:

| Input name    | Required | Description                                            |
| ------------- | -------- | ------------------------------------------------------ |
| `p1UserId`    | Yes      | The current user's PingOne user ID.                    |
| `companyLogo` | No       | The company logo to display in user-facing HTML pages. |
| `flowMethod`  | No       | The flow method.                                       |

## Output schema

This flow has the following outputs:

| Output Name     | Description                                   |
| --------------- | --------------------------------------------- |
| `subflowResult` | The result status of the flow.                |
| `errorMessage`  | The error message to pass to the parent flow. |
| `errorDetails`  | The details of the error that occurred.       |

## Variables and parameters

This flow uses the following variable or parameter values:

| Parameter name         | Description                                                                                                 |
| ---------------------- | ----------------------------------------------------------------------------------------------------------- |
| `p1UserId`             | The current user's PingOne user ID.                                                                         |
| `minPaymentLimit`      | The minimum payment size for the user.                                                                      |
| `maxPaymentLimit`      | The maximum payment size for the user.                                                                      |
| `currency`             | The currency symbol for the user's locale.                                                                  |
| `userPaymentOnline`    | Indicates whether online transactions are enabled or disabled.                                              |
| `userPaymentThreshold` | A threshold above which payments and transfers require approval.                                            |
| `userPaymentLimit`     | The maximum size of online payments or transfers. Online payments or transfers above this limit are denied. |