Skip to main content
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

1

Schedule a UX review

Email support@truv.com to schedule a UX review session. Get tips on implementing Truv Bridge to increase conversion rates.
2

Test with production test providers

Use the production test providers (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.
3

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

Update branding

Ensure Truv Bridge matches your application’s branding. Visit Branding to update colors, logo, and link expiration. Fill out your company profile in Settings → Company.
5

Set up production environment

Request Production keys via the API Keys page. Configure your backend to use Production credentials. Remove Sandbox credentials from production code.
6

Invite team members

Add teammates to the Dashboard for shared access and monitoring.

​
Bridge setup

1

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

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

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.

​
Configure webhooks

1

Subscribe to webhooks

Add your endpoint URL in the Dashboard under Development → Webhooks. Each environment needs a separate URL.
2

Verify signatures

Validate the X-WEBHOOK-SIGN header on every incoming webhook. See Security for code examples in 5 languages.
3

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.

​
Handle errors

1

Implement retry logic

Add retry logic for API calls to handle intermittent outages at supported institutions. Use exponential backoff.
2

Handle partial completions

Users may not complete all connections. Process available data rather than treating partial completions as failures.
3

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

Monitor error rates

Track error rates by type (login_error, mfa_error, unavailable) to spot provider-specific issues early.

​
Industry-specific checklists

Test Credentials

Sandbox credentials and test scenarios

Test Documents

Sample documents for document processing testing