Skip to main content

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.

​
Overview

Underwriting applications is in Beta and not ready for production integration.
Underwriting applications on the Tesouro platform allow you to submit business, stakeholder, and financial information for underwriting review and decisioning. Applications are created and managed using GraphQL mutations and progress through a defined lifecycle as they move from initial creation to final decision. The underwriting flow is designed to be flexible. You may create an application with all required data in a single request and then submit it immediately in a subsequent request, or progressively build and update an application over time before submitting it for review. This enables a variety of integration patterns, including near-synchronous application submission and asynchronous data collection.
Scenario A — Business checking account onboarding at a regional bankA developer at Heartland Commerce Bank is integrating Tesouro’s underwriting API into their small business checking account opening flow. When a business applies, the integration creates an underwriting application with business entity details and beneficial owner information, then submits it for review. Tesouro runs KYB and KYC decisioning and returns an outcome that Heartland Commerce Bank uses to automatically approve or decline the account opening request.Scenario B — Small business loan origination at a fintech lenderA developer at Bridgepoint Capital is building a loan origination system for small business term loans. Their integration uses Tesouro’s underwriting API to progressively collect business financials, tax documents, and stakeholder data as applicants move through a multi-step application form. Once all required data is present, the integration submits the application and uses webhooks to receive the final credit decision.Scenario C — Revolving lines of credit at a credit unionA developer at Clearwater Credit Union is adding a line of credit product to their digital banking platform. They use Tesouro’s underwriting API as part of their existing member onboarding flow — creating applications on behalf of members, fulfilling any information requests the underwriting team surfaces, and receiving Approved or Declined outcomes to determine credit limit offers.
At a high level, the underwriting process consists of:
  1. Creating an underwriting application with the required business, stakeholder, and financial details
  2. Updating the application as additional information becomes available
  3. Submitting the application for underwriting review once all required data is provided
  4. Participating in underwriter-driven actions, such as receiving and fulfilling information requests and supporting manual review of decision components
  5. Receiving an underwriting decision
After submission, applications may undergo automated and manual review. Underwriters can request additional information, run decision components on demand, and progress the application through its lifecycle until a final outcome is reached. This documentation walks through each stage of the underwriting application lifecycle, including the required inputs, available mutations, expected responses, and common integration patterns.

​
End-to-end flow

This section outlines the typical end-to-end flow for underwriting an application on the Tesouro platform. While the platform supports flexible submission models, most integrations follow the same general sequence from application creation through final decision.

​
High-level sequence

At a high level, the underwriting flow consists of the following steps:
  1. Create the application Create an underwriting application using the createUnderwritingApplication mutation.
    • Stakeholders may be included at creation or omitted initially
    • The application enters the Created state
  2. Add or update application details Use updateUnderwritingApplication to add or modify application data such as:
    • Business information
    • Bank accounts
    • Financial details
    • Supporting documentation via attachments
  3. Submit the application Submit the application using submitUnderwritingApplication once all required data and stakeholders are present.
  4. Automated processing The application enters the Processing state, where:
    • Automated verification checks run
    • Decision components are executed by the system
  5. Manual review (if required) If discrepancies are detected, the application transitions to Pending for underwriter evaluation.
  6. Final decision The application reaches Decisioned with one of the following outcomes:
    • Approved
    • Declined
    • Withdrawn
Scenario A (continued) — Single-step submissionThe Heartland Commerce Bank integration submits a fully completed application in a single sequence — business entity data and beneficial owners are included at creation, and the application is submitted immediately after. The system runs automated KYB and KYC checks, all pass, and Heartland Commerce Bank receives an Approved decision within seconds via webhook.Scenario B (continued) — Progressive submissionThe Bridgepoint Capital integration creates an application early in the funnel with just the business name and EIN, then progressively adds financial statements, tax documents, and stakeholder data as the applicant completes each step of their form. The application is only submitted once all required fields are present, triggering the full underwriting review.

​
Flexible submission models

Tesouro supports multiple submission strategies depending on your integration needs:
  • Single-step submission Create and submit a fully completed application in close succession when all data is available upfront.
  • Progressive submission Create an application early and progressively update it as data becomes available, submitting only when all requirements are met.
Both models follow the same lifecycle and result in identical underwriting outcomes.

​
Monitoring progress

Throughout the end-to-end flow, application status changes and underwriting actions can be monitored using webhooks. This allows your system to react to events such as:
  • Application submission
  • Information requests
  • Status transitions
  • Final decisions
Use webhooks to monitor application progress asynchronously rather than polling the API. Webhooks provide real-time notifications and reduce unnecessary API calls.

​
Next steps