KYB Onboarding Tech Stack 2026: Sumsub vs Veriff vs In-House
KYB (Know Your Business) digital goods में हर B2B payment flow के लिए compliance obligation है। KYC के विपरीत, KYB person नहीं, company verify करता है: incorporation, UBOs, sanctions, और ongoing monitoring। यह article 2026 के लिए production KYB stack walk-through है।
1. KYB engine को क्या करना चाहिए
Minimum pipeline:
async function onboardBusiness(b: BusinessApplication): Promise<KybDecision> {
await collectDocuments(b); // Cert of incorp, articles, IDs
await documentAi.extract(b.docs); // OCR + structured fields
await registryLookup(b); // Companies House, MCA India, etc.
await sanctionsScreen(b); // OFAC, EU, UN, UK
await pepCheck(b.ubos); // Political exposure
const score = riskScore(b);
if (score > 70) return { decision: 'manual_review' };
if (score > 40) return { decision: 'approved_enhanced_monitoring' };
return { decision: 'approved' };
}
हर step audit log के साथ अलग compliance checkpoint है।
2. Sumsub vs Veriff — production comparison
| Feature | Sumsub | Veriff |
|---|---|---|
| Jurisdiction coverage | 220+ | 190+ |
| KYB API | Yes (full) | Yes (limited) |
| UBO discovery | Auto + manual | Manual upload |
| OCR + Document AI | Industry-leading | Strong |
| Pricing (KYB) | $20–40/applicant | $5–15/applicant |
| Median onboarding time | 18 min | 11 min |
| Conversion (KYB completion) | 81% | 87% |
| Sanctions DB refresh | 4h | 24h |
Compliance-heavy distributors (FX, crypto) के लिए Sumsub pick है। Retail/SaaS B2B जहाँ UX coverage से ज़्यादा matter करे — Veriff।
3. Document AI — OCR + LLM extraction
KYB documents (incorporation cert, articles, IDs) PDF/JPEG में आते हैं। 2026 stack:
# Sumsub-style pipeline
from sumsub import Client
sumsub = Client(api_key=os.environ['SUMSUB_KEY'])
applicant = sumsub.applicants.create(level='kyb-business')
sumsub.applicants.add_document(
applicant_id=applicant.id,
file=open('incorporation.pdf', 'rb'),
type='COMPANY_DOC',
sub_type='CERTIFICATE'
)
# Sumsub OCR + LLM extracts: company_name, reg_number, dir_names, address
result = sumsub.applicants.get(applicant.id)
print(result.extracted_data)
Western registries पर accuracy 95–98% है। Emerging markets (LatAm, Africa) पर — 80–88%, human review चाहिए।
4. Beneficial-owner graph
UBO discovery ownership chain का recursive walk है। Company A → owns 60% B → owns 80% C के लिए, C का effective owner = 0.6 * 0.8 = 48%। Graph की तरह store करें:
CREATE TABLE ownership_edges (
parent_id UUID, -- shareholder (person या company)
child_id UUID, -- owned entity
percentage DECIMAL(5,2),
effective_date DATE,
source TEXT, -- 'registry', 'self_declared'
PRIMARY KEY (parent_id, child_id, effective_date)
);
-- Recursive UBO query
WITH RECURSIVE chain AS (
SELECT parent_id, child_id, percentage AS effective
FROM ownership_edges WHERE child_id = $target
UNION ALL
SELECT e.parent_id, c.child_id, c.effective * e.percentage / 100
FROM chain c JOIN ownership_edges e ON e.child_id = c.parent_id
)
SELECT parent_id FROM chain WHERE effective > 25;
हर verified partner पर quarterly run करें re-validation के लिए।
CTA
FoxReload hood के नीचे Sumsub use करता है और enterprise partners को <24h में KYB clear करता है। Access request करें और onboarding शुरू करें।