Recipe 1 - Business Customer Onboarding Verification

Use Case
Verify new business customers during onboarding to reduce fraud and regulatory risk, and identify pay risk.

Who Uses This
Banks; Fintechs; Payments platforms; Marketplaces; Lending platforms

Implementation Flow

1. Collect business information from onboarding form (validate inputs; avoid placeholders).
2. Call Advanced Match (include showGrades=true during tuning).
3. Evaluate markaazMatchConfidenceScore and grades; consider threshold (e.g., 8.3 default).
4. Retrieve enrichment (Firmographics, Compliance, Business Health) using markaazId.
5. Run onboarding risk rules; persist markaazId for future use.

Normalize legal structure (Optional): Because legalStructure is returned as raw Markaaz data partner values, clients should leverage Markaaz’s normalization guidance to reduce false positives. Compare normalized vs normalized values, not raw API response values vs user‑selected request values). For example: LLC, Limited Liability, and Limited Liability Company all map to a single customer-side value. Contact Markaaz for further guidance on normalization for your use case.

Recommended APIs

IF markaazMatchConfidenceScore >= 9
AND companyStatus = "active"
THEN auto-approve

IF markaazMatchConfidenceScore < 8
THEN manual review

Value
Reduces onboarding fraud; improves identity verification; automates KYB workflows.

Recipe 2 - Search + Pre-fill Onboarding

Use Case
Reduce friction in signup flows by letting users select their business instead of typing everything manually.

Who Uses This
SaaS platforms; Marketplaces; Payments providers; Procurement platforms

Implementation Flow

1. User enters business name
2. Call Search (include country where possible) and display candidate businesses
3. User selects correct business
4. User may add additional business data
5. Call Advanced Match to verify with matchConfidenceScore and field grades
6. Pre-fill onboarding form with matched data (bizInfo fields)

Mismatch between client‑captured legal structure and raw partner value is common; clients should compare normalized values rather than raw strings to prevent false exceptions. Legal structure guidance can be found below in the Firmographic API response fields reference table.

Benefits
Faster onboarding; fewer typos; higher match rates.

Recipe 3 - Supplier / Vendor Risk Screening

Use Case
Evaluate the legitimacy of suppliers before onboarding them.

Who Uses This
Procurement platforms; Enterprise procurement teams; Financial institutions; B2B marketplaces

Implementation Flow

1. Supplier submits business info
2. Call Advanced Match
3. Retrieve Compliance and Business Health signals; optionally Hierarchy for ownership context
4. Evaluate risk indicators and approve/review supplier

Recommended APIs

IF companyStatus = "inactive"
OR activeInsolvency > 0
THEN reject supplier

Note: activeInsolvency is derived from the count of insolvency records; bankruptcy (Business Health) is separately sourced and may differ.

Recipe 4 - Fraud Detection During Business Onboarding

Use Case
Detect synthetic or fraudulent businesses

Who Uses This
Fintechs; Payments companies; Lending platforms; Marketplaces

Signals Used

• Low match confidence (below threshold)
• Address mismatch grades (e.g., C/F) despite name similarity
• companyStatus = inactive
• Suspicious corporate structure (unexpected parent types or missing expected hierarchy)

Implementation Flow

1. Run Advanced Match with showGrades=true
2. Retrieve enrichment signals (Compliance, Business Health, Firmographics, Hierarchy, etc.)
3. Score fraud risk with weighted rules across grades and enrichment
4. Route to manual review as needed

Recipe 5 - Business Hierarchy and Compliance Discovery

Use Case
Understand the ownership hierarchy or corporate relationships between business entities to retrieve a full compliance profile

Who Uses This
Procurement teams; Supply chain risk teams; Large enterprises

Implementation Flow

1. Match business via Advanced Match
2. Retrieve Company Hierarchy
3. Identify parent companies (parentTypeCode: Immediate, Domestic, Global, Affiliate Global)
4. Evaluate group‑level risk and verification scope using Markaaz Verification APIs for each discovered hierarchy entity (Compliance Details, Business Health, Financials Data)

Benefits
Detect hidden ownership; identify concentration risk; determine appropriate verification scope (which entities require screening).

Recipe 6 - Large Dataset Business Matching (Bulk Processing)

Use Case
Match large datasets of businesses to Markaaz identifiers.

Who Uses This
Data platforms; Enterprises with large vendor lists; Data integration teams

Implementation Flow

1. Submit match requests in controlled batches (or through your data pipeline)
2. Store markaazId for every success
3. Run enrichment in scheduled batch jobs (parallel where possible)

Performance Tips

• Parallelize independent API calls after match; asynchronous workflows for enrichment; cache results and avoid re‑matching known entities.

Recipe 7 - Person‑to‑Business Identity Verification

Use Case
Verify that a person is associated with a business.

Who Uses This
Financial institutions; KYB/KYC platforms; Fraud detection teams

Implementation Flow

1. Match business (Advanced Match → markaazId)
2. Submit person data via P2B (namesToMatch array)
3. Evaluate relationship signals against officers/contacts
4. Use thresholds configured in Enterprise Portal for name matching; keep upper threshold near 89 unless advised otherwise

Benefits
Detect impersonation; validate beneficial ownership or authorized signers.