Introduction
A graphical interface that guides users through complex journeys, such as onboarding, combining interrelated identification, verification and signing steps.
- Universe:
- Umbrella
- Status:
- live
- Access:
- Contact IDCanopy for credentials and product access.
- Testing:
- Contact IDCanopy for test details.
Guide users through a complete process
IDCanopy Workflows & UI provides the graphical, user-facing experience for processes that involve more than one check. Instead of building a separate screen and integration for each capability, bring the related steps together in a guided journey that users can complete within your service.
An onboarding journey, for example, can collect information, verify a person or business, request supporting evidence and lead into signing. The steps are interrelated: information established earlier can be used later, and the journey can ask for further action when the case requires it. The exact steps depend on the configured process and enabled capabilities.
Workflows across capabilities
A journey can combine KYC, KYB, Identity & Signing and Risk Intelligence. These are the capabilities behind the process; the workflow and UI organise how the user moves through it. Use this integration when you want a guided experience rather than assembling every interaction yourself. For individual checks within your own application and UI, use the IDCanopy API.
QES is an upcoming capability that can be incorporated into a workflow, rather than a separate integration family. The QES identify-and-sign documentation describes its current, separate test-environment contract; do not assume that contract is already a step in every hosted journey. See the platform overview and Identity & Signing for product context.
Your configured integration
Talk to IDCanopy about the journey you want to build. We will provide your configured workflow, personalised handshake request and integration instructions, including the enabled steps, authentication and result delivery. Contact office@idcanopy.com to get started.
How it connects to your application
Your backend creates a journey and receives a uiHandle, the launch URL for its graphical interface. Your frontend opens it in an iframe or redirects the user to it. Journey outcomes arrive at your backend by webhook, so your application can continue the wider process.
Conceptual sequence. The browser hosts the interaction; your backend handles credentials and verifies result delivery. Hosted UI and webhook details remain pending verification.
Continue with Hosted UI for the launch pattern and Webhooks for result delivery. Both guides identify details still pending live verification.