KYC / KYB (AML)¶
Documentation status
Last verified: 26 Sep 2026. Readiness uses the single rubric and status vocabulary.
Automates Know Your Customer / Know Your Business verification, biometrics, screening, and customer risk scoring for onboarding and compliance programmes.
Purpose¶
Give onboarding and compliance teams structured answers for identity, documents, biometrics, and AML screening — without embedding every identity vendor into each client application.
Users¶
| Audience | How they use it |
|---|---|
| Onboarding / compliance operations | Drive customer journeys via the banking application |
| Partner / client engineers | Call KYC / KYB HTTP APIs from a backend |
| Risk / AML analysts | Consume risk profiles and screening outcomes |
Business problem¶
Customer due diligence requires many vendor calls (ID, documents, face, sanctions/PEP, adverse media) with consistent payloads and risk outputs. MasteryHive centralises those checks behind partner-facing APIs.
Capabilities¶
| Area | What is supported |
|---|---|
| Identity checks | Individual ID verification (including aggregated ID flows) |
| Business checks | Business / KYB verification |
| Address checks | Address verification |
| Document verification | Document checks and document extraction |
| Biodata | Biodata verification |
| Biometrics | Liveness checks and face comparison (including ID-image comparison paths) |
| Sanctions / PEP screening | OpenSanctions-style finders, PEP and sanctions checker |
| Adverse media | Adverse media screening |
| Risk / report | Customer risk profile calculation and report generation |
| Regulatory XML | Covered on AML and Regulatory Reporting (PARTIAL offline goAML) |
End-to-end workflow¶
Typical integrator sequence (order owned by the calling app):
- ID and/or document checks
- Liveness + face comparison
- PEP / sanctions / adverse media
- Risk profile + report
flowchart LR
id[ID_and_docs]
bio[Biometrics]
screen[Screening]
risk[Risk_and_report]
id --> bio --> screen --> risk
Inputs¶
| Input | Notes |
|---|---|
| JSON request bodies | Per-check schemas in partner OpenAPI |
| File references | Cloud-storage HTTPS URLs for images / documents — not browser uploads to MasteryHive |
| Customer identifiers | For example userId as used by each route |
Outputs¶
| Output | Notes |
|---|---|
| Per-check verification / screening results | Vendor-backed; structure in OpenAPI |
| Risk profile / generated report | For downstream compliance UX |
| goAML XML | Not an HTTP product surface — see AML and Regulatory Reporting |
Integrations¶
| Dependency | Role |
|---|---|
| Identity / document vendors | Server-side ID, business, address, document checks |
| Screening providers | Sanctions, PEP, adverse media |
| Face / liveness models | Biometric checks |
| Banking application | Orchestrates the journey and stores durable customer state |
Production authentication and network exposure are agreed per environment. Call from your backend, not from a browser. See Auth and tenancy.
Partner OpenAPI: KYC OpenAPI. Guide: KYC / KYB API.
Readiness¶
Rated with the single readiness rubric. Reasons for each rating are on that page.
| Gate | Rating |
|---|---|
| Code | PARTIAL |
| Integration Verified | UNKNOWN |
| Ops Ready | PARTIAL |
| Security Approved | NOT MET |
| GA | NOT MET |
goAML report generation is rated separately on AML and Regulatory Reporting.
See Product readiness summary.
Limitations — what is not guaranteed¶
- Vendor uptime, match quality, and country coverage are vendor-dependent; MasteryHive does not guarantee a specific hit rate.
- The OpenSanctions download routes (
/download,/download/all) are commented out in the service code and are not mounted. They are not part of the API. - Production auth is not a universal Fraud-style JWT scheme on every KYC route — confirm gateway requirements per environment.
- goAML XML generation does not submit to NFIU and is not a complete filing product.
- Orchestration, retries across vendors, and customer UX remain the calling application’s responsibility.