Connection Lifecycle

​

Overview

Transcrypts utilizes Tasks on connected accounts to gather user information. Tasks leverage Link connections with providers to execute actions such as data retrieval and modification. When interfacing with providers, Transcrypts processes user data through multiple stages. Key topics covered:

• Task status lifecycle with sequencing and error descriptions
• Data processing stages including approximate timeframes and durations

​

Task Status Lifecycle

When users connect payroll accounts through Transcrypts Bridge, a Link is established. This provider connection receives a unique identifier — the link ID or access_token — which enables data collection and refresh initiation. The access_token works with Links to retrieve reports and trigger data refreshes. Each action creates a Task, which Transcrypts then processes through the payroll provider.

​

Task Statuses

Tasks progress sequentially through these statuses: new -> login -> mfa -> parse -> full_parse -> done

​

Task Errors

Unsuccessful Task actions include:

​

Data Processing Stages

Transcrypts processes data through various stages. Larger documents and specific formats may require extended median times. Webhooks or status update API endpoints track Tasks.

​

Processing Stages

​

Median Stage Times

Processing durations are approximations and subject to variation:

• Login: 5 to 15 seconds
• Parse: 30 to 60 seconds (base parsing)
• Full parse: 1 to 5 minutes