KYCConcepts & Definitions

Key Concepts

An overview of the fundamental building blocks of the FrankieOne platform, such as Entities, Workflows, and Risk Assessments.

This guide introduces the primary building blocks of the FrankieOne platform. Understanding these core concepts is the first step toward a successful integration.

For details on specific data structures like addresses and consent, see the Key Data Objects page. For a full list of terms, visit the Glossary.

Platform Building Blocks

These are the fundamental concepts that power the FrankieOne platform. Click on any concept to learn more.

An Entity is the central object in the FrankieOne platform, representing a single customer you want to verify. All information, checks, and results are linked to an entity.

  • An Individual is an entity type representing a single person.
  • An Organization is an entity type representing a business or other non-individual entity.

A Workflow is a configurable, end-to-end process that runs a sequence of steps to verify an entity. You can design workflows to meet your specific risk and compliance requirements. A workflow is composed of steps such as KYC verifications, AML screening, IDV checks, and risk assessments.

A Service Profile provides an overview of an entity’s verification progress and risk status in the context of a specific product or service you offer. A single entity can have multiple service profiles, allowing you to apply different rules and risk policies for different products (e.g., a credit card vs. a home loan).

A Process Result is the raw, granular data returned from a single check against a third-party data source (e.g., a match for a name from a government database). A workflow step evaluates one or more process results to determine its outcome.

FrankieOne uses granular Risk metrics to calculate a customer’s risk profile. During a workflow, an entity is scored against configurable risk factors (e.g., age, location, PEP status). The cumulative score determines the entity’s overall risk level, which can trigger different actions like Enhanced Due Diligence (EDD).

An Issue is a problem raised during a workflow that requires manual review or intervention. Issues are created for significant events, such as a failed KYC check or a match on a sanctions watchlist, and provide clear guidance on the next steps.

How The Concepts Connect

A typical verification process follows this logical flow:

  1. You create an Entity representing your customer.
  2. You assign a Service Profile to the Entity for the product they are accessing.
  3. You trigger a Workflow to begin verification.
  4. The Workflow runs checks, generating Process Results from data sources.
  5. A Risk Assessment is performed based on the results.
  6. If problems occur, an Issue is created for review.

Technical Architecture

The FrankieOne API is built using the REST (Representational State Transfer) architectural style. This provides a simple, predictable, and scalable interface for interacting with all platform resources.

By adopting REST, FrankieOne ensures that its API is flexible and easy to learn. All communication is performed over secure HTTPS using standard HTTP methods (like GET, POST, PATCH) and clear, resource-oriented URLs. This unified approach allows you to interact with different parts of the platform in a consistent way, supporting robust automation and integration with your systems.