Skip to main content
When a user authenticates through Truv Bridge, the system creates a Link, a persistent connection to their payroll provider or bank. Each Link has a unique access_token that enables all subsequent data retrieval and modifications. Tasks are the individual actions performed through Links (e.g., fetching income data, switching direct deposits). Each task progresses through a defined status lifecycle.

Task status flow

Every task authenticates through the Link first, then follows one of two paths depending on its type. A task may skip mfa when the provider doesn’t require multi-factor authentication.

Standard tasks

A standard task collects data from the connected account:

DDS tasks

A Direct Deposit Switch task replaces parse and full_parse with switch_deposit:

Status definitions


Error states

Tasks may enter an error state at any point in the lifecycle:
Subscribe to task-status-updated webhooks to receive error states in real time. See Task Webhook Events for the full list of task events.

Data processing

See Data Processing for stage timing, median durations, data availability at each stage, and typical processing times.

Relationship to Orders

Orders are the top-level containers for verification requests. When a user completes an Order:
  1. The user authenticates through Bridge, creating a Link
  2. A Task is created on that Link to retrieve the requested data
  3. The Task progresses through the status lifecycle
  4. On completion, data is available via the API and the order status updates
A single Order can have multiple connections (e.g., a borrower connecting two employers), each with their own Link and Tasks.

Monitor tasks

Dashboard

View task details in the Dashboard under Activity > Tasks. Filter by status, date, and provider.

API

Retrieve task status programmatically:

Webhooks

Subscribe to task events for real-time monitoring:
  • task-status-updated with status: done: task finished successfully
  • task-status-updated with an error status: task encountered an error