Compliance tasks

Compliance tasks represent actionable steps that a connected account must complete to become or remain operational.

They provide structured guidance for fulfilling regulatory and contractual obligations, such as accepting agreements or completing declarations.

Why tasks exist

Requirements indicate what is missing or incomplete.

Tasks provide the context needed to resolve those requirements.

For example:

A requirement may indicate that an agreement must be accepted
A task provides the agreement bundle, documents, and instructions needed to collect that acceptance

Tasks are derived from requirements.

Not all requirements produce tasks. Tasks are used when additional context or structured interaction is required.

Tasks are commonly used to:

Fetch account status

Retrieve the current compliance status and list of tasks for the account.

Render task content

Display documents, checkboxes, or declarations based on the task payload.

Collect user input

Capture acceptance from an authorized person.

Submit attestation

Send the completed attestation to the API.

Verify completion

Re-fetch account status to confirm the task is resolved.

Tasks may be marked as blocking.

Blocking tasks must be completed before the account can operate
Non-blocking tasks can be completed later without immediately restricting the account

{
  "blocking": true,
  "status": "action_required"
}

Tasks can appear:

Your platform should continuously monitor and process tasks as part of normal account operations.