docs: include businessType in the business-customer create examples

[JasonCWang]

What

Adds businessType to the six POST /customers business-customer examples (kyc-regulated, kyc-unregulated, creating-customers/customers, the global-p2p and ramps configuring-customers pages, and the grid-api skill snippet).

Why

businessType is optional in the schema and appeared in none of our examples. But a receiver advertises the sender fields it requires via requiredPayerDataFields on the lookup response, and GBP receivers require this one.

That makes for a confusing failure: a business customer created by copying the docs passes KYB, shows kybStatus: APPROVED, and then fails every GBP quote with MISSING_MANDATORY_USER_INFO before the payment is attempted. It reads as a corridor or provider problem rather than a field that was never set at creation.

Setting it in the examples means the copy-paste path produces a customer that can actually pay. Existing customers can be fixed with PATCH /customers/{id}, or unblocked for a single payment by passing senderCustomerInfo on the quote.

Test Plan

Verified every edited businessInfo block still parses as JSON, and that INFORMATION is a member of the BusinessType enum in openapi/components/schemas/customers/BusinessType.yaml. No spec changes, so no rebundle needed.

🤖 Generated with Claude Code

[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 12:40am
grid-wallet-demo	Ignored	Preview	Aug 14, 2026 12:40am

[mintlify]

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

Project	Status	Preview	Updated (UTC)
Grid	🟢 Ready	View Preview	Aug 14, 2026, 12:42 AM

[greptile-apps]

Greptile Summary

Adds the optional businessInfo.businessType field to six business-customer creation examples so copied requests include sender information that GBP receivers may require.

• Uses the valid INFORMATION enum value consistently across the Grid API skill and Mintlify onboarding snippets.
• Updates documentation examples only; no API schema or generated bundle changes are needed.

Confidence Score: 5/5

The documentation-only change appears safe to merge.

The added field is placed correctly within businessInfo, and INFORMATION is accepted by the current BusinessType schema for business-customer creation.

Important Files Changed

Filename	Overview
.claude/skills/grid-api/SKILL.md	Adds guidance and a valid businessType field to the business-customer curl example.
mintlify/global-p2p/onboarding/configuring-customers.mdx	Adds the valid business classification to the Global P2P regulated-customer example.
mintlify/ramps/onboarding/configuring-customers.mdx	Adds the valid business classification to the Ramps business-customer example.
mintlify/snippets/creating-customers/customers.mdx	Updates the shared customer-creation snippet with the accepted business type.
mintlify/snippets/kyc/kyc-regulated.mdx	Adds the accepted business type to the regulated KYB example.
mintlify/snippets/kyc/kyc-unregulated.mdx	Adds the accepted business type to the unregulated KYB creation step.

_{Reviews (1): Last reviewed commit: "docs: include businessType in the busine..." | Re-trigger Greptile}