When to Use Bridge Widget
| Use Case | Recommended Method |
|---|---|
| Deposit Switch | Bridge Widget |
| Paycheck Linked Lending | Bridge Widget |
| Income & Employment | Embedded Orders |
| Assets | Embedded Orders |
| Employment | Embedded Orders |
Token flow
The Widget-only flow uses a three-token exchange to securely connect users:| Token | Created By | Lifetime | Purpose |
|---|---|---|---|
bridge_token | Your server (via API) | 6 hours | Initialize Truv Bridge on the client |
public_token | Truv Bridge (on success) | Short-lived | Temporary token for exchange |
access_token | Token exchange (via API) | Persistent | Configure DDS/PLL and retrieve data |
Implementation
Step 1: Create a user [Server-side]
Create a user to associate with this connection.id from the response to use in the next step.
Step 2: Create a bridge token [Server-side]
Create a bridge token with the user ID and your product configuration. Pass theaccount details for the destination bank account.
- Deposit Switch
- Paycheck Linked Lending
Step 3: Initialize Bridge Widget [Client-side]
Pass thebridge_token to Truv Bridge. When the user connects successfully, Bridge returns a public_token via the onSuccess callback.
Step 4: Exchange token and retrieve data [Server-side]
Exchange thepublic_token for a persistent access_token:
access_token securely. Use it to fetch data and manage the connection.
Webhooks
Listen for these server-side webhook events to track connection status:task-status-updatedwithstatus: done— task completed successfullytask-status-updatedwith error statuses — connection failed (see Task lifecycle)
Best practices
- Always wait for
task-status-updatedwebhook withstatus: donebefore treating a connection as complete - Handle errors with user-friendly messaging
- Store
link_idandaccess_tokenfor future reference
Next steps
Direct Deposit Switch
Direct Deposit Switch integration for Retail Banking
Paycheck-Linked Loans
Complete Paycheck Linked Lending setup guide
Bridge Events
Client-side event types and error codes
Best Practices
Widget-only implementation guidelines