## Before you start  
Make sure you have the following:

Access to the RiskOS™ Dashboard with the **Address Risk** enrichment enabled.

- Your account owner or administrator can enable this for you. If you're unsure who to contact, [reach out to support](mailto:support@socure.com) for assistance.

A basic understanding of RiskOS™ workflows and components.

- If this is your first time working with workflows, review the [Workflow overview](https://help.socure.com/riskos/docs/workflow-overview) to understand inputs, enrichments, routing logic, and decisions.

## How it works  
Socure Address Risk evaluates a postal address and returns signals that help assess address-related fraud risk and consistency.

Address Risk returns:

- **Address Risk Score**: Indicates the likelihood that an address is associated with elevated fraud risk.
- **Name-Address Correlation**: Indicates how strongly an address aligns with the individual’s name.

You can use these signals across onboarding, authentication, profile updates, and higher-risk transactions to support fraud prevention and trust decisions.

### How Address Risk fits into a workflow  
In RiskOS™, workflows are built by connecting reusable components. Address Risk 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](https://help.socure.com/riskos/docs/workflow-steps).

### Execution flow in RiskOS™  
Address Risk runs synchronously as part of a RiskOS™ workflow. There is no user handoff or pause in execution.

```
Input

Address Risk

Routing logic

Decision
```

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

1. **Input**

You call the Evaluation API with address data and supporting identity information.

2. **Address Risk enrichment**

RiskOS™ evaluates the postal address and returns risk scores, correlations, and reason codes.

3. **Routing logic**

The workflow evaluates Address Risk outputs.

4. **Decision**

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

### Workflow components used by Address Risk  
Address Risk uses a subset of standard RiskOS™ workflow components.

| Component | Purpose | Typical input | Output / What to use next |
| --- | --- | --- | --- |
| **Input** | Start an evaluation | Address and supporting identity data | Workflow execution begins |
| **Enrichment** | Evaluate address risk | — | Risk score, correlation, reason codes |
| **Condition** | Branch based on risk or signals | Address risk signals | Route to appropriate path |
| **Decision Rule / Score Card** | Apply policy or scoring logic | Address risk signals | Pass/fail or cumulative risk classification |
| **Decision** | Emit final outcome | Routed value | Accept / Review / Reject |

## Configure Address Risk  
### Add Address Risk 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 **Address Risk**.

After the enrichment is added, its outputs can be referenced by downstream workflow logic.

### Configure inputs and routing  
Address Risk evaluates the address information provided by your workflow. Providing complete and accurate inputs improves overall signal quality.

#### Required inputs  
- `data.individual.given_name`

First name of the individual

- `data.individual.family_name`

Last name of the individual

- `data.individual.address.line_1`

First line of the address

- `data.individual.address.country`

Country code in ISO 3166-1 alpha-2 format

#### Optional supporting inputs  
When available, include:

- `data.individual.address.locality`
- `data.individual.address.major_admin_division`
- `data.individual.address.postal_code`

Omitting optional fields doesn't prevent execution, but may limit certain outputs or reduce confidence.

You can use Address Risk outputs—including scores, correlations, and reason codes—to configure routing logic that supports outcomes such as **Accept**, **Review**, or **Reject**.

Routing strategies should align with your organization’s fraud policy and risk tolerance.

### 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.

- Address inputs are collected, normalized, and passed consistently
- Country codes use the ISO 3166-1 alpha-2 format
- Workflow routing aligns with your fraud policy and risk tolerance
- Review or fallback paths are clearly defined
- Address Risk scores and reason codes are accessible to relevant teams

Updated about 2 months ago