Onboarding and review lifecycle

Follow the onboarding and review lifecycle from submitted data through approval, information requests, enhanced diligence, or rejection.

See API availability before using this lifecycle as a production API contract.

Review lifecycle

Roots creates an identity record from the latest information held about a client, end customer, associated person, or counterparty. A review is a point-in-time assessment of that identity.

The lifecycle can include client KYB, end-customer KYB, end-customer KYC, associated-person screening, counterparty screening, post-funding review, and periodic refresh.

stateDiagram-v2
  [*] --> CREATED
  CREATED --> IN_PROGRESS
  IN_PROGRESS --> PASSED
  IN_PROGRESS --> RFI_REQUIRED
  IN_PROGRESS --> EDD_REQUIRED
  IN_PROGRESS --> REJECTED
  RFI_REQUIRED --> IN_PROGRESS
  EDD_REQUIRED --> PASSED
  EDD_REQUIRED --> REJECTED
  PASSED --> [*]
  REJECTED --> [*]

Submit a complete onboarding package

Submit complete entity data, documents, and associated-person information before you expect Roots to begin review. Roots evaluates the applicable entity type, jurisdiction, product, and risk context to determine the required information.

For a business end customer, include the business identity, ownership and control structure, expected activity, and supporting documents. Link each UBO, director, control person, and authorized signatory to the business as an associated person.

Understand review outcomes

Outcome	Meaning	What you do
`PASSED`	Roots first-line review has passed. A bank gate can still apply before activation.	Retrieve the linked account or product state before continuing.
`RFI_REQUIRED`	Roots needs information, clarification, or supporting documents.	Stop dependent automation and route the request to a human workflow.
`EDD_REQUIRED`	The relationship requires enhanced due diligence.	Collect the requested evidence and wait for the required decision.
`REJECTED`	The application cannot proceed.	Do not create or fund an account for the affected end customer.
Manual assessment	An exception requires human review.	Keep dependent activity blocked until Roots reports the outcome.

Apply automation boundaries

You can automate data collection, record creation, and status retrieval. Do not automate approval-direction overrides, release from a bank-controlled hold, or other decisions reserved to the partner bank.

A person status is not a substitute for a review outcome. Re-check the linked person, account, and restriction state after Roots resolves a review.

Next steps

Follow Onboard a business end customer to model a business and its associated people.
Read Holds, restrictions, and RFIs to manage escalated outcomes.
Read Compliance operating model for bank-gate behavior.