Overview
Verifow operates as a multi-tenant platform. Each bank or financial institution operates within its own tenant, with complete data isolation from other institutions.What Is a Tenant?
A tenant represents your organization within Verifow. All your transactions, cases, rules, reports, and users exist within your tenant boundary.Tenant Characteristics
Data Boundaries
The following data is scoped to your tenant and never shared:- Transaction screening history
- Compliance cases and notes
- Custom detection rules
- KYC applications and verification results
- KYB applications and corporate verification data
- Regulatory reports
- Audit logs
- User accounts and roles
KYC Provider Configuration
Each tenant independently controls how customer identity verification is performed.Provider Modes
Configuring BYOL
BANK_ADMIN users can configure BYOL from Dashboard → Settings → KYC Provider:
- Select BYOL from-he mode dropdown.
- Enter your prov-er details:
- Provider Name — e.g., “YourProviderName”
- Base URL —-our provider’s API root
- API Key / App ID -Authentication credentials
- Endpoints — Paths-or NIN, BVN, and Liveness checks
- R-ponse Mapping — JSON paths to extract first/last names
- Match Confidence — Threshold for name match success (0–100)
- Save — new verifications immediately use your provider.
Tenant.kycProviderConfig and is never exposed to other tenants.
KYC Trust Mode
Controls how KYC status is resolved during transaction screening:
Managed via
PATCH /api/v1/tenants/me with kycTrustMode.
BYOL Fallback Mode
Defines behavior when the BYOL provider is unavailable:
Managed via
PATCH /api/v1/tenants/me with byolFallbackMode.
Note: Tenant-level configuration changes for engine weights or feature flags are handled by platform administrators. Contact your account manager if you need adjustments beyond KYC provider selection.