Hosted Enrollment - Baselayer

Hosted enrollment is an onboarding flow Baselayer runs for you. You build the flow once in Console as a customer journey: the steps an applicant sees, the fields on each step, the checks to run and your branding. Then, for each applicant, you start a session from your server and send them to it. Baselayer collects their details, verifies them and tells you the outcome.

Try the journey builder

Console’s journey builder, running in your browser: add steps and fields, brand it, and click through every screen as an applicant. Nothing you do there leaves your browser.

How it works

Build and publish a journey in Console

Lay out the steps and fields, pick the checks, add your branding, then publish. Sessions always run the published version. See Build a journey.

Start a session per applicant

From your server, start a session on the journey. Baselayer answers with an embed URL: open it in an iframe or redirect the applicant to it. See Sessions and embedding.

The applicant completes the flow

They step through your journey on Baselayer’s hosted screens.

Receive the outcome

A webhook tells you the session completed and its verdict; then read the session’s results for everything the applicant entered and every check found. See Receive the outcome.

What the applicant sees

A typical journey runs through these screens, in order:

Screen	Shown when
Start verification	The journey uses Pre.Fill: the applicant enters their phone number and date of birth.
Verification code	When Pre.Fill sends a one-time code to that phone.
One screen per step	Every step you add, with its fields. If Pre.Fill finds no match, the applicant types their identity details on the identity step instead.
Verification in progress	While the journey’s checks run.
Decision	Approved, or pending review when a check needs a person to look or the journey runs no checks. It shows not approved only after your team rejects the application in Console.

Hosted enrollment must be enabled for your organization. Until it is, the session endpoints answer 403 with error code 37. Contact us to turn it on.

Try the journey builder

​How it works

​What the applicant sees

How it works

What the applicant sees