Document optional payment provider clients

[rgarcia]

summary

• append one bring-your-own OAuth client section to each existing provider guide, with protected-file CLI examples for config registration and wallet creation. leave existing provider onboarding unchanged.
• keep KERNEL-managed credentials as the recommendation and briefly explain link backend OAuth responsibilities.
• add shared configuration semantics and targeted browser-guide cross-links and mode/recovery notes. no payments overview, cutover guidance, new pages, or navigation changes.

validation

• mint validate --telemetry=false passed.
• mint broken-links --telemetry=false passed.
• shell syntax checked for bash examples in all four changed pages.
• assertions verify each provider page has exactly one appended diff hunk, the payments overview is unchanged, and cutover text is absent.
• CLI flags and request semantics checked against command implementation and API schemas. no live credentials or provider calls used.

release dependency

Publish after the provider-configuration API and CLI commands are available. The examples assume vault-provider-configs, --provider-config-name, and --tokens-file support.

[mintlify]

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

Project	Status	Preview	Updated
Kernel	🟢 Ready	View Preview	Sep 11, 2026, 2:21 PM

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

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 76efa4d. Configure here.}

[cursor]

Stale comment

Risk assessment: Very Low

Decision: Keep existing approval. Risk did not increase after the latest push. Not re-approving.

Re-evaluation (synchronize after prior approval)

This automation previously approved 76efa4d. The follow-up commit f488773 only reformats existing caveats in integrations/payments/stripe-link.mdx and vaults.mdx from dense prose into labeled bullets. Same facts, no new pages, no new commands, no config or code.

Scope (from the current diff vs main)

• 5 files, all existing Mintlify .mdx pages (+153 / -23)
• No docs.json, redirects, navigation, CI, workflows, or other config changes
• No application code, infrastructure, schema, or auth implementation changes
• No CODEOWNERS file in this repo, so codeowner review is not required

Why Very Low

Documentation-only: optional payment-provider-client guidance on existing pages (accordions, CLI examples, lifecycle/status notes). Blast radius is published docs copy. No production logic, shared service, or infra surface.

Residual notes (not risk-elevating)

• Examples document CLI/API flags that may not be universally available yet (vault-provider-configs, --provider-config-name, --tokens-file). That is a docs-release timing concern, not runtime risk in this repo.
• Credential-handling guidance stays documentation; it does not change how the platform stores or enforces secrets.

Approval stands. No revoke.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Risk assessment: Very Low

Decision: Keep existing approval. Risk did not increase after the latest push. Not re-approving.

Re-evaluation (synchronize after prior approval)

This automation previously approved 76efa4d. The latest commit 6182ec0 is still documentation-only. Compared with the previously assessed tip (f488773), it:

• Moves optional bring-your-own OAuth client guidance from Before you start accordions into appended sections on the existing Link and Agentcard pages
• Reverts integrations/payments/overview.mdx so that file is unchanged vs main
• Removes cutover/recovery guidance that had been added to the default onboarding path
• Updates heading anchors and a few mode/recovery notes

No new pages, no config/code, and the changed surface vs main is smaller than the last assessment.

Scope (from the current diff vs main)

• 4 files, all existing Mintlify .mdx pages (+98 / -6)
  • browsers/enable-payments-in-browser-agent.mdx
  • integrations/payments/agentcard.mdx
  • integrations/payments/stripe-link.mdx
  • vaults.mdx
• No docs.json, redirects, navigation, CI, workflows, or other config changes
• No application code, infrastructure, schema, or auth implementation changes
• No CODEOWNERS file in this repo, so codeowner review is not required

Why Very Low

Documentation-only edits to existing product docs: appended CLI examples, provider-config semantics, and cross-links. Blast radius is published docs copy. No production logic, shared service, or infra surface.

Residual notes (not risk-elevating)

• Examples document CLI/API flags that may not be universally available yet (vault-provider-configs, --provider-config-name, --tokens-file). That is a docs-release timing concern, not runtime risk in this repo.
• Credential-handling guidance stays documentation; it does not change how the platform stores or enforces secrets.

Approval stands. No revoke.

  

_{Sent by Cursor Automation: Assign PR reviewers}