Set up Account Intelligence

Before you start

Make sure you have the following:

Access to the RiskOS™ Dashboard with the Account Intelligence enrichment enabled.

• Your account owner or administrator can enable this for you. If you're unsure who to contact, reach out to support for assistance.

A basic understanding of RiskOS™ workflows and components.

• If this is your first time working with workflows, review the Workflow overview to understand inputs, enrichments, routing logic, and decisions.

How it works

Socure Account Intelligence and Account Intelligence Premier are identity verification enrichments available in RiskOS™. They validate inputs such as account number, routing number, and PII elements (e.g., name, address, or date of birth) against authoritative sources to generate score-based decisions on account ownership and availability.

Account intelligence is available as either Standard or Premier enrichments. Each enrichment will have a standard set of entitlements.

Account Intelligence

Best for quick confirmation of account existence and ownership.

• availabilityScore: Confidence level that the account is open and active
• ownershipScore: Confidence level that the applicant owns or controls the account
• reasonCodes: Structured insights into why an account passed, failed, or was inconclusive
• fieldValidations: Input-level checks (e.g., routing number, account number, SSN/EIN, name) and their verification results

Account Intelligence Premier

Best for high-assurance account validation with deeper insights.

• availabilityScore and ownershipScore: Expanded with deeper insights from premium data sources
• reasonCodes: More granular attribution to highlight signals from authoritative and premium sources
• fieldValidations: Enhanced input-level verification across consumer and business accounts
• premiumSignals: Additional insights from exclusive data sources to increase confidence in high-risk use cases

How Account Intelligence fits into a workflow

In RiskOS™, workflows are built by connecting reusable components. Account Intelligence is added as an Enrichment step.

Once the enrichment runs, its outputs are available to downstream workflow components, including:

• Conditions
• Decision rules
• Rule score cards
• Manual review steps
• Final decisions

For more detail on these components, see Workflow Steps.

Execution flow in RiskOS™

Account Intelligence runs synchronously as part of a RiskOS™ workflow. There is no user handoff or pause in execution.

Input
Account Intelligence
Routing logic
Decision

At a high level, the execution flow looks like this:

1. Input You call the Evaluation API with account details and supporting identity attributes.

2. Account Intelligence enrichment RiskOS™ evaluates account availability and ownership using configured inquiry types.

3. Routing logic The workflow evaluates availability, ownership, and reason codes.

4. Decision The workflow returns a final outcome (for example, Accept, Review, or Reject).

Workflow components used by Account Intelligence

Account Intelligence uses a subset of standard RiskOS™ workflow components.

Configure Account Intelligence

Add Account Intelligence to a workflow

1. In the RiskOS™ Dashboard, go to Workflows and create a new workflow or open an existing one.
2. On the workflow canvas, select the plus (+) icon.
3. Add an Enrichment step and select:
   • Socure Account Intelligence, or
   • Socure Account Intelligence Premier

Configure inputs and routing

Typical required inputs include:

• routing_number
• account_number
• account_inquiries (for example, AVAILABILITY, OWNERSHIP, or both)

Optional inputs may include:

• Consumer or business identity attributes
• Account type (checking, savings)
• Additional PII to improve ownership confidence

Routing strategies should align with your risk policy, including how to handle:

• Inactive or closed accounts
• Ownership mismatches
• Inconclusive or insufficient data

Save and publish

Once your workflow is configured, publish it to go live.

Workflow testing checklist

Use this checklist to confirm accuracy, resilience, and completeness before going live.

Account details

• Routing numbers are valid and correctly formatted.
• Account numbers fall within expected issuer or bank norms.
• Account type is captured and used consistently where required.
• Consumer vs. business account context is applied consistently.

Name matching inputs

• Account holder name inputs are validated and normalized.
• Business and individual name formats are handled correctly.
• Normalization rules are applied consistently across inputs.

PII (optional but recommended)

• Supporting PII is validated and normalized when provided.
• Dates of birth reject impossible values.
• Phone and email inputs are validated where used.
• Address inputs follow regionally aware validation rules.
• National ID handling follows regional requirements.

Request schema conformance

• Inquiry types are set correctly for the intended use case.
• Retry, idempotency, and fallback behavior are defined.