> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tesouro.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Component catalog

> Reference of common decision components including identity verification, TIN match, and bank account checks.

While decision components vary by underwriting configuration, common components include:

### Identity verification

Verifies stakeholder identities against government databases and credit bureaus.

* Validates name, date of birth, SSN/TIN
* Checks for identity fraud indicators
* Produces status outcomes: VERIFIED, FAILED, REVIEW\_REQUIRED

### TIN match

Validates business Tax Identification Number (EIN) with IRS records.

* Confirms business legal name matches IRS records
* Verifies TIN is valid and active
* Produces status outcomes: MATCH, MISMATCH, REVIEW\_REQUIRED

### Bank account verification

Verifies bank account ownership and validity.

* Confirms account is active and accessible
* Validates routing and account numbers
* May use micro-deposits or third-party verification
* Produces status outcomes: VERIFIED, FAILED, PENDING

### Credit assessment

Evaluates business and stakeholder creditworthiness.

* Retrieves credit scores and reports
* Assesses credit history
* Produces assessment outcomes: credit score, risk rating

<Callout icon="clapperboard-play" color="#6938EF" type="scenario">
  **Scenario**

  Ben's keyboard business application completes automated processing. The
  identity verification and TIN match components both return VERIFIED status.
  However, the bank account verification component returns REVIEW\_REQUIRED
  because the account was recently opened. The application moves to Pending
  status, and an underwriter reviews the bank account documentation.
</Callout>

## Decision component schema

The decision component schema defines the structure and expected fields for each component type. Query the schema using the `schema` field on [`UnderwritingApplication`](/underwriting/reference/graphql/types/underwritingapplication) to understand:

* Available decision components
* Expected fields for each component
* Field data types and validation rules

### Query decision components schema

The schema helps you understand what decision components will run and what data they evaluate.

<Note>
  The decision components schema is useful for building integrations that display underwriting
  status and results to end users in a structured way.
</Note>

<RequestExample>
  ```graphql Operation lines expandable theme={null}
  query UnderwritingApplication($input: UnderwritingApplicationInput!) {
    underwritingApplications(input: $input) {
      items {
        id
        schema {
          id
          version
          underwritingDecisionComponentSchemas {
            id
            label
            underwritingDecisionComponentItemSchemas {
              id
              label
              underwritingDecisionComponentFieldSchemas {
                id
                label
                helperText
                isRequired
                isReadOnly
                fieldType
              }
            }
          }
        }
      }
    }
  }
  ```

  ```json Variables lines theme={null}
  {
    "input": {
      "where": {
        "id": {
          "eq": "3fa85f64-5717-4562-b3fc-2c963f66afa6"
        }
      },
      "paging": {
        "skip": 0,
        "take": 10
      }
    }
  }
  ```
</RequestExample>