> ## 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.

# Frequently asked questions

> Answers to common questions about underwriting applications, stakeholders, submissions, and updates.

<AccordionGroup>
  <Accordion title="Can I create and submit an application in a single request?">
    No. Creating an application and submitting it for underwriting are two separate API operations.

    If all required data and stakeholders are available upfront, you may create the application using [`createUnderwritingApplication`](/underwriting/reference/graphql/operations/create-underwriting-application) and then immediately submit it in a subsequent request using [`submitUnderwritingApplication`](/underwriting/reference/graphql/operations/submit-underwriting-application) with the returned application ID.
  </Accordion>

  <Accordion title="Can stakeholders be added after application creation?">
    Yes. Stakeholders can be added, updated, or removed after creation using specialized stakeholder inputs via the [`updateUnderwritingApplication`](/underwriting/reference/graphql/operations/update-underwriting-application) mutation, as long as the application has not reached a final decision.

    See [managing stakeholders](/underwriting/guides/managing-stakeholders) for details.
  </Accordion>

  <Accordion title="Can an application be updated after submission?">
    Most core application fields become read-only after submission. Updates may only be permitted if explicitly allowed during underwriting review.

    However, you can still respond to [information requests](/underwriting/guides/information-requests) and provide additional documentation when requested by underwriters.
  </Accordion>

  <Accordion title="What are the final application outcomes?">
    The only final outcomes are:

    * **Approved** – The application meets underwriting requirements
    * **Declined** – The application does not meet underwriting requirements
    * **Withdrawn** – The application was withdrawn before a final decision

    All other statuses (Created, Submitted, Processing, Pending) represent intermediate stages in the underwriting process.
  </Accordion>

  <Accordion title="Should I poll the API to check application status?">
    No. [Webhooks](/underwriting/guides/webhooks) are the recommended mechanism for tracking application progress and underwriting actions.

    Polling should be avoided except for recovery or reconciliation scenarios. Webhooks provide:

    * Real-time notifications
    * Lower API load
    * More efficient integrations
    * Immediate reaction to events
  </Accordion>

  <Accordion title="Are webhook events delivered exactly once?">
    No. Webhooks are delivered **at least once**. Your system should be designed to handle duplicate events idempotently.

    Use the event ID included in each webhook payload to track which events you've already processed and prevent duplicate processing.

    See [webhooks](/underwriting/guides/webhooks) for implementation best practices.
  </Accordion>

  <Accordion title="How long does underwriting typically take?">
    Underwriting timelines vary based on several factors:

    * **Automated approval** – Applications that pass all automated checks may be approved within minutes
    * **Manual review** – Applications requiring manual review typically take 1-3 business days
    * **Information requests** – Timeline depends on how quickly requested information is provided

    Use [webhooks](/underwriting/guides/webhooks) to receive notifications when decisions are made rather than expecting specific timeframes.
  </Accordion>

  <Accordion title="Can I test underwriting in a sandbox environment?">
    Yes. Tesouro provides sandbox environments for testing underwriting integrations.

    * Use test data to create and submit applications
    * Simulate different verification outcomes
    * Test webhook delivery and processing
    * Practice handling information requests

    Contact your Tesouro representative for sandbox access and test data guidelines.

    <Warning>
      Always test your integration in sandbox before moving to production. This helps identify issues
      with validation, webhook handling, and error scenarios without affecting real underwriting data.
    </Warning>
  </Accordion>

  <Accordion title="What happens if I submit incomplete data?">
    If you submit an application with incomplete data:

    1. The [`submitUnderwritingApplication`](/underwriting/reference/graphql/operations/submit-underwriting-application) mutation will validate required fields
    2. Validation errors will be returned in the response
    3. The application status will be SUBMISSION\_INVALID
    4. You can update the application with missing data using [`updateUnderwritingApplication`](/underwriting/reference/graphql/operations/update-underwriting-application)
    5. Resubmit the application after corrections

    The validation process ensures all required information is present before underwriting begins.
  </Accordion>

  <Accordion title="How do I handle multiple stakeholders with the same role?">
    You can have multiple stakeholders with the same role (e.g., two owners each with 50% ownership).

    When adding stakeholders:

    * Create separate stakeholder entries for each individual
    * Assign appropriate roles to each stakeholder
    * Ensure ownership percentages sum correctly for owners
    * Include all required information for each stakeholder

    See [managing stakeholders](/underwriting/guides/managing-stakeholders) for examples.
  </Accordion>

  <Accordion title="What if bank account verification fails?">
    If bank account verification fails:

    1. Review the [decision component](/underwriting/guides/decision-components) results to understand why
    2. Check for common issues:
       * Incorrect routing or account number
       * Account is closed or frozen
       * Account ownership doesn't match business name
    3. Update the application with corrected bank account information if needed
    4. The underwriter may create an [information request](/underwriting/guides/information-requests) asking for additional documentation
  </Accordion>

  <Accordion title="Can I withdraw an application after submission?">
    Yes. Applications can be withdrawn before a final decision is reached.

    Use the [`updateUnderwritingApplication`](/underwriting/reference/graphql/operations/update-underwriting-application) mutation with the status field set to WITHDRAWN. This is useful when:

    * The merchant no longer wants to proceed
    * Significant changes make the current application obsolete
    * You need to restart the process with corrected information
  </Accordion>
</AccordionGroup>