RiskOS™ Dashboard Setup
Learn how to set up Socure Advanced Prefill in the RiskOS™ Dashboard to autofill verified identity data from minimal inputs and streamline onboarding.
Set up Advanced Prefill in the RiskOS™ Dashboard
Before you start
Make sure you have the following:
Your account owner or administrator can enable this for you. If you're unsure who to contact, reach out to support for assistance.
If this is your first time working with workflows, review the Workflow overview to understand inputs, enrichments, routing logic, and decisions.
How it works
Advanced Prefill + Consumer Onboarding is a two-workflow solution in RiskOS™ designed to reduce onboarding friction while maintaining strong fraud and compliance controls.
- The Advanced Prefill workflow (
alt_advanced_pre_fill) determines whether it is safe to display verified identity data to the end user. It leverages products such as Digital Intelligence, Phone Risk, SIM Swap, Silent Network Authentication (SNA), and One-Time Passcode (OTP) to confirm device integrity and phone possession. This workflow does not perform KYC or fraud checks, and its decision logic cannot be modified to maintain security integrity. - The Consumer Onboarding workflow (
consumer_onboarding) performs full KYC and fraud evaluations on the final data—whether prefilled, edited, or manually entered by the user. It can be configured to match your organization’s specific onboarding and risk policies.
In short, Advanced Prefill controls when data can be shown, while Consumer Onboarding determines who can be approved.
Note:
The Advanced Prefill workflow can only be modified by an authorized solutions engineer from Socure's team. Self-service management of this workflow is disabled to protect unauthorized access to user data.
How Advanced Prefill fits into a workflow
Advanced Prefill is executed before Consumer Onboarding and acts as a data disclosure gate.
Once Advanced Prefill completes:
- Approved users see prefilled data
- Rejected users proceed with manual entry
- On-hold users resume after OTP verification
The Consumer Onboarding workflow is then initiated using the final data.
Execution flow in RiskOS™
Advanced Prefill uses an asynchronous execution model with pause-and-resume behavior.
-
Collect minimal input
The user provides minimal input:
phone_numberanddate_of_birth. Collect adi_session_tokenfrom the Digital Intelligence SDK to begin the Advanced Prefill flow. -
Run the Advanced Prefill workflow
The Advanced Prefill workflow (
alt_advanced_pre_fill) orchestrates the following checks to determine if verified data can be displayed:
- Digital Intelligence (DI) – Detect risky devices or sessions.
- Phone Risk – Evaluate line type, tenure, and velocity.
- SIM Swap – Check for recent SIM changes (requires carrier approval).
- Possession check (SNA → OTP fallback) – Confirm phone possession.
- Prefill enrichment – Return verified identity data.
- Phone Risk re-check – Validate name–phone correlation.
- Decision node – Return
APPROVE,REJECT, orON_HOLD.
-
Decision handling
Based on the workflow’s decision:
APPROVE→ The form is prefilled with verified data, and the user may review or correct fields.REJECT→ No prefill data is shown; the user must enter information manually.ON_HOLD→ The workflow pauses until OTP verification completes.
-
Start Consumer Onboarding
After the user reviews or enters their information, initiate a new Consumer Onboarding workflow (
consumer_onboarding) using the verified data returned from Advanced Prefill. This workflow performs full KYC and fraud evaluations and returns the final onboarding decision.
Asynchronous behavior
Advanced Prefill uses a pause-and-resume execution model when One-Time Passcode verification is required.
- The workflow enters ON_HOLD
- There is no API to force continuation
- The workflow resumes automatically on One-Time Passcode success, failure, or expiration
Consumer Onboarding must not be started until Advanced Prefill reaches a terminal state.
What Advanced Prefill evaluates
Advanced Prefill is intentionally conservative and may fail closed.
It evaluates:
- Device and session risk (Digital Intelligence)
- Phone legitimacy and tenure
- Recent SIM swap activity
- Phone possession (SNA → OTP)
- Allow / Deny list matches
- Name–phone correlation after Prefill resolution
Any failure or uncertainty may result in REJECT or ON_HOLD.
What customers can and cannot control
| Area | Customer-configurable |
|---|---|
| Advanced Prefill decision logic | No |
| Device / phone score thresholds | No |
| Consumer Onboarding routing | Yes |
| Step-up products (eCBSV, DocV) | Yes |
| Reason code handling | Yes |
| Allow / Deny lists | Yes |
Workflow components used
| Component | Purpose |
|---|---|
| Input | Collect minimal identity and session data |
| Enrichment | Evaluate device, phone, possession, identity |
| Rule Score Cards | Aggregate device and phone risk |
| Condition | Gate disclosure and step-ups |
| On Hold | Pause workflow for OTP |
| Decision | Approve, reject, or hold |
Quick start checklist
Use this checklist to validate readiness before production launch.
Updated 25 days ago
