---
updatedAt: 2026-11-12T15:06:37.000Z
agentTools:
  siteIndex: https://help.socure.com/llms.txt
  projectIndex: https://help.socure.com/riskos/llms.txt
---

# Integrate Deceased Check

Learn how to call the RiskOS™ Evaluation API for deceased status checks with Socure Deceased Check.

## Overview

This guide shows you how to:

1. Gather the consumer's identity data (name, date of birth, SSN, address) on your onboarding form.
2. Submit a `POST /api/evaluation` request from your backend with the collected data.
3. Act on the `decision` field (`ACCEPT`, `REVIEW`, or `REJECT`) in the response to route the consumer.
4. Flag deceased matches when the response returns reason code `R907` or `R909`.

<br />

## Before you start

<div class="strike-through-checklist-container">
  <div class="strike-through-checkbox-container">
    <input class="strike-through-checkbox" type="checkbox" />

<span><a href="https://help.socure.com/riskos/docs/deceased-check-riskos-setup#/">Configure and publish a workflow</a> for the <strong>Deceased Check</strong> enrichment. </span>

  </div>

  <div class="strike-through-checkbox-container">
    <input class="strike-through-checkbox" type="checkbox" />

<span> Confirm regional coverage for the Deceased Check enrichment (available exclusively in the United States).

  </div>

  <div class="strike-through-checkbox-container">
    <input class="strike-through-checkbox" type="checkbox" />

<span> Get your <strong>API key</strong> from the <a href="https://riskos.sandbox.socure.com/developers/key-management" target="_blank" rel="noopener noreferrer">API & SDK Keys</a> page in the RiskOS™ Dashboard. </span>

  </div>

</div>

<br />

## Start an evaluation

### Endpoint

Start with **Sandbox** for development and testing, then move to **Production** for live applications.

```http Sandbox
POST https://riskos.sandbox.socure.com/api/evaluation
```
```http Production
POST https://riskos.socure.com/api/evaluation
```

### Authentication

Include your API key in the `Authorization` header as a **Bearer token**, with standard JSON headers:

```http
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
Accept: application/json
X-API-Version: 2025-01-01.orion   # optional – pins a specific API version
```

<br />

### Example request

```curl
curl --location --request POST 'https://riskos.sandbox.socure.com/api/evaluation' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--data-raw '{
  "id": "APP-123456",
  "timestamp": "2022-07-28T06:10:54.298Z",
  "workflow": "consumer_onboarding",
  "data": {
    "individual": {
      "given_name": "Jessica",
      "family_name": "Roberts",
      "national_id": "123456789",
      "date_of_birth": "1943-09-19",
      "email": "j.roberts@example.com",
      "phone_number": "+13475551234",
      "address": {
        "line_1": "234 Main Street",
        "line_2": "Apt. 3C",
        "locality": "Jersey City",
        "major_admin_division": "NJ",
        "country": "US",
        "postal_code": "07307"
      },
      "additional_context": {
        "user_consent": true,
        "consent_timestamp": "2020-05-26T13:34:43Z"
      }
    }
  }
}'
```
```python
import os
import requests

url = "https://riskos.sandbox.socure.com/api/evaluation"
headers = {
    "Content-Type": "application/json",
    "Accept": "application/json",
    "Authorization": f"Bearer {os.getenv('YOUR_API_KEY')}"
}
payload = {
    "id": "APP-123456",
    "timestamp": "2022-07-28T06:10:54.298Z",
    "workflow": "consumer_onboarding",
    "data": {
        "individual": {
            "given_name": "Jessica",
            "family_name": "Roberts",
            "national_id": "123456789",
            "date_of_birth": "1943-09-19",
            "email": "j.roberts@example.com",
            "phone_number": "+13475551234",
            "address": {
                "line_1": "234 Main Street",
                "line_2": "Apt. 3C",
                "locality": "Jersey City",
                "major_admin_division": "NJ",
                "country": "US",
                "postal_code": "07307"
            },
            "additional_context": {
                "user_consent": True,
                "consent_timestamp": "2020-05-26T13:34:43Z"
            }
        }
    }
}

response = requests.post(url, headers=headers, json=payload)
data = response.json()
```

<br />

### Request schema

**Validation rules & accuracy guidance**

Deceased Check is available for U.S. records only. These rules ensure RiskOS™ can match the individual.

<Accordion title="Required fields" icon="fa-id-badge">
  Every request must include:

  * `given_name`
  * `family_name`
</Accordion>

<Accordion title="Conditionally required fields" icon="fa-list-check">
  Provide at least **one** of the following to identify the individual:

  * `national_id` (last 4 or full 9-digit SSN/ITIN)
  * `address.line_1` + `address.locality` + `address.major_admin_division` + `address.postal_code`
  * `date_of_birth`
  * `phone_number`
</Accordion>

<Accordion title="Accuracy guidance" icon="fa-bullseye">
  At least one conditional input is strongly recommended to improve match accuracy. When available, send `national_id`, `date_of_birth`, and full address fields. `address.country` and `additional_context.user_consent` are optional.
</Accordion>

<br />

#### Top-level fields

Path: root request object

<Table align={["left","left","left","left","left"]}>
  <thead>
    <tr>
      <th>
        Field
      </th>

      <th>
        Type
      </th>

      <th>
        Required
      </th>

      <th>
        Description
      </th>

      <th>
        Example
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        `id`
      </td>

      <td>
        String
      </td>

      <td>
        Required
      </td>

      <td>
        Required, customer-defined unique identifier for the request.

        This value must be unique for each evaluation. Reusing an ID causes RiskOS™ to treat the request as a re-run and can impact processing behavior, results, and downstream workflows.
      </td>

      <td>
        `"APP-123456"`
      </td>
    </tr>

    <tr>
      <td>
        `timestamp`
      </td>

      <td>
        String
      </td>

      <td>
        Required
      </td>

      <td>
        Timestamp when the evaluation was initiated.
      </td>

      <td>
        `"2022-07-28T06:10:54.298Z"`
      </td>
    </tr>

    <tr>
      <td>
        `workflow`
      </td>

      <td>
        String
      </td>

      <td>
        Required
      </td>

      <td>
        **RiskOS™** workflow name configured in your environment. <br /><br /> **Note:** The workflow name must be unique within your RiskOS™ environment. It is not scoped by use case and must identify a single active workflow for each Evaluation API request.
      </td>

      <td>
        `"consumer_onboarding"`
      </td>
    </tr>

    <tr>
      <td>
        `data`
      </td>

      <td>
        Object
      </td>

      <td>
        Required
      </td>

      <td>
        Main payload containing applicant or business information.
      </td>

      <td>

      </td>
    </tr>

    <tr>
      <td>
        → `individual`
      </td>

      <td>
        Object
      </td>

      <td>
        Required
      </td>

      <td>
        Primary identity object containing personal information.
      </td>

      <td>
        See `individual` schema below.
      </td>
    </tr>
  </tbody>
</Table>

<br />

#### `individual` fields

Path: `data.individual`

| Field                | Type   | Required    | Description                                                                                                                                | Example                                |
| :------------------- | :----- | :---------- | :----------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------- |
| `given_name`         | String | Required    | Applicant’s first name (omit prefixes like Mr., Ms.).                                                                                      | `"Jessica"`                            |
| `family_name`        | String | Required    | Applicant’s last name (omit suffixes like Jr., III).                                                                                       | `"Roberts"`                            |
| `national_id`        | String | Conditional | U.S. SSN (full or last 4 digits); improves precision for identity resolution.                                                              | `"123456789"`                          |
| `date_of_birth`      | String | Conditional | Date of birth (`YYYY-MM-DD`, `YYYYMMDD`, or `YYYY/MM/DD`).                                                                                 | `"1943-09-19"`                         |
| `address`            | Object | Conditional | Street, city, state (ISO 3166-2), postal code, and country (ISO 3166-1 alpha-2).                                                           | See `address` schema below.            |
| `phone_number`       | String | Optional    | Applicant’s phone number in E.164 format. The API expects the standard E.164 format but tolerates hyphens and spaces for user convenience. | `"+13475551234"`                       |
| `additional_context` | Object | Conditional | Provides supplementary metadata for RiskOS™ workflows (for example, consent info).                                                         | See `additional_context` schema below. |

<br />

#### `address` fields

Path: `data.individual.address`

| Field                  | Type                        | Required | Description                                     | Example             |
| :--------------------- | :-------------------------- | :------- | :---------------------------------------------- | :------------------ |
| `line_1`               | String                      | Optional | Street number/house name and street.            | `"234 Main Street"` |
| `line_2`               | String                      | Optional | Additional address data (apartment, landmarks). | `"Apt. 3C"`         |
| `locality`             | String                      | Optional | City, town, or village.                         | `"Jersey City"`     |
| `minor_admin_division` | String                      | Optional | District or borough.                            | `null`              |
| `major_admin_division` | String                      | Optional | State or province code (ISO 3166-2).            | `"NJ"`              |
| `country`              | String (ISO 3166-1 alpha-2) | Optional | Country code.                                   | `"US"`              |
| `postal_code`          | String                      | Optional | Postal or ZIP code.                             | `"07307"`           |

<br />

#### `additional_context` fields

Path: `data.individual.additional_context`

| Field               | Type                 | Required | Description                                                                                                                                                                                                                                                                                   |
| :------------------ | :------------------- | :------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `user_consent`      | Boolean              | Required | Indicates whether the user provided consent.                                                                                                                                                                                                                                                  |
| `consent_timestamp` | String `<date-time>` | Optional | The date and time when the user provided consent, specified in ISO 8601 / RFC 3339 format. If not provided, defaults to the current transaction timestamp. Although optional, it is required for **eCBSV** to meet the 90-day consent window set by the SSA. Example: `2022-07-28T06:10:54Z`. |

<br />

## Example response

When you call the Evaluation API, RiskOS™ returns a JSON payload that includes the final decision, evaluation metadata, and enrichment-specific results.

```json
{
  "id": "APP-123456",
  "eval_id": "6dc8f39c-ecc3-4fe0-9283-fc8e5f99e816",
  "workflow": "consumer_onboarding",
  "workflow_id": "dc7f261e-b158-477e-9770-7e4eae066156",
  "workflow_version": "28.16.0",
  "status": "CLOSED",
  "sub_status": "Review",
  "decision": "REVIEW",
  "decision_at": "2025-10-07T23:50:03.738648201Z",
  "tags": [],
  "review_queues": [],
  "data_enrichments": [
    {
      "enrichment_name": "Socure Deceased Check",
      "enrichment_endpoint": "https://sandbox.socure.com/api/3.0/EmailAuthScore",
      "enrichment_provider": "Socure",
      "status_code": 200,
      "request": {},
      "response": {
        "referenceId": "f3863a33-69ca-43c2-90e0-8b4344a41a09",
        "deceasedCheck": {
          "socureId": "46fd3b11-a130-4915-8cc4-074bbd799669",
          "reasonCodes": [
            "R909",
            "R907"
          ],
          "firstName": "Jessica",
          "middleName": "Marie",
          "surName": "Roberts",
          "nationalId": "123456789",
          "dob": "1943-09-19",
          "dod": "2022-11-19",
          "age": 79,
          "sourceAttribution": [
            "Probate"
          ]
        },
        "customerProfile": {
          "userId": "u-1a2b3c4d",
          "customerUserId": "cust-98765"
        }
      }
    }
  ]
}

```

### Key response fields

RiskOS™ returns a consistent set of top-level fields that describe the outcome of an evaluation, with enrichment-specific results that depend on your workflow configuration.

#### Where to find specific results

| Area                             | Fields                                                                                | How to use it                                                                                                                                              |
| -------------------------------- | ------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Decision and routing**         | `decision`, `decision_at`, `tags`, `review_queues`, `notes`, `score`                  | **Primary control signals.** Branch application logic using `decision`. Use tags, queues, notes, and score for secondary routing, review, and explanation. |
| **Module results**               | Module-specific fields (for example: `reasonCodes`, scores, extracted attributes)     | Evidence and signals produced by workflow modules. Use for escalation, compliance review, investigation, and audit.                                        |
| **Identifiers and traceability** | `id`, `eval_id`                                                                       | Persist these identifiers to correlate API calls, logs, webhooks, GET requests, and support cases.                                                         |
| **Enrichment execution**         | `data_enrichments[]` (`response`, `status_code`, `total_attempts`, `is_source_cache`) | Inspect enrichment outputs and detect provisioning issues, partial failures, retries, or cached responses.                                                 |
| **Workflow context**             | `workflow`, `workflow_id`, `workflow_version`                                         | Understand which workflow ran and which version produced the result. Useful for debugging and historical analysis.                                         |
| **Evaluation lifecycle**         | `eval_status`, `status`, `sub_status`                                                 | Execution and case state only. Useful for monitoring and asynchronous workflows. **Do not use for business decisions.**                                    |
| **Execution context**            | `eval_source`, `eval_start_time`, `eval_end_time`, `environment_name`                 | Observability and performance metadata for latency tracking, environment validation, and API vs Dashboard attribution.                                     |

<br />

### Decision and routing (primary control signals)

Use these fields to determine what action your application should take.

> `decision` values are workflow-specific and may differ from the examples shown in this guide.

| Field           | Type                 | Description                                                                                                                                                                                                | Example                            |
| :-------------- | :------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :--------------------------------- |
| `decision`      | String (enum)        | Final evaluation result.<br /><br />Possible values:<br />• `ACCEPT`<br />• `REVIEW`<br />• `REJECT`<br /><br />**Note**: The fields returned can be customized to fit your integration or business needs. | `"REVIEW"`                         |
| `decision_at`   | String `<Date-Time>` | RFC 3339 timestamp when the decision was finalized.                                                                                                                                                        | `"2025-10-07T23:50:03.738648201Z"` |
| `score`         | Number               | If configured for a workflow, provides an aggregate score of all steps. This can be used for risk banding, additional routing, or analytics alongside the primary `decision` value.                        |                                    |
| `tags`          | Array of strings     | Array of labels applied during the workflow to highlight routing choices, notable signals, or rule outcomes. Useful for reporting, segmentation, or UI highlighting in the RiskOS™ Dashboard.              | `[]`                               |
| `review_queues` | Array of strings     | Lists any manual review queues the evaluation was sent to. Empty when the case is fully auto-resolved without human review.                                                                                | `[]`                               |
| `notes`         | String               | Freeform text field for analyst or system comments about the evaluation. Often used to capture manual review rationale or investigation context.                                                           |                                    |

<br />

### Evaluation lifecycle and status

These fields describe where the evaluation is in its lifecycle and are useful for monitoring and asynchronous workflows.

| Field         | Type          | Description                                                                                                                                                                  | Example                |
| :------------ | :------------ | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :--------------------- |
| `eval_status` | String (enum) | Indicates the current state of an evaluation in RiskOS™.<br /><br />Possible values:<br />• `evaluation_completed`<br />• `evaluation_paused`<br />• `evaluation_in_process` | `evaluation_completed` |
| `status`      | String (enum) | Indicates the current state of an evaluation or case.<br /><br />Possible values:<br />• `OPEN`<br />• `CLOSED`                                                              | `"CLOSED"`             |
| `sub_status`  | String        | Provides additional detail about the evaluation status.<br /><br />Example values:<br />• `Under Review`<br />• `Pending Verification`<br />• `Accept`<br />• `Reject`       | `"Review"`             |

<br />

### Identifiers and traceability

Use these fields to correlate requests, logs, webhooks, and support cases.

| Field              | Type                           | Description                                                                                   | Example                                  |
| :----------------- | :----------------------------- | :-------------------------------------------------------------------------------------------- | :--------------------------------------- |
| `id`               | String (UUID or custom string) | Your evaluation identifier within RiskOS™.<br /><br />**Note**: This is *customer-generated*. | `"APP-123456"`                           |
| `eval_id`          | String (UUID)                  | RiskOS™-generated unique identifier for the evaluation.                                       | `"6dc8f39c-ecc3-4fe0-9283-fc8e5f99e816"` |
| `workflow`         | String                         | Name of the workflow executed.                                                                | `"consumer_onboarding"`                  |
| `workflow_id`      | String (UUID)                  | Unique identifier for the workflow run.                                                       | `"dc7f261e-b158-477e-9770-7e4eae066156"` |
| `workflow_version` | String                         | Version of the executed workflow.                                                             | `"28.16.0"`                              |

<br />

### Execution context

These fields provide timing and environment context for the evaluation.

| Field              | Type                 | Description                                                                                                                                                                                                         | Example                            |
| :----------------- | :------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | :--------------------------------- |
| `eval_source`      | String enum          | Indicates where the evaluation was initiated from.<br /><br />Possible values:<br />• `API`: Request submitted via the Evaluation API.<br />• `Dashboard`: Case created or evaluated through the RiskOS™ Dashboard. | `"API"`                            |
| `eval_start_time`  | String `<Date-Time>` | RFC 3339 timestamp for when RiskOS™ started processing the evaluation. Useful for latency and performance monitoring.                                                                                               | `"2025-10-07T23:50:03.60187976Z"`  |
| `eval_end_time`    | String `<Date-Time>` | RFC 3339 timestamp for when RiskOS™ finished processing the evaluation. Can be paired with `eval_start_time` to compute total processing time.                                                                      | `"2025-10-07T23:50:03.738794253Z"` |
| `environment_name` | String               | Indicates which environment the evaluation ran in. Typically `Sandbox` for testing or `Production` for live traffic.                                                                                                | `"Sandbox"`                        |

<br />

### Enrichment results

Enrichment outputs are returned in the `data_enrichments` array.

| Field                 | Type    | Description                                                                                               | Example                                               |
| :-------------------- | :------ | :-------------------------------------------------------------------------------------------------------- | :---------------------------------------------------- |
| `enrichment_name`     | String  | Name of the module or service executed (for example, Digital Intelligence, Verify Plus, Sigma Synthetic). | `"Socure Deceased Check"`                             |
| `enrichment_endpoint` | String  | API endpoint that processed the enrichment.                                                               | `"https://sandbox.socure.com/api/3.0/EmailAuthScore"` |
| `enrichment_provider` | String  | Provider of the enrichment service (`Socure`, `RestAPI`, etc.).                                           | `"Socure"`                                            |
| `status_code`         | Integer | HTTP status returned by the enrichment API call.                                                          | `200`                                                 |
| `request`             | Object  | Request payload sent to the enrichment service.                                                           | See `request` schema below.                           |
| `response`            | Object  | Normalized response data from the enrichment service.                                                     | See `response` schema below.                          |
| `error`               | String  | Populated only if the enrichment encountered an error.                                                    |                                                       |
| `is_source_cache`     | Boolean | Indicates whether cached data was used instead of a live API call.                                        | `false`                                               |
| `total_attempts`      | Integer | Number of attempts made to retrieve the enrichment data.                                                  | `1`                                                   |

<br />

#### `response` fields

| Field             | Type          | Description                                                                          | Example                                                    |
| :---------------- | :------------ | :----------------------------------------------------------------------------------- | :--------------------------------------------------------- |
| `referenceId`     | String (UUID) | Unique identifier assigned to each enrichment after a RiskOS™ workflow is finalized. | `"f3863a33-69ca-43c2-90e0-8b4344a41a09"`                   |
| `deceasedCheck`   | Object        | Deceased status and attribution data for the queried individual.                     | See the `deceasedCheck` schema in the following section.   |
| `customerProfile` | Object        | Customer profile identifiers echoed back for the queried individual.                 | See the `customerProfile` schema in the following section. |

<br />

#### `deceasedCheck` fields

| Field               | Type             | Description                                                               | Example                                  |
| :------------------ | :--------------- | :------------------------------------------------------------------------ | :--------------------------------------- |
| `socureId`          | String (UUID)    | Socure’s persistent identity ID used for Graph Intelligence correlations. | `"46fd3b11-a130-4915-8cc4-074bbd799669"` |
| `reasonCodes`       | Array of strings | Structured codes indicating deceased status.                              | `["R909", "R907"]`                       |
| `firstName`         | String           | Resolved first name.                                                      | `"Jessica"`                              |
| `middleName`        | String or null   | Resolved middle name.                                                     | `"Marie"`                                |
| `surName`           | String           | Resolved last name.                                                       | `"Roberts"`                              |
| `nationalId`        | String           | SSN resolved from the deceased record (full or last 4).                   | `"123456789"`                            |
| `dob`               | String           | Date of birth.                                                            | `"1943-09-19"`                           |
| `dod`               | String or null   | Date of death if reported.                                                | `"2022-11-19"`                           |
| `age`               | Integer          | Calculated age if date of death provided.                                 | `79`                                     |
| `sourceAttribution` | Array of strings | Data source confirming deceased status.                                   | `["Probate"]`                            |

<br />

#### `customerProfile` fields

| Field            | Type   | Description                                            | Example        |
| :--------------- | :----- | :----------------------------------------------------- | :------------- |
| `userId`         | String | Socure-assigned user identifier for the individual.    | `"u-1a2b3c4d"` |
| `customerUserId` | String | Your own user identifier submitted for the individual. | `"cust-98765"` |

***

<br />

## Apply routing logic

Use `decision` and `reasonCodes` to drive workflow outcomes:

* **Refer** if reason code `R907` or `R909` is returned
* **Accept** if neither is present
* **Fail** if inputs are invalid or cannot be resolved

<br />

## Best practices for integration and maintenance

* Validate API inputs against the expected schema.
* Use sandbox mode and known test identities during QA.
* Monitor `reasonCodes` and `sourceAttribution` for transparency and auditability.
* Use `decision`, `tags`, and review routing to drive operational workflows.
* Log and store evaluation payloads and responses for compliance and dispute resolution.

***

## Validation checklist

### Test coverage

<HTMLBlock>{`
<div class="strike-through-checklist-container">
  <div class="strike-through-checkbox-container">
    <input class="strike-through-checkbox" type="checkbox" /><span>Known good identities → <code>ACCEPT</code></span>
  </div>
  <div class="strike-through-checkbox-container">
    <input class="strike-through-checkbox" type="checkbox" /><span>Bad/mismatched identities → <code>REJECT</code> or <code>REVIEW</code></span>
  </div>
  <div class="strike-through-checkbox-container">
    <input class="strike-through-checkbox" type="checkbox" /><span>Edge cases logged + reviewed</span>
  </div>
</div>
`}</HTMLBlock>

### Schema and error handling

<HTMLBlock>{`
<div class="strike-through-checklist-container">
  <div class="strike-through-checkbox-container">
    <input class="strike-through-checkbox" type="checkbox" /><span>Fields match schema across environments</span>
  </div>
  <div class="strike-through-checkbox-container">
    <input class="strike-through-checkbox" type="checkbox" /><span>Errors are structured and retryable</span>
  </div>
  <div class="strike-through-checkbox-container">
    <input class="strike-through-checkbox" type="checkbox" /><span>Use exponential fallback with jitter for resubmissions</span>
  </div>
</div>
`}</HTMLBlock>

### Logging and observability

<HTMLBlock>{`
<div class="strike-through-checklist-container">
  <div class="strike-through-checkbox-container">
    <input class="strike-through-checkbox" type="checkbox" /><span>Log full request/response</span>
  </div>
  <div class="strike-through-checkbox-container">
    <input class="strike-through-checkbox" type="checkbox" /><span>Include correlation IDs</span>
  </div>
  <div class="strike-through-checkbox-container">
    <input class="strike-through-checkbox" type="checkbox" /><span>Redact secrets from logs</span>
  </div>
</div>
`}</HTMLBlock>

### Exception routing

<HTMLBlock>{`
<div class="strike-through-checklist-container">
  <div class="strike-through-checkbox-container">
    <input class="strike-through-checkbox" type="checkbox" /><span>Escalation paths defined for <code>REVIEW</code></span>
  </div>
  <div class="strike-through-checkbox-container">
    <input class="strike-through-checkbox" type="checkbox" /><span>Support team has access to logs + scores</span>
  </div>
</div>
`}</HTMLBlock>

# Sibling pages

* [Set up Deceased Check](https://help.socure.com/riskos/docs/deceased-check-riskos-setup.md)
* [Deceased Check FAQs](https://help.socure.com/riskos/docs/deceased-check-faqs.md)