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

# Launch Checklist

> Pre-production steps for any Truv integration

Complete these steps before going live. Not all steps are required for minimal operation, but following them makes your integration more robust, secure, and maintainable.

## Production setup

<Steps>
  <Step title="Schedule a UX review">
    Email [support@truv.com](mailto:support@truv.com) to schedule a UX review session. Get tips on implementing Truv Bridge to increase conversion rates.
  </Step>

  <Step title="Test with production test providers">
    Use the [production test providers](/developers/testing/test-credentials#testing-in-production) (Truv Payroll Provider, Truv Bank OAuth, Truv Bank non-OAuth) with sandbox credentials to validate your integration against real provider behavior. This confirms your webhook handling, error flows, and data ingestion work correctly.
  </Step>

  <Step title="Run User Acceptance Testing (UAT)">
    Walk through the full end-to-end flow as an end user: complete verification, confirm data appears in your system, test error and retry paths, and verify notifications deliver correctly.
  </Step>

  <Step title="Update branding">
    Ensure Truv Bridge matches your application's branding. Visit [Branding](https://dashboard.truv.com/app/customization/account/branding) to update colors, logo, and link expiration. Fill out your company profile in **Settings** → **Company**.
  </Step>

  <Step title="Set up production environment">
    Request Production keys via the [API Keys](https://dashboard.truv.com/app/development/keys) page. Configure your backend to use Production credentials. Remove Sandbox credentials from production code.
  </Step>

  <Step title="Invite team members">
    Add teammates to the [Dashboard](https://dashboard.truv.com/app/settings/team) for shared access and monitoring.
  </Step>
</Steps>

***

## Bridge setup

<Steps>
  <Step title="Assign tracking identifiers">
    Pass a unique value for `tracking_info` when creating bridge tokens. This makes connections easy to track in the Dashboard and in your own systems.
  </Step>

  <Step title="Set up deeplinking">
    If you collect the user's employer name upfront, resolve it to a `company_mapping_id` and pass it when creating the order or bridge token. This skips the search screen and improves conversion. See [Deeplinking](/developers/integration/embedded-orders/deeplinking).
  </Step>

  <Step title="Handle onEvent callbacks">
    Implement `onEvent` handling to provide better UX when the user closes Bridge or encounters an error. Use events to track conversion metrics. See [Bridge Events](/developers/sdks/bridge-events).
  </Step>
</Steps>

***

## Configure webhooks

<Steps>
  <Step title="Subscribe to webhooks">
    Add your endpoint URL in the Dashboard under **Development** → **Webhooks**. Each environment needs a separate URL.
  </Step>

  <Step title="Verify signatures">
    Validate the `X-WEBHOOK-SIGN` header on every incoming webhook. See [Security](/api-reference/security) for code examples in 5 languages.
  </Step>

  <Step title="Respect timeouts">
    Your endpoint must respond within **1 second** connection timeout and **1 second** read timeout. If you need to do heavy processing, acknowledge the webhook immediately and process asynchronously.
  </Step>
</Steps>

***

## Handle errors

<Steps>
  <Step title="Implement retry logic">
    Add retry logic for API calls to handle intermittent outages at supported institutions. Use exponential backoff.
  </Step>

  <Step title="Handle partial completions">
    Users may not complete all connections. Process available data rather than treating partial completions as failures.
  </Step>

  <Step title="Test data refresh">
    Confirm that refresh orders return updated data when the session is active. Verify your system falls back to a new verification link when refresh returns `login_error` or `mfa_error`. See [Data Refresh](/developers/integration/embedded-orders/data-refresh).
  </Step>

  <Step title="Monitor error rates">
    Track error rates by type (login\_error, mfa\_error, unavailable) to spot provider-specific issues early.
  </Step>
</Steps>

***

## Industry-specific checklists

<CardGroup cols={2}>
  <Card title="Test Credentials" icon="key" href="/developers/testing/test-credentials">
    Sandbox credentials and test scenarios
  </Card>

  <Card title="Test Documents" icon="flask" href="/developers/testing/test-documents">
    Sample documents for document processing testing
  </Card>
</CardGroup>