Lion Platform — Integrated Compliance
KYC that opens accounts.
Not KYC that delays them.
Identity verification, OFAC screening, PEP detection, and 24+ global watchlist checks — embedded directly in the application workflow. No separate login. No separate tool. No compliance lag between application and account number.
Step 1
Applicant Submits
Name, DOB, SSN, address, phone
Step 2
Lion Initiates KYC
Automatically at submission
Step 3
Compliance Layer Activates
Routed to the appropriate screening provider
Step 4
Full Screening Runs
Identity, 24+ watchlists, PEP detection, fraud scoring
Step 5
Results Surface in Lion
Inline review, no platform switch
Step 6
Account Opens
Real-time on approval or threshold clearance
Compliance that's disconnected is compliance that costs you clients.
Legacy platforms treat identity verification as a separate workflow — a different tool, a different login, a different queue. Processors export data, check a result somewhere else, and manually reconcile the outcome back into the core system before an account can open. Every handoff is a delay. Every delay is a client who might not wait.
| Onboarding Step | Legacy Platform | Lion |
|---|---|---|
| KYC Initiation | Processor manually triggers through a separate tool after application arrives | ✓Automatic at application submission — no action required |
| OFAC / Watchlist Screening | Separate process, often same-day batch or manual export | ✓Simultaneous with identity check, results within seconds |
| PEP Detection | Manual check or separate vendor subscription | ✓Screened automatically across IZ_PEP and cross-referenced with applicant self-disclosure |
| Results Review | Log into the KYC vendor's portal to view results, then return to core system | ✓All results displayed inline — processor never leaves Lion |
| Watchlist Hit Review | Documented in a separate system; reconciled manually | ✓Clear or dismiss inline with full audit capture |
| Account Number Generation | After manual approval — often hours or days after KYC completes | ✓Instant at approval decision or automated threshold clearance |
| Audit Trail | Separate compliance system; not tied to account record | ✓Every KYC event, watchlist review, and step-up action logged in Lion's unified audit trail |
Best-in-class screening, seamlessly orchestrated.
Lion's compliance infrastructure connects to best-in-class identity verification and risk screening engines — orchestrated automatically so your team never has to manage vendor connections, API calls, or result reconciliation.
Identity Verification
KYC CoreName, date of birth, SSN, address, and phone verified against authoritative data sources. Documentary verification — government-issued ID, liveness check, selfie comparison — triggered automatically when identity confidence requires it.
Sanctions & Watchlist Screening
OFAC & PEPReal-time screening across 24+ US government, PEP, and international watchlists — simultaneous with identity verification, not sequenced after it. Per-hit match analysis and inline review workflow surfaced directly in Lion.
Advanced Risk Intelligence
Fraud & SignalsStructured risk scoring — synthetic identity detection, fraud signals, email, phone, and address correlation scores, PEP match flags. Machine-readable decision variables that power Lion's configurable auto-approval thresholds.
No vendor management on your end. Lion handles the screening integrations — provider connections, result normalization, and status tracking — so your team interacts with a single, consistent compliance interface regardless of which checks ran or which engine processed them.
The KYC Lifecycle
Application Submitted
Identity Data Submitted for Verification
Multi-Layer Screening Runs
Results Surface in Lion
Processor Reviews (or Threshold Auto-Approves)
Account Opens
Every data point verified. Every result structured.
KYC in Lion doesn't return a pass/fail verdict and stop there. Every identity check produces structured, field-level results — what matched, what didn't, and how confident the result is — so a processor reviewing a complex application sees exactly what the screening found, not a summarized narrative.
Identity Data Match
Each submitted field returns a discrete match result against authoritative data sources:
- Name — first, last, full
- Date of birth
- Social Security Number
- Address — street, city, state, ZIP
- Phone number
Documentary Verification & Step-Up
Triggered automatically when identity confidence requires it — or manually escalated by a reviewer when additional documentation is needed.
- Driver's license (front + back)
- Passport or state-issued ID
- Liveness check (configurable)
- Selfie comparison against document (configurable)
- Document authenticity assessment
Supporting documents for step-up review are stored in Lion's integrated document storage and attached permanently to the application record.
Fraud & Risk Intelligence
A structured set of machine-readable risk indicators goes beyond identity match — surfaced as labeled fields in the admin review panel.
- Synthetic identity score (elevated / very high)
- Overall fraud score
- Email risk (correlation + risk level)
- Phone risk (correlation + risk level)
- Address risk (correlation + risk level)
- Documentary verification required flag
Risk Signal Variables
Each of these is a discrete, boolean, queryable field on the KYC result — not a narrative text field. They power both the admin review display and the configurable auto-approval threshold logic.
watchlistMatch
Hit on any monitored watchlist
pepListMatch
Matched on PEP list (IZ_PEP or global)
kycListMatch
Direct KYC list match signal
alertlistMatch
Hit on internal alert or fraud list
fraudScoreVeryhigh
Fraud risk score in very high tier
syntheticScoreHigh
Synthetic identity risk elevated
syntheticScoreVeryhigh
Synthetic identity risk very high
emailRiskHigh
Email address correlation flagged
emailRiskVeryhigh
Email address in very high risk tier
emailCorrelationScoreLow
Low email-to-identity correlation
phoneRiskHigh
Phone number correlation flagged
phoneRiskVeryhigh
Phone number in very high risk tier
phoneCorrelationScoreLow
Low phone-to-identity correlation
addressRiskHigh
Address risk elevated
addressCorrelationScoreLow
Low address-to-identity correlation
addressListMatch
Address matches a flagged location
needDocv
Documentary verification required
deviceRiskRc
Device risk reason codes (array)
Operations teams see labeled indicators. Integrators get the full structured payload. Every risk signal above is surfaced in the admin review panel with a human-readable label and status indicator — no technical interpretation required for day-to-day reviews. For teams building CRM integrations, automated routing workflows, or external reporting pipelines, the complete structured JSON result is available via API.
KYC Configurability & Account Import Flexibility
Verification steps are configurable per provider. Enable or disable liveness checks, photo ID capture, and selfie comparison to match your current compliance policies — or to adapt as requirements shift.
Configurable Verification Steps
Each verification step — liveness check, photo ID upload, selfie comparison — can be individually toggled at the provider configuration level. Tune your KYC workflow to match your current policies, regulatory obligations, and the risk profile of your applicant population without rebuilding your onboarding flow.
Account Imports & Takeovers
When acquiring a book of business or migrating existing account holders, KYC checks can be performed without burdening the account holder with a full re-verification flow. Screening can be run in the background against existing identity data, keeping the transition frictionless for clients who would otherwise disengage.
24+ watchlists. Simultaneous. Every applicant. Every time.
This is not a checkbox against a single OFAC file. Every applicant is screened simultaneously against the full suite of US government, international, and PEP watchlists. Every hit — regardless of which list triggered it — surfaces the same structured review workflow with full match analysis and audit-captured disposition.
Watchlists screened simultaneously at every application
Of applications screened — no manual initiation required
PEP detection — screened + applicant self-disclosure cross-referenced
Additional vendor logins required to review a hit
US Government Watchlists
US_SDN — OFAC Specially Designated Nationals and Blocked Persons List. US_SSI — Sectoral Sanctions Identifications. US_FSE — Foreign Sanctions Evaders.
Politically Exposed Persons
International PEP list screened automatically at application. Cross-referenced against the applicant's own self-disclosure from the compliance questionnaire. Both the screened result and the self-disclosure are visible to the reviewing processor.
International / Multilateral
EU_CON — EU Consolidated Financial Sanctions. UK_HMC — UK HM Treasury Consolidated List. IZ_UNC — UN Consolidated List. Includes country-specific lists for Singapore and Turkey.
How Watchlist Hits Work
A watchlist hit does not automatically fail an application. It routes the application to inline review with full match analysis — so a processor can distinguish a genuine sanction from a common-name false positive, act on it, and record the rationale.
Hit Detected
Application pauses at WATCHLIST_COMPLETE with hit status pending_review. The processor sees: which list triggered the hit, which fields matched (name, DOB, location, document numbers) and the confidence of each match, the date the entry first appeared on the watchlist (firstActive), and whether the entry is currently active or has since been removed (inactiveSince). All of that context is on one screen — no external lookup needed to evaluate the hit.
Processor Reviews Inline
Two actions available — both audit-captured. Clear: hit is reviewed; applicant approved despite match (with rationale recorded). Dismiss: hit is a false positive — common name match, wrong birth year, etc. — and is dismissed. Both actions are permanent, immutable log entries.
Disposition Recorded
The review decision — who reviewed it, when, and what was decided — is permanently attached to the applicant's record. Status transitions to reviewed, cleared, or dismissed. The record is never altered; only the status is updated forward.
Ongoing monitoring is included. Lion subscribes to watchlist monitoring for every verified account holder. When an existing account holder subsequently appears on a monitored watchlist, Lion receives an alert automatically — no manual pull required, no separate monitoring subscription needed. The hit surfaces in the same inline review workflow used at onboarding.
Every KYC result, inline. Every action, one click.
A processor reviewing a pending application in Lion's portal sees the full compliance picture without switching tools. Identity verification results, risk signals, watchlist screening, application status, and all review actions are on a single page — nothing exported, nothing reconciled, nothing re-entered.
Identity Verification Widget
Each verification step is shown individually: KYC Check (identity data match results), Documentary Verification (if triggered), Risk Check (fraud and synthetic identity signals), and Watchlist Screening status. Each step shows its own status so a processor can see not just the overall outcome but exactly which check requires attention — no guesswork, no hunting through raw data.
Watchlist Screening Panel
Separate from the identity widget, the watchlist panel shows overall screening status and per-hit details — which list triggered, what fields matched, match confidence, temporal data (when the entry became active, whether it's currently inactive), and the review action buttons. Clearing or dismissing a hit takes one click and captures the reviewer's identity and timestamp automatically.
Deep Investigation Access
For applications requiring deeper investigation, a direct link to the underlying account record in the banking infrastructure layer is available inline — no separate login, no separate system to navigate. Application status (PENDING_APPROVAL, APPROVED, REJECTED) is displayed as a live status pill so a processor can confirm downstream state without leaving Lion.
Admin Actions Available
From the same page: view all KYC and watchlist results, clear or dismiss watchlist hits with recorded rationale, reset identity verification data and trigger re-verification, edit compliance information (including PEP flag correction), and approve or reject the application. The entire review-to-decision workflow completes without leaving Lion.
Identity Verification
Watchlist Hit · Pending Review
US_SDN — Specially Designated Nationals
Name match: partial_match · DOB match: no_match
Location: no_match · Documents: no_data
First active: 2019-03-14 · Currently active: Yes
Application Status
Clean applicants shouldn't wait for a manual review queue.
Lion supports configurable risk thresholds that evaluate every KYC result automatically. When an applicant clears the threshold — no watchlist hits, no PEP match, fraud and identity scores within acceptable range — the application is approved without processor involvement. The account number exists within seconds of the application being submitted.
Configure once. Every clean applicant moves at full speed. The risk threshold is a provider-level setting — set it once and every future application is evaluated against it automatically. Different thresholds for different distribution channels are supported, giving you precise control over where the fast lane applies. Clean applicants never touch the review queue. Complex cases still do.
What Happens When a Threshold Is Cleared
KYC Result Evaluated Against Threshold
Application Approved Automatically
Account Number Generated in Real Time
Account Is Immediately Active — Fund It Today
Applications That Don't Clear the Threshold
Applications that don't pass the threshold are not rejected — they're routed to the manual review queue. The processor applies the standard review workflow described above. The threshold creates a fast lane for clean applicants without removing the review path for complex cases.
Conservative Threshold
More applications route to manual review. Suitable for custodians with stricter risk appetite or higher-risk applicant populations. Processors review a larger percentage but every review is informed by the same structured KYC data.
Permissive Threshold
More applications auto-approve. Suitable for custodians with lower-risk applicant populations or distribution channels with established client vetting at the source. Clean applications open accounts in seconds — funded and invested the same day.
| Step | Legacy Platform | Lion with Auto-Approval |
|---|---|---|
| Application submitted | Enters manual review queue | KYC runs automatically at submission |
| Identity screening | Processor manually initiates | Automatic — initiated at submission |
| Watchlist check | Separate batch or manual process | Simultaneous with identity, same session |
| Review (clean applicant) | Required regardless of risk | Bypassed when threshold is cleared |
| Account number | After manual approval decision | Automatic — within seconds of KYC clear |
| Client notification | After processor approves | Immediate — account active, ready to fund |
| First contribution | Next business day or later | Same-day funding — account open, funded, and asset purchased in one session |
KYB — Know Your Business
Entity accounts — LLCs, partnerships, trusts, and corporations holding SDIRA interests — flow through the same compliance infrastructure as individual KYC. Business entity details, ownership structure, and beneficial owner information are verified at the same point in the application workflow, with the same watchlist and sanctions screening applied.
Entity Verification
Entity type, formation documents, EIN, and business address are verified through the same KYB workflow used for individual KYC. The same watchlist and sanctions screening that runs for individuals runs for entities — no separate compliance process, no separate review queue.
Beneficial Owners
Ownership structure and beneficial owner information are captured in the application model. Individual owners are subject to the same identity and watchlist screening as direct applicants — the compliance chain doesn't break at the entity boundary.
Inherited IRA Context
For inherited accounts, Lion captures the original owner's identity — name, date of birth, date of death, SSN, and the beneficiary relationship. This context is available to the reviewing processor and is part of the application record permanently.
Same infrastructure, same audit trail. KYB screening surfaces in the same application review panel as individual KYC. Processors don't interact with a separate interface for entity accounts — the review workflow is identical whether the applicant is an individual or an LLC.
Every KYC interaction is a permanent audit record.
Lion's audit trail is not a KYC-specific log — it's the platform's unified activity log, and KYC events are first-class citizens in it. Every screening initiation, every watchlist hit, every reviewer action, every step-up approval, and every approval or rejection decision is a permanent, immutable entry tied to the applicant's record.
System — triggered on application submission
System — KYC provider webhook
System — screening provider
Sarah K. · Compliance Officer · 192.168.1.44
Sarah K. · Compliance Officer
Immutable Records
Audit log entries are never edited or deleted. A watchlist hit that was dismissed remains in the log alongside the dismissal rationale — forever. Regulators and auditors see the complete decision chain, not a sanitized summary.
Actor Attribution
Every human action captures who did it — the specific user, their role, and their IP address. System events capture which external trigger (webhook, Crown callback, API key) initiated the change. There is no anonymous action in Lion's audit trail.
Unified — Not Siloed
KYC events are in the same audit stream as account changes, document uploads, fund transfers, and admin actions. A single audit export covers the entire account lifecycle — compliance review and all — without stitching together data from multiple systems.
Full compliance, headless. KYC as a first-class API operation.
Lion's KYC infrastructure is fully accessible via API. Submit an application, poll verification status, retrieve watchlist hit details, take review actions, and handle approvals — all programmatically. Build a fully white-labeled onboarding experience in your own interface while Lion and Crown handle the compliance layer underneath.
POST · Submit an application and trigger KYC
// Application submitted with submitImmediately=true (default)
// KYC initiates automatically — no separate trigger needed
POST /api/v1/onboard/applications
Authorization: Bearer lk_live_••••••••••••••••••••••
Content-Type: application/json
{
"firstName": "Jordan",
"lastName": "Mitchell",
"dateOfBirth": "1978-04-22",
"ssn": "•••-••-6781",
"address": {
"street": "742 Evergreen Terrace",
"city": "Springfield",
"state": "OR",
"zip": "97401"
},
"phone": "+15415550198",
"iraType": "TRADITIONAL",
"compliance": {
"politicallyExposed": false,
"cannabis": false,
"gambling": false
}
}Response
{
"id": "app_2f8ac7e1-…-c3d1",
"status": "UNDER_REVIEW",
"kycStatus": "KYC_IN_PROGRESS",
"watchlistStatus": "WATCHLIST_WAITING",
"crownApplicationId": ••••••,
"createdAt": "2025-09-12T14:22:03Z"
}GET · Poll KYC and verification status
GET /api/v1/applications/{id}/verification
Authorization: Bearer lk_live_••••••••••••••••••••••
// Response — identity complete, watchlist hit requires review
{
"applicationId": "app_2f8ac7e1-…",
"identityStatus": "KYC_COMPLETE",
"watchlistStatus": "WATCHLIST_COMPLETE",
"provider": "OSCILAR",
"riskSignals": {
"watchlistMatch": true,
"pepListMatch": false,
"fraudScoreVeryhigh": false,
"syntheticScoreHigh": false,
"emailRiskHigh": false,
"needDocv": false
},
"watchlistHits": [
{
"hitId": "wlh_8c3f…",
"listCode": "US_SDN",
"reviewStatus": "pending_review",
"nameMatch": "partial_match",
"dobMatch": "no_match",
"locationMatch": "no_match"
}
]
}Watchlist Review Actions via API
PATCH · Dismiss a watchlist hit (false positive)
PATCH /api/v1/applications/{id}/screening/hits/{hitId}
Authorization: Bearer lk_live_••••••••••••••••••••••
Content-Type: application/json
{
"action": "dismiss",
"rationale": "Common name partial match; DOB and location no_match. Confirmed false positive."
}
// Response
{
"hitId": "wlh_8c3f…",
"reviewStatus": "dismissed",
"reviewedBy": "usr_4a2d…",
"reviewedAt": "2025-09-12T14:38:17Z",
"auditEventId": "aud_e7c1…"
}PUT · Approve application after KYC review
PUT /api/v1/applications/{id}/decision
Authorization: Bearer lk_live_••••••••••••••••••••••
Content-Type: application/json
{
"decision": "approve"
}
// Response — account number created in real time
{
"applicationId": "app_2f8ac7e1-…",
"accountId": "acc_7b9e…",
"accountNumber": "••••••••••",
"status": "ACTIVE",
"crownStatus": "APPROVED",
"openedAt": "2025-09-12T14:39:03Z"
}Webhook Events — Real-Time Compliance Notifications
Register a webhook endpoint to receive real-time events as KYC and watchlist screening progress. Drive your own onboarding UX or internal workflow routing without polling.
application.kyc.complete
Identity verification finished — includes final identity status and risk signal summary. If all signals are clean, this may be immediately followed by application.approved for threshold-cleared applications.
application.watchlist.hit
A watchlist hit was detected. Payload includes the hit ID, list code, and match analysis. Use this to route the application to your review queue or alert your compliance team — the action must be taken in Lion or via the review API.
application.approved
Application approved — account number available. Payload includes the account ID and the account number. This is the event to trigger your post-onboarding flow: funding instructions, welcome communication, or first-contribution prompt.
Full OpenAPI schema available. Every request shape, response type, and enum value is documented in Lion's Swagger spec. The client SDK is auto-generated from the same spec — type-safe, versioned, and always in sync with the live API. No hand-maintained type definitions.
KYC is part of the Lion license.
Compliance shouldn't require a separate procurement. Lion's integrated KYC — identity verification, OFAC and watchlist screening, PEP detection, admin review interface, audit trail, and auto-approval thresholds — is an optional feature included in Lion's annual license.
Included in the license. KYC access — the admin interface, watchlist coverage, and audit logging — is part of the platform. No compliance add-on required to enable reviews.
Licensed on annual B2B terms. KYC is covered by the same annual terms as the rest of Lion. We walk through those terms with you on a call.
Optional — not required. KYC is an opt-in feature. If your onboarding workflow has compliance handled upstream or through a different channel, Lion doesn't force the screening layer. Enable it at the provider level when it fits your workflow.
Provider flexibility. No lock-in to a single identity provider. Crown's dual-provider architecture means provider flexibility is built in — switching or adding a second screening provider doesn't require a platform migration.
OFAC and watchlist monitoring included. The 24+ watchlist coverage described above — including ongoing monitoring when active — is not a separate subscription. It's part of the KYC workflow that runs at every application.
Auto-approval threshold is a config, not a paid tier. Configuring the risk threshold that enables automated approvals is a provider-level setting — not a premium feature that requires a contract upgrade.
Every item above is available today — no roadmap items, no locked tiers, no feature flags that require a support ticket to enable. If you're running accounts through Lion, this is the compliance layer that comes with it.
Start with compliance done right.
Lion's KYC infrastructure handles the identity, sanctions, and fraud layer so your team focuses on the client relationship — not the compliance queue. Embedded in the platform. Priced per use. Ready to go.
Lion Platform — Built for regulated account custodians.
Related reading
- HubLion in depthEvery long-form page on how Lion handles the daily work of a self-directed book, in one place.Read it
- ExplainerHow Lion worksThe application pipeline, the request model every movement flows through, and where statements and tax forms come from.Read it
- WalkthroughLion Platform SeriesA module-by-module walk through the account-holder portal, admin tools, payments and bulk imports.Read it
- In depthDocument intakeProcessors hand forms to the in-app assistant, it proposes each record, and staff approve before anything changes.Read it
- In depthDeposit reconciliationHow incoming deposits arrive from the bank, get matched to accounts and post, including split deposits and check holds.Read it
- FAQLion FAQShort answers on account types, asset types, ACH collection, tax forms, pricing and implementation.Read it
