Launch Checklist

Schedule UX review

  • To help with your implementation and get tips on the best ways to implement BridgeBridge - The client-side component that your users will interact with in order to link their payroll accounts to Truv and allow you to access their accounts via the Truv. and increase conversion, email [email protected] to schedule a UX review session.

Test in development

  • To test with live credentials you'll need a "Development" Access keyAccess key - The unique key passed into the X-Access-Secret header of every API request to authorize it.. Head to the API Keys page and click the "Request keys". Once approved you will have a Development Access key available in your Dashboard. Use this Access keyAccess key - The unique key passed into the X-Access-Secret header of every API request to authorize it. instead of your Sandbox key in your application to test with live credentials for up to 50 connections.

Update branding

  • Before going live you want to ensure BridgeBridge - The client-side component that your users will interact with in order to link their payroll accounts to Truv and allow you to access their accounts via the Truv. matches your application's branding. Visit Branding to update colors, your application logo and LinkLink - A connection to a payroll provider used to retrieve payroll data. expiration limit.
  • Fill out company profile in Settings > Company.
  • If you are looking for a full white labeled solution that allows to hide Truv logo, "Get help" button and more, visit Settings > White Labeling to remove Truv branding and more.

Setup production env

  • Ensure the product_type you're specifying in the /v1/bridge-tokens endpoint matches the endpoints you're calling.
  • To request Production keys, head to the API Keys page and click the "Request keys".
  • Configure Truv Bridge and your backend to use Production environment.
  • Ensure you're using production keys that you can find under API Keys.
  • If migrating from Sandbox, make sure to remove use of Sandbox credentials and update unit tests that you run to only use Sandbox environment.
  • Invite your team members in Dashboard

Setup Bridge

  • Update client_name when using bridge-tokens/ end point.
  • Assign unique identifier for tracking_info to make reports in Dashboard more accurate.
  • Review UX best practices for the product of your choice.
  • Setup deep linking if you have data about the user beforehand and want to skip unnecessary screens in Bridge by providing certain fields when requesting a bridge_tokenbridge_token - A short-lived token provided by the Truv to authorize the use of Bridge. This token has a 6 hour expiration..
  • Handle onEvent to provider a better UX in case user closes BridgeBridge - The client-side component that your users will interact with in order to link their payroll accounts to Truv and allow you to access their accounts via the Truv. or gets an error.
  • Handle onEvent events to track conversion metrics.

Configure webhooks

  • To subscribe to Truv webhooks navigate to the Webhooks section of the dashboard and enter the URL endpoint where you would like to receive updates.
  • Confirm that that your application meets our HTTP request timeouts: 1 second for a connection timeout and 1 second for a read timeout (wait for the response after connection). The receiving API should respect those timeouts, otherwise the webhook events will not be received successfully.

Store identifiers

  • Truv's identifiers let you associate API and Provider events with your requests, and will help our support team resolve your support issues faster. Access keyAccess key - The unique key passed into the X-Access-Secret header of every API request to authorize it.s are the core identifiers that map your end-users to LinkLink - A connection to a payroll provider used to retrieve payroll data.s.
  • Store access_tokens securely and associate them with users of your application.

Delays in data

  • For TaskTask - A process where a Link is used to pull/write data from/to a payroll provider.s, ensure that you are waiting until the status = done to attempt to pull all available data, as many fields are not available when status = full_parse. See more in Data processing.

Update mode

Delete data

  • If your contract allows to delete data, use DELETE /link/{access_token}/ to remove a Link and all associated data.

Post launch

  • Reach out to [email protected] to schedule a session with your dedicated implementation manager.

Did this page help you?