Clarify payment checkout and processor support by AnnaXWang · Pull Request #549 · kernel/docs

AnnaXWang · 2026-09-05T18:04:40Z

Summary

distinguish Stripe Link and Agentcard credential providers from merchant payment processors across the payment and Vaults guides
replace the Stripe-only checkout section with the native Stripe, Shopify, Square, Recurly, and Razorpay adapter formats and current validation caveats
remove processor compatibility as a provider-selection criterion and add Shopify and non-Stripe Agentcard examples
document the benefits and current reliability limits of KERNEL's native handoff
document safe handling of Stripe's hidden or duplicate disclosure controls and keep checkout submission one-shot

Testing

ran the Mintlify local preview
verified all five affected routes return HTTP 200
ran Mintlify broken-links successfully

Note

Low Risk
Documentation-only changes to Mintlify guides; no application code, APIs, or payment behavior changes.

Overview
This PR reframes payment docs so Stripe Link and Agentcard are credential providers, separate from the merchant's payment processor. It states that aliases can fill any standard card form (processor need not be Stripe) while native egress handoff only applies when the outgoing request matches a documented adapter.

The payments overview replaces the Stripe-only "Supported checkouts" section with Checkout and processor coverage: a table for Stripe, Shopify, Square, Recurly, and Razorpay POST formats, plus examples (e.g. Stripe Link on Shopify), validation caveats, a Why use KERNEL handoff section, and guidance to contact support for more processors. Provider choice is tied to approval lifecycle, not processor compatibility; comparison tables drop checkout-fit / Stripe-only constraint columns.

Across the browser agent, Agentcard, Stripe Link, and Vaults guides, wording shifts from "supported checkout/substitution" to recognized processor requests and native handoff. Prerequisites now require checkouts that match adapter coverage. Purchase verification is described as processor-agnostic (trusted order backend first). Checkout submission is one-shot (no retries on timeout or indeterminate results). Stripe agent-disclosure checkboxes get guidance for hidden/duplicate responsive controls (visible label, native click(), verify checked).

Actor/responsibility tables and the payments flow diagram now distinguish credential provider from merchant processor.

^{Reviewed by Cursor Bugbot for commit b6bfc17. Bugbot is set up for automated code reviews on this repo. Configure here.}

mintlify · 2026-09-05T18:04:44Z

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

Project	Status	Preview	Updated
Kernel	🟢 Ready	View Preview	Sep 5, 2026, 6:05 PM

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

AnnaXWang · 2026-09-05T18:45:43Z

   or an action is present, stop and ask me to resolve wallet setup outside this
   agent. do not create another wallet or print, return, or open an action url.
 3. create a KERNEL browser with `user-12345` attached as a vault, then navigate
-   it to https://buy.stripe.com/28E5kw7DtgKXdLqgiY53O00.


I want to keep https://buy.stripe.com/28E5kw7DtgKXdLqgiY53O00 since that's what our testing was done on

AnnaXWang · 2026-09-05T18:46:10Z

 offers **I am an AI agent acting on behalf of someone else**, select that option.
-don't bypass the disclosure or replace the page's normal submission with a raw
-processor request.
+stripe can render hidden or duplicate copies of its disclosure control for


I think this is mentioned too many times in our docs now, find the single best place to include this information, do not mention more than 2x

AnnaXWang · 2026-09-05T18:46:22Z


-Submit the checkout once. If the payment request pauses for user approval,
-wait for the controller to finish that approval. Do not retry payment.
+Stripe may render hidden or duplicate disclosure controls. Target the visible


this seems like extraneous because we already mention it before

AnnaXWang · 2026-09-05T18:47:26Z

+<span className="kernel-brand-name">KERNEL</span> currently has adapters for
+request formats used by stripe, shopify, square, recurly, and razorpay.
+
+agentcard's direct SDK recognizes additional processors, but


I would say "kernel's native handoff aims to support the same processors that are supported by agentcard's direct SDK. email support@kernel.sh if you need
another processor so we can prioritize its adapter and validate a real checkout."

AnnaXWang · 2026-09-05T18:48:07Z

+different request layouts, and unrecognized processor endpoints pass through
+without native handoff.
+
+agentcard's direct SDK recognizes additional processors that


I would say "kernel's native handoff aims to support the same processors that are supported by agentcard's direct SDK. email support@kernel.sh if you need
another processor so we can prioritize its adapter and validate a real checkout."

cursor

Stale comment

Risk assessment: Very Low

Verdict: Re-evaluated after the latest push. Risk did not increase. Previous approval stands (not re-approving).

This PR still only edits Mintlify documentation (*.mdx). The full diff touches five pages:

browsers/enable-payments-in-browser-agent.mdx

integrations/payments/overview.mdx

integrations/payments/agentcard.mdx

integrations/payments/stripe-link.mdx

vaults.mdx

No application code, config, CI, navigation, or infrastructure files change. There is no CODEOWNERS file, so no required codeowner review applies.

The latest commit (b6bfc17) only rearranges existing docs copy: it shortens example agent prompts, restores a Stripe payment-link URL in an example, and softens adapter-coverage wording. That does not expand blast radius or add production logic.

Across the PR, the edits:

Distinguish credential providers (Stripe Link, Agentcard) from merchant processors

Document native processor request formats (Stripe, Shopify, Square, Recurly, Razorpay) and keep pass-through caveats

Document Stripe disclosure-control handling and one-shot checkout submission in the guide body

Example prompt snippets live in product docs, not in deployed model-instruction files. Blast radius is limited to the docs site. No production logic, auth, billing code, or shared services are modified.

Risk level: Very Low
Action: No approval change. Existing approval remains.

_{Sent by Cursor Automation: Assign PR reviewers}

cursor

Risk assessment: Very Low

Verdict: Re-evaluated the current HEAD (b6bfc17). Risk did not increase. Previous approval stands (not re-approving).

Assessed from the file diff only (5 files, +150 / −59). Every changed path is Mintlify documentation (*.mdx):

browsers/enable-payments-in-browser-agent.mdx
integrations/payments/overview.mdx
integrations/payments/agentcard.mdx
integrations/payments/stripe-link.mdx
vaults.mdx

No application code, config, CI, navigation (docs.json), or infrastructure files change. There is no CODEOWNERS file, so no required codeowner review applies.

The edits rewrite payment-guide copy: they distinguish credential providers from merchant processors, document native adapter request formats, and add checkout-submission / disclosure guidance in the docs body. Example agent prompts live in product guides, not in deployed model-instruction files.

The post-approval commit (65a3f6a → b6bfc17) only rearranges that same docs copy (shorter example prompts, restored Stripe payment-link URL, softer adapter-coverage wording). That does not expand blast radius or add production logic.

Risk level: Very Low
Action: No approval change. Existing approval remains.

_{Sent by Cursor Automation: Assign PR reviewers}

cursor

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

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

Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.

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

cursor · 2026-09-05T20:47:30Z

+<span className="kernel-brand-name">KERNEL</span>'s native handoff aims to
+support the same processors supported by agentcard's direct SDK. email
+[support@kernel.sh](mailto:support@kernel.sh) if you need another processor so
+we can prioritize its adapter and validate a real checkout.


Processor coverage copied across pages

Medium Severity

The credential-provider versus processor explanation, adapter list, and native-handoff support note are reproduced in full on multiple pages instead of living on the canonical checkout-and-processor-coverage section and being briefly summarized with a link. That breaks the single-source-of-truth pattern and already shows small wording drift across copies.

Additional Locations (2)

vaults.mdx#L159-L166

browsers/enable-payments-in-browser-agent.mdx#L9-L14

^{Triggered by learned rule: Single source of truth — no deep content duplication across pages}

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

rgarcia

reviewed — looks good.

Document Stripe disclosure controls

31ed3f7

mintlify Bot deployed to staging September 5, 2026 18:05 View deployment

Clarify payment processor coverage

65a3f6a

AnnaXWang changed the title ~~Document Stripe disclosure checkbox handling~~ Clarify payment checkout and processor support Sep 5, 2026

mintlify Bot deployed to staging September 5, 2026 18:35 View deployment

cursor Bot approved these changes Sep 5, 2026 •

edited

Loading

View reviewed changes

AnnaXWang commented Sep 5, 2026

View reviewed changes

Address payment docs review

b6bfc17

mintlify Bot deployed to staging September 5, 2026 18:52 View deployment

cursor Bot reviewed Sep 5, 2026

View reviewed changes

AnnaXWang marked this pull request as ready for review September 5, 2026 20:42

AnnaXWang requested review from hiroTamada and rgarcia September 5, 2026 20:42

cursor Bot reviewed Sep 5, 2026

View reviewed changes

rgarcia approved these changes Sep 5, 2026

View reviewed changes

AnnaXWang merged commit f98baf8 into main Sep 5, 2026
4 checks passed

AnnaXWang deleted the hypeship/document-stripe-disclosure branch September 5, 2026 21:09

Navigation Menu

Uh oh!

Clarify payment checkout and processor support - #549

Clarify payment checkout and processor support#549
AnnaXWang merged 3 commits into
mainfrom
hypeship/document-stripe-disclosure

AnnaXWang commented Sep 5, 2026 •

edited by cursor Bot

Loading

Uh oh!

mintlify Bot commented Sep 5, 2026 •

edited

Loading

Uh oh!

AnnaXWang Sep 5, 2026

Uh oh!

AnnaXWang Sep 5, 2026

Uh oh!

AnnaXWang Sep 5, 2026

Uh oh!

AnnaXWang Sep 5, 2026

Uh oh!

AnnaXWang Sep 5, 2026

Uh oh!

cursor Bot left a comment •

edited

Loading

Uh oh!

cursor Bot left a comment

Uh oh!

cursor Bot left a comment

Uh oh!

cursor Bot Sep 5, 2026

Uh oh!

rgarcia left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

AnnaXWang commented Sep 5, 2026 • edited by cursor Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Testing

Uh oh!

mintlify Bot commented Sep 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

AnnaXWang Sep 5, 2026

Choose a reason for hiding this comment

Uh oh!

AnnaXWang Sep 5, 2026

Choose a reason for hiding this comment

Uh oh!

AnnaXWang Sep 5, 2026

Choose a reason for hiding this comment

Uh oh!

AnnaXWang Sep 5, 2026

Choose a reason for hiding this comment

Uh oh!

AnnaXWang Sep 5, 2026

Choose a reason for hiding this comment

Uh oh!

cursor Bot left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Risk assessment: Very Low

Uh oh!

cursor Bot left a comment

Choose a reason for hiding this comment

Risk assessment: Very Low

Uh oh!

cursor Bot left a comment

Choose a reason for hiding this comment

Uh oh!

cursor Bot Sep 5, 2026

Choose a reason for hiding this comment

Processor coverage copied across pages

Uh oh!

rgarcia left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

AnnaXWang commented Sep 5, 2026 •

edited by cursor Bot

Loading

mintlify Bot commented Sep 5, 2026 •

edited

Loading

cursor Bot left a comment •

edited

Loading