How would you define the success of Incode's identity verification API for financial institutions?

Introduction

Defining the success of Incode's identity verification API for financial institutions requires a comprehensive approach that considers multiple stakeholders and metrics. To address this product success metrics challenge effectively, I'll follow a structured framework covering core metrics, supporting indicators, and risk factors while considering all key stakeholders.

Step 1

Product Context

Incode's identity verification API is a crucial tool for financial institutions to verify customer identities securely and efficiently. This API integrates into the onboarding process of banks, credit unions, and other financial services providers.

Key stakeholders include:

1. Financial institutions (primary customers)
2. End-users (bank customers)
3. Regulatory bodies
4. Incode's product and engineering teams

The typical user flow involves:

1. User initiates account opening or high-risk transaction
2. Financial institution calls Incode's API
3. User provides required identification (e.g., photo ID, selfie)
4. API processes and verifies the information
5. Results returned to the financial institution

This product aligns with Incode's strategy of providing secure, AI-powered identity verification solutions. It competes with similar offerings from companies like Onfido and Jumio, differentiating through advanced AI capabilities and seamless integration.

The product is in the growth stage, with established market presence but significant room for expansion and feature enhancement.