Skip to the operations

Banking

Truv in a decision flow.

5 Truv operations a decision flow can call directly, with the credentials your own contract issued. The response is data the rest of the flow reads, branches on, and keeps in the trace.

Category
Banking
Type
Integration
Authentication
API key headers
Test environment
Production host only

Who they are

Income and employment verification from payroll systems.

Truv connects to payroll and HR providers, with the applicant's consent, and returns employment status, income and pay history from the source rather than from an uploaded document. The same connections also support direct deposit switching.

What a flow can call

5 operations, each one a step you can place on the canvas.

  1. POST/v1/users/$data.truv_user_id/tokens/

    Start a payroll connection (Bridge token)

    First step. Mints the token that initialises TruvBridge for one user, who then picks their employer or payroll provider and logs in there.

  2. POST/v1/link-access-tokens/

    Exchange the public token

    Second step. Bridge hands the front end a public_token; this trades it for the access_token and, more importantly, the link_id that every report call below is keyed by.

  3. GET/v1/links/$data.truv_link_id/income-employment-reports

    Get income and employment (VOIE)

    The verification of income and employment for a completed link — pay rate, frequency and employment status straight from the payroll record.

  4. GET/v1/links/$data.truv_link_id/employment-reports

    Get employment only (VOE)

    Employer, title, start date and status without the income detail.

  5. GET/v1/links/$data.truv_link_id/statements

    Get pay statements

    Individual pay statements with gross, net and the earnings and deductions breakdown.

Where it sits in the decision

Banking calls have a natural place in a flow.

Bank data answers the question a stated income cannot: what actually arrives, how regularly, and what leaves again. It is usually pulled once per application and then read by several nodes — affordability, income verification, any rule about balance volatility — so it is worth fetching early and deriving from, rather than calling repeatedly.

Whatever Truv returns is part of the run, so it is part of the record. When someone asks months later why an applicant was declined, the answer cites what came back at the time rather than re-fetching from a service whose answer has since changed.

  • 01Add Truv as a connection authenticating with API key headers.
  • 02Truv has one host for both environments, so guard test runs with your own credentials and limits.
  • 03Place a Connection node and pick an operation — “Start a payroll connection (Bridge token)” is usually the first one a flow needs.
  • 04Map the response into the fields your rules read, then test the whole path before it carries live traffic.

Common questions

Using Truv in a flow.

How do I connect Truv to a decision flow?

Add Truv as a connection in your workspace authenticating with API key headers, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use Truv in a decision without ever seeing the secret.

Can I test Truv without touching production?

Truv exposes one host for both environments, so there is no separate sandbox to point at. Test runs still execute in Sandbox and are recorded separately in decision history, but the call goes to the same place as production — so guard it with your own test credentials, rate limits, or data.

What can a flow call on Truv?

5 operations, including “Start a payroll connection (Bridge token)”, “Exchange the public token”, “Get income and employment (VOIE)”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Start a payroll connection (Bridge token)”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.

Where in a decision should Truv be called?

Bank data answers the question a stated income cannot: what actually arrives, how regularly, and what leaves again. It is usually pulled once per application and then read by several nodes — affordability, income verification, any rule about balance volatility — so it is worth fetching early and deriving from, rather than calling repeatedly.

Also in Banking

Ready when you are

Wire Truv into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs