docs(kyb): add data and document collection requirements snippet

[pengying]

Summary

• New snippet mintlify/snippets/kyc/kyb-data-requirements.mdx documenting exactly what Grid collects to KYB a business customer, sourced from compliance:
  • Business identifying information (legal name, DBA, principal address, countries of operation, tax/registration ID)
  • Ownership and control structure — fields collected for each controlling person and each ≥25% owner, with US-vs-non-US ID rules
  • Required documents — formation docs, ownership chart, proof of address dated within 3 months, tax ID, plus the US-UBO non-documentary verification carve-out
• Embedded the snippet at the top of the KYB tab in snippets/kyc/kyc-unregulated.mdx so developers see what they'll need before walking through the steps. The snippet is reusable if we want to surface it elsewhere (regulated platforms reference, dedicated page, etc.).

Test plan

• make build passes
• mint openapi-check passes
• Spot-check the KYB tab on the Configuring Customers page renders the new section between the intro Note and the Steps

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
grid-flow-builder	Ready	Preview, Comment	May 29, 2026 1:31am

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
Grid	🟢 Ready	View Preview	May 29, 2026, 1:06 AM

[pengying]

• docs(kyb): add data and document collection requirements snippet #530 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Greptile Summary

This PR adds a new kyb-data-requirements.mdx snippet that enumerates the business information, ownership/control structure details, and supporting documents required before KYB onboarding completes, then embeds it in the KYB tab of the unregulated-platform onboarding guide.

• New snippet (kyb-data-requirements.mdx): Covers three sections — business identifying information, ownership and control structure (with individual ID requirements split by U.S./non-U.S. residency), and a required-documents checklist. A <Note> clarifies that U.S. beneficial owners are verified non-documentarily.
• kyc-unregulated.mdx change: Adds an import statement and an inline <KybDataRequirements /> call immediately before the KYB <Steps> block, so the data requirements appear in context before the step-by-step instructions.

Confidence Score: 3/5

The prose change is small and correctly placed, but the new snippet contains a factual error about beneficial ownership collection criteria that could mislead implementers into under-collecting required data.

The ownership/control section joins the control prong and the 25%+ ownership prong with 'and', implying both must be true simultaneously for an individual to fall in scope. Under standard CDD rules these are independent — a CEO with no equity stake and a silent 40% owner must each be collected regardless of whether they meet the other criterion. A reader who follows this documentation literally could produce a non-compliant onboarding flow by omitting control-only or ownership-only individuals.

mintlify/snippets/kyc/kyb-data-requirements.mdx — specifically the 'Ownership and control structure' section and its use of 'and' to combine the two collection triggers.

Important Files Changed

Filename	Overview
mintlify/snippets/kyc/kyb-data-requirements.mdx	New snippet listing KYB data and document requirements; the ownership/control structure section incorrectly links the control prong and the 25%+ ownership prong with 'and' instead of treating them as independent criteria.
mintlify/snippets/kyc/kyc-unregulated.mdx	Adds import and inline inclusion of the new KybDataRequirements snippet inside the KYB tab; mechanical change with no logic issues.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[KYB Tab in kyc-unregulated.mdx] --> B[KybDataRequirements snippet]
    B --> C[Business Identifying Info\nlegal name, DBA, address, tax ID]
    B --> D[Ownership & Control Structure]
    D --> D1[Control: significant responsibility\nto manage/direct entity]
    D --> D2[Ownership: 25%+ equity\ndirectly or indirectly]
    D --> D3[Per-individual fields\nname, DOB, address, ID number]
    D3 --> D3a[U.S. persons: SSN or ITIN]
    D3 --> D3b[Non-U.S. persons: ITIN / passport\n/ alien card / gov ID]
    B --> E[Required Documents\nformation docs, ownership chart,\nproof of address, tax ID docs,\nnon-U.S. passport + extra ID]
    A --> F[Steps: Create Business Customer\nPOST /customers]
    A --> G[Steps: Register Beneficial Owners\nPOST /beneficial-owners]
    A --> H[Steps: Upload Documents\nPOST /documents]
    A --> I[Steps: Submit for Verification\nPOST /verifications]

Loading

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
mintlify/snippets/kyc/kyb-data-requirements.mdx:13-16
**"And" conjunction misrepresents the two-prong beneficial ownership rule**

The bullet list connects the control prong and the ownership prong with `and`, implying an individual must satisfy both simultaneously. Under standard CDD/AML beneficial-ownership rules (e.g., FinCEN's CDD Rule), these are independent criteria: a control person (e.g., a CEO with 0 % equity) must be identified even if they own less than 25%, and a 25 %+ passive owner must be collected even if they hold no management role. As written, a reader could conclude that a CEO with no ownership stake — or a silent 40 % equity holder — falls outside the collection scope, which may lead to a non-compliant onboarding flow.

_{Reviews (1): Last reviewed commit: "docs(kyb): add data and document collect..." | Re-trigger Greptile}

[github-actions]

✱ Stainless preview builds for grid

This PR will update the grid SDKs with the following commit messages.

cli

chore(internal): regenerate SDK with no functional changes

csharp

docs(api): add KYB requirements documentation to verification submit

go

docs(api): add KYB documentation to verification Submit method

kotlin

docs(api): add KYB requirements documentation to verification submit

openapi

docs(api): expand KYB requirements in verification endpoint

php

docs(api): expand KYB requirements documentation in verifications submit method

python

docs(api): add KYB collection requirements to verifications create

ruby

docs(api): add KYB requirements documentation to verifications submit method

typescript

docs(api): add KYB requirements to verifications submit method

✅ grid-typescript studio · code

Your SDK build had at least one note diagnostic.
generate ✅ → build ✅ → lint ✅ → test ✅

npm install https://pkg.stainless.com/s/grid-typescript/8cac5e8f3d2263b69324f0814a83cd7a9fb27907/dist.tar.gz

✅ grid-openapi studio · code

Your SDK build had at least one note diagnostic.
generate ✅

✅ grid-ruby studio · code

Your SDK build had at least one note diagnostic.
generate ✅ → build ✅ → lint ✅ → test ✅

✅ grid-kotlin studio · code

Your SDK build had at least one note diagnostic.
generate ✅ → build ✅ → lint ✅ → test ✅

⚠️ grid-python studio · code

Your SDK build had a failure in the lint CI job, which is a regression from the base state.
generate ✅ → build ✅ → lint ❗ → test ❗

pip install https://pkg.stainless.com/s/grid-python/040cac3e92e69094ef6885e34fa0c2864fbbae39/grid-0.0.1-py3-none-any.whl

⚠️ grid-csharp studio · code

Your SDK build had a failure in the build CI job, which is a regression from the base state.
generate ⚠️ → build ❗ → lint ✅ → test ❗

⚠️ grid-go studio · code

Your SDK build had a failure in the lint CI job, which is a regression from the base state.
generate ✅ → build ✅ → lint ❗ → test ❗

go get github.com/stainless-sdks/grid-go@f5971bf9b434d15dc3549f545a719000ecdc2b94

✅ grid-php studio · code

Your SDK build had at least one note diagnostic.
generate ✅ → lint ✅ → test ✅

⚠️ grid-cli studio · code

Your SDK build had a failure in the test CI job, which is a regression from the base state.
generate ⚠️ → build ⏭️ → lint ⏭️ → test ❗

---

This comment is auto-generated by GitHub Actions and is automatically kept up to date as you push.
If you push custom code to the preview branch, re-run this workflow to update the comment.
Last updated: 2026-05-29 19:21:24 UTC