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
ScenarioBen’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.
Decision component schema
The decision component schema defines the structure and expected fields for each component type. Query the schema using theschema field on 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.The decision components schema is useful for building integrations that
display underwriting status and results to end users in a structured way.