> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lendflow.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Ekata KYC

## Ekata KYC

Ekata KYC evaluates an individual's identity information through four separate inquiries. Lendflow combines the available results so your team can review identity risk, address risk, and phone validity or use those values in Data Orchestration.

The **Ekata KYC** block is available for individual entities in the **KYC** category of Workflow Builder and Data Orchestration.

<Warning>
  Ekata is a bring-your-own-credentials service. Your organization must connect active Ekata credentials before the service can run.
</Warning>

## Available inquiries

| Inquiry | Required data | What it evaluates | Result used by Data Orchestration |
| - | - | - | - |
| **Account Opening** | Full name, email, telephone, and complete personal address | Correlation among the applicant's name, email, phone, and personal address. | Identity risk score from 0 to 500. |
| **Transaction Risk** | Full name, email, telephone, business legal name, and complete business address | Correlation among the applicant, business, and business-address information. | Identity risk score from 0 to 500. |
| **Address Risk** | Complete personal address | Validity and risk of the applicant's personal address. | Address risk score from 0 to 1. |
| **Phone Intelligence** | Telephone and personal-address country | Validity and characteristics of the applicant's telephone number. | Valid or invalid boolean exposed as **Phone Risk**. |

Lendflow sends these inquiries concurrently. An inquiry with insufficient or invalid inputs is skipped, so a completed Ekata result may contain only some of the four response objects.

## Requirements

Requirements differ by inquiry.

### Account Opening

| Application field | Requirement | Notes |
| - | - | - |
| Primary owner's first and last name | Required | Uses the primary owner's identity record. |
| Primary owner's email | Required | Must be a valid email address. |
| Primary owner's telephone | Required | Must be a valid telephone number. |
| Primary owner's street address, city, state, ZIP code, and country | Required | Uses the primary owner's personal address. |
| Primary owner's address line 2 | Optional | Additional personal-address information. |

### Transaction Risk

| Application field | Requirement | Notes |
| - | - | - |
| Primary owner's first and last name | Required | Uses the primary owner's identity record. |
| Primary owner's email | Required | Must be a valid email address. |
| Primary owner's telephone | Required | Must be a valid telephone number. |
| Business legal name | Required | Uses the legal name on the application. |
| Business street address, city, state, ZIP code, and country | Required | Uses the business address. |
| Business address line 2 | Optional | Additional business-address information. |

### Address Risk

| Application field | Requirement | Notes |
| - | - | - |
| Primary owner's street address, city, state, ZIP code, and country | Required | Uses the primary owner's personal address. |
| Primary owner's address line 2 | Optional | Additional personal-address information. |

### Phone Intelligence

| Application field | Requirement | Notes |
| - | - | - |
| Primary owner's telephone | Required | Must be a valid telephone number. |
| Primary owner's address country | Required | Uses the country from the primary owner's personal address. |

Ekata does not currently receive the applicant's IP address from Lendflow.

If one inquiry lacks valid inputs, Lendflow can still run the other valid inquiries. The service fails as a whole only when every attempted inquiry fails.

## Configure Ekata KYC in Data Orchestration

1. In the Lendflow Dashboard, open **Builders > Data Orchestration**.
2. Create or edit a template.
3. Add **Ekata KYC** from the **KYC** service category.
4. Select the Ekata attributes the template should evaluate.
5. Configure the applicable conditions and connect each outcome to the next block.
6. Save and publish the template.

The result attributes trigger Ekata when current prerequisite data is unavailable. Because inquiries can be skipped independently, configure conditions to handle missing attributes when the corresponding application information may be incomplete.

See [Data Orchestration](/product-guides/dashboard/data-orchestration/data-orchestration) for the complete template-building workflow.

## Run Ekata KYC through the API

Data services run through a published Data Orchestration template. Your integration needs:

* An integration token with permission to access the application and run Data Orchestration.
* The application ID.
* Active Ekata credentials for the organization.
* A published template containing the **Ekata KYC** block.
* The template ID.
* The applicable workflow `stage_id` when the template is assigned to a specific stage.

1. Call [Execute Data Orchestration](/api-reference/data-orchestration/execute-data-orchestration) for the application.
2. Include `template_id` and `application_id`. Include `stage_id` when applicable.
3. Confirm that the response contains `data.executed: true`.
4. Monitor the asynchronous run with [List Data Orchestration Logs](/api-reference/data-orchestration/list-data-orchestration-logs) and [Get Data Orchestration Log](/api-reference/data-orchestration/get-data-orchestration-log).
5. Retrieve the application's enrichment data after the service finishes to review the available Ekata inquiry responses.

An accepted execution response means the run was scheduled. It does not mean Ekata has finished processing.

## What the service returns

| Response object | Meaning |
| - | - |
| `account_opening` | Identity risk and correlation results for name, email, phone, and personal address. |
| `transaction_risk` | Identity risk and correlation results that also use the business and business address. |
| `address_risk` | Address validity, location, and risk information. |
| `phone_risk` | Phone validity, carrier, line type, activity, and risk information. |

A representative combined response has this shape:

```json theme={"system"}
{
  "account_opening": {
    "identity_risk_score": 412
  },
  "transaction_risk": {
    "identity_risk_score": 389
  },
  "address_risk": {
    "address_risk_score": 0.08,
    "validity_level": "valid"
  },
  "phone_risk": {
    "is_valid": true,
    "line_type": "mobile"
  }
}
```

Do not apply one score scale to every result:

| Result | Type or range | Interpretation |
| - | - | - |
| Account Opening identity risk score | Number from 0 to 500 | Higher and lower values must be interpreted according to your organization's Ekata policy. Lendflow does not impose a pass threshold. |
| Transaction Risk identity risk score | Number from 0 to 500 | Configure the threshold appropriate for your underwriting rules. |
| Address risk score | Decimal from 0 to 1 | This is not a 0-to-500 identity risk score. |
| Phone validity | Boolean | Indicates whether Ekata considers the telephone number valid. |

If an inquiry is absent, confirm that the application contained its required information. A missing inquiry is different from an inquiry that returned a negative result.

### Response attributes

| Attribute | Type | Meaning |
| - | - | - |
| `account_opening` | Object | Contains the Account Opening identity and correlation result. |
| `account_opening.identity_risk_score` | Number | Account Opening identity risk score from 0 to 500. |
| `transaction_risk` | Object | Contains the Transaction Risk identity and correlation result. |
| `transaction_risk.identity_risk_score` | Number | Transaction Risk identity risk score from 0 to 500. |
| `address_risk` | Object | Contains address validity and risk information. |
| `address_risk.address_risk_score` | Number | Address risk score from 0 to 1. |
| `address_risk.validity_level` | String | Ekata's classification of the submitted address's validity. |
| `phone_risk` | Object | Contains phone validity, carrier, line-type, and activity information. |
| `phone_risk.is_valid` | Boolean | Indicates whether Ekata considers the telephone number valid. |
| `phone_risk.line_type` | String | Classification such as mobile, landline, fixed VoIP, or another supported phone type. |

Additional fields can include name, email, phone, and address correlation values; warnings; carrier information; and phone popularity, velocity, or volatility. Review the object containing the field to determine which inquiry produced it.

## FAQ

<AccordionGroup>
  <Accordion title="Why is Ekata unavailable for my organization?">
    Ekata requires active credentials supplied by your organization. Confirm that Ekata is connected under your organization's data-provider settings.
  </Accordion>

  <Accordion title="Why is one Ekata result missing?">
    Each inquiry validates its own inputs. Lendflow skips an inquiry when the required personal, business, address, email, or phone information is unavailable or invalid.
  </Accordion>

  <Accordion title="Does Ekata use one score range for every inquiry?">
    No. Account Opening and Transaction Risk use 0-to-500 identity risk scores, Address Risk uses a 0-to-1 decimal, and Phone Risk is a boolean validity result.
  </Accordion>

  <Accordion title="Does Lendflow automatically pass or fail an application from an Ekata score?">
    No. Configure your organization's score thresholds and outcomes in Data Orchestration.
  </Accordion>

  <Accordion title="Does data.executed true mean Ekata has finished?">
    No. It means Data Orchestration accepted and scheduled the run. Monitor the orchestration log for completion.
  </Accordion>
</AccordionGroup>