docs: use collectData.schema as source of truth for native UI, deprecate fields

[jakubuid]

Summary

Atom Wallet QA (Slack thread) surfaced that wallets building native data-collection UI render forms from the deprecated collectData.fields array, which only lists name and date of birth — required fields like country never appear. The correct source is collectData.schema (JSON Schema: properties + top-level required + conditional anyOf groups). The docs recommended the WebView flow but never spelled this out for integrators who build native UI anyway.

This PR makes the guidance explicit across all platforms and integration types.

flowchart TD
    A[Option selected with collectData] --> B{UI approach}
    B -- "Recommended" --> C[Display collectData.url in WebView/iframe]
    C --> D[IC_COMPLETE → confirm WITHOUT collectedData]
    B -- "Native UI" --> E[Parse collectData.schema<br/>properties + required + anyOf]
    E --> F[Confirm WITH collectedData built from schema]
    B -. "Never" .-> G[❌ deprecated collectData.fields<br/>incomplete — misses country etc.]

Loading

Changes

• Shared snippet (snippets/webview-data-collection-overview.mdx, included by all 10 SDK pages — standalone + WalletKit × Kotlin/Swift/Flutter/React Native/Web): new Building Native UI Instead section — parse schema (properties, required, anyOf, validation constraints, tosConfirmed), submit via collectedData, with a <Warning> that fields is deprecated and incomplete
• All 10 SDK pages: the CollectDataAction data model now labels schema as the native-UI source of truth (url as the recommended WebView flow), with a deprecation warning for fields beneath each model — visible where devs look when their IDE autocompletes the deprecated property
• API-first guide: expanded native-form guidance (required + anyOf parsing) plus deprecation warning — the raw API response still contains fields
• Wallets overview FAQ: "Can wallets implement custom UI?" now spells out schema-as-source-of-truth and the fields deprecation
• AI-prompt pages (×4): model comments updated so generated integrations never use fields
• PSP Headless SDK (payments/psps/headless-sdk/implementation.mdx): the InformationCapture example rendered a KYC form from collectData.fields — now renders from schema with the deprecation note (headless integrations always build their own UI, so this mattered most)

No API reference changes needed — the OpenAPI specs already mark fields as deprecated: true.

🤖 Generated with Claude Code

[mintlify]

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

Project	Status	Preview	Updated (UTC)
wc-pay-docs	🟢 Ready	View Preview	Aug 26, 2026, 7:03 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[ignaciosantise]

"Build Native UI instead" appears as a section inside "Embedded Data Collection Form", and also its above "Webview message types", which looks weird in the side bar. Check in the preview link

[jakubuid]

Good catch — fixed in ba578b4. The section was rendering at the end of the shared snippet, so it landed inside "Embedded Data Collection Form" and above "WebView Message Types" on every page. Folded it into an <Accordion> instead: the guidance stays in place but no longer emits a TOC entry, so the sidebar now flows straight from "Customizing the form appearance" to "WebView Message Types".