KYC, KYB & Identity · Use case

Orchestrate multiple identity vendors

Scope this use caseTalk to us

Short answer

Orchestration puts one integration and one rules engine in front of several identity vendors, so each user goes to the vendor that works best for them, with fallbacks when a check fails. It pays off once you operate in several countries or need resilience.

What this use case is

Orchestration puts one integration and one rules engine in front of several identity vendors, so each user goes to the vendor that works best for them, with fallbacks when a check fails. It pays off once you operate in several countries or need resilience.

Who builds this

Multi-country fintechs
Crypto platforms
Marketplaces
Companies consolidating vendors

What your customer sees

  1. 1One consistent onboarding flow
  2. 2Fewer failed checks
  3. 3A fallback route instead of a dead end

How KYC, KYB & Identity solves it

1

User enters the flow

User enters the flow

2

Rules decide the vendor by country, risk or document

Rules decide the vendor by country, risk or document

3

Check performed

Check performed

4

Failure or low confidence triggers a fallback vendor

Failure or low confidence triggers a fallback vendor

5

Results normalised into one format

Results normalised into one format

6

Decision and evidence stored in one audit trail

Decision and evidence stored in one audit trail

Want to have

  1. Connectors to the vendors you need
  2. Rules engine
  3. Fallback logic
  4. Normalised results
  5. Unified audit trail
  6. Reporting per vendor

Optional

  1. A/B testing between vendors
  2. Cost-based routing
  3. No-code flow builder

Design decisions

Approach

Orchestration platform
Build in-house
Vendor with built-in orchestration

speed versus control and cost.

What to put in your RFP

Connectors

  • vendors and check types

Rules

  • routing
  • fallbacks
  • testing

Data

  • normalisation
  • audit
  • reporting

Commercials

  • platform fee plus pass-through
Add these to an RFP

How to evaluate providers for this use case

  1. 1Vendors already connected
  2. 2Rule flexibility
  3. 3Reporting per vendor
  4. 4Commercial model versus direct contracts

Pitfalls

  • Adding orchestration before you need a second vendor
  • Double margins on pass-through checks
  • Losing vendor-specific features

What providers will ask you

  1. Current vendors and gaps
  2. Markets
  3. Volumes by market

Other Finlane categories that cover parts of this

This use case is solved mainly with KYC, KYB & Identity. These categories cover specific parts of it and can be tendered alongside it.

Fraud & AML Monitoring

Risk signals that feed routing decisions

RegTech & Compliance Ops

Audit and reporting

Frequently asked questions

Other KYC, KYB & Identity use cases

Onboard consumers with document + selfie

Verify ID documents plus a liveness selfie, with automated decisioning and manual review fallback.

Verify businesses and UBOs

Pull company registry data, map the ownership tree, and screen directors/UBOs against sanctions and PEP lists.

Screen for sanctions, PEP and adverse media

Run initial and ongoing screening against global watchlists with configurable match thresholds.

Scope orchestrate multiple identity vendors with KYC, KYB & Identity providers

Scope this use case