docs: document endUserTermsConsent on the Disclosures page

[ls-bolt]

Summary

Documents endUserTermsConsent on the Disclosures page. Unregulated platforms must record each customer's End User Terms acceptance — for both INDIVIDUAL and BUSINESS customers — or Grid won't provision that customer's internal accounts, and customer-scoped transactions are rejected with 403 END_USER_TERMS_NOT_ACCEPTED.

Disclosures already covered the legal side of this requirement (embed the terms, require affirmative acceptance, send evidence of your consent flow) but stopped short of how to record an acceptance through the API. That left the integration details in the OpenAPI schema descriptions only.

Approach

Everything lands on the existing Disclosures page, next to the consent-flow requirements it already documents, so an integrator reads the obligation and the API call in one place. Added there, as a Record each acceptance section:

• The endUserTermsConsent object on POST /customers, with a field-by-field table
• The same field on PATCH /customers/{customerId}, so consent can be recorded for customers that already exist — the path for integrations that predate the field
• Reading the field back on GET /customers/{customerId} to find customers still missing consent
• That regulated platforms rely on their own end user agreements and don't send it

The page keeps pointing integrators at the hosted terms URL they must embed; it deliberately does not document GET /customers/end-user-terms, since the terms are embedded once rather than fetched per customer. The termsVersion row notes that Grid rejects an unrecognized version with 400 END_USER_TERMS_VERSION_NOT_FOUND.

The two paragraphs Disclosures already had on this are replaced by the fuller treatment rather than duplicated.

Changes: 2 files

• mintlify/payouts-and-b2b/onboarding/disclosures.mdx — the Record each acceptance section and the consequences of missing consent
• mintlify/snippets/internal-accounts.mdx — warn that a customer's internal accounts aren't provisioned until consent is recorded, linking to Disclosures

Test plan

• mintlify dev (CLI 4.2.284, Node 20) — Disclosures renders and reads straight from presenting the terms into recording acceptance; the Internal Accounts warning renders and its link resolves to Disclosures
• markdownlint — no new findings versus origin/main on either file
• mintlify broken-links — no new broken links in the touched files

Reply with a comment (e.g. LGTM) to approve — emoji reactions don't notify me on GitHub.

[mintlify]

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

Project	Status	Preview	Updated (UTC)
Grid	🟢 Ready	View Preview	Aug 14, 2026, 5:22 PM

[vercel]

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

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
grid-flow-builder	Ignored	Preview	Aug 14, 2026 7:55pm
grid-wallet-demo	Ignored	Preview	Aug 14, 2026 7:55pm

[lightspark-bot]

• docs: document endUserTermsConsent on the Disclosures page #837 👈 (View in Graphite)
• main

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

[greptile-apps]

Greptile Summary

Documents how unregulated platforms record End User Terms acceptance and the consequences of missing consent.

• Adds POST and PATCH examples with a field-by-field consent reference.
• Explains how to identify customers without recorded consent.
• Adds a shared internal-accounts warning linking readers to the disclosures guide.

Confidence Score: 5/5

The documentation-only change appears safe to merge.

The documented consent fields, accepted values, update requirements, response behavior, and error codes align with the repository’s API contracts, and no actionable defect remains.

Important Files Changed

Filename	Overview
mintlify/payouts-and-b2b/onboarding/disclosures.mdx	Adds consent-recording examples and behavior that align with the customer request, response, and error schemas.
mintlify/snippets/internal-accounts.mdx	Adds an explicitly scoped warning about consent-gated account provisioning and transactions.

_{Reviews (1): Last reviewed commit: "docs: move endUserTermsConsent onto the ..." | Re-trigger Greptile}