Clarify the browser agent payments guide

[AnnaXWang]

Summary

• Link to the wallet overview for provider choice instead of repeating its comparison, define the controller/agent/user roles, and clarify where real card values enter the browser.
• Separate one-time wallet setup from the per-purchase flow; create the browser before purchase verification and keep each provider's checkout steps in its own tab.
• Consolidate shared safety requirements, move checkout-specific details into expandable notes, and move coding-agent prompts to the end.
• Make trusted merchant order verification an explicit prerequisite and success condition in both prompts. Preserve no-retry, approval isolation, and recovery safeguards.
• Remove roadmap text and repeated explanations, reducing prose outside code blocks by about 26%. Preserve existing executable examples and referenced section anchors.

Validation

• mint broken-links — passed.
• Local Mintlify preview — guide returns HTTP 200; desktop and mobile rendering inspected.
• Browser checks — provider tab switching, expandable checkout notes, and in-page anchor targets passed; no page errors or mobile horizontal overflow.
• Verified all 18 original executable examples remain unchanged; Python examples parse.
• git diff main...HEAD --check — passed; full diff reviewed for scope and unnecessary changes.
• Documentation-only change; no live payment or checkout was executed.

---

Note

Low Risk
Documentation-only edits to a single MDX guide; no runtime, auth, or payment API behavior changes.

Overview
Restructures Enable Payments in a Browser Agent so one-time wallet setup is separate from the per-purchase flow, with clearer roles (controller, agent, user) and shared safety rules up front.

Provider choice now points at the wallet overview instead of an inline Link vs Agentcard table. Checkout steps live in Link by Stripe and Agentcard tabs; Stripe payment links, disclosure controls, and wallet edge cases move into expandable Checkout-specific notes.

The purchase path now explicitly creates the browser and navigates to checkout before verification, then walks through verify/confirm, non-card fields, provider-specific payment input, and outcome verification—with merchant order record confirmation as the success bar (also reflected in the end-of-guide coding-agent CLI prompts). Roadmap prose is removed; coding-agent copy moves to Try with a coding agent at the bottom. Executable SDK/CLI examples and section anchors are preserved; surrounding prose is trimmed.

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

[mintlify]

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

Project	Status	Preview	Updated
Kernel	🟢 Ready	View Preview	Sep 17, 2026, 12:28 AM

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

[cursor]

Stale comment

Risk assessment: Low

Decision: Risk is unchanged after this update. The prior approval stands; not re-approving.

Re-evaluation after 383f946

This synchronize deletes a 5-line <Warning> under Fill the approved fields. The same fill disclosure rules remain in the shared safety list and in the Link coding-agent prompt (do not read filled values back, expose them in model context, or assume recordings omit them). This commit does not change executable examples, prompts, navigation, or config.

Overall scope (current HEAD vs main)

• Single file: browsers/enable-payments-in-browser-agent.mdx (429 insertions / 393 deletions).
• Mintlify documentation only. No application code, APIs, auth, billing logic, infrastructure, or docs.json changes.
• No CODEOWNERS file in the repo.

Why Low (not Very Low)

Earlier commits on this PR still relocate and tighten copy-paste coding-agent prompts (trusted merchant order record as the success bar, recovery_required / no-retry language). Prompt-text edits can change agent behavior, so this stays Low rather than Very Low. The delta is localized and more conservative.

Why not Medium or higher

No shared runtime systems, production logic, or infrastructure are modified. Blast radius is this docs page. The latest commit does not relax isolation, retry, or approval-outside-the-agent constraints.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Risk assessment: Low

Decision: Risk is unchanged after 383f946. The prior approval stands; not re-approving.

Re-evaluation after 383f946

This commit deletes a 5-line <Warning> under Fill the approved fields. The same fill disclosure rules remain in the Link coding-agent prompt (do not read filled values back, expose them in model context, or assume recordings omit them). Shared safety rules at the top of the page still cover enrollment/approval isolation, independent verification, no-retry, and merchant order-record confirmation. This commit does not change executable examples, prompts, navigation, or config.

Overall scope (current HEAD vs main)

• Single file: browsers/enable-payments-in-browser-agent.mdx (429 insertions / 393 deletions).
• Mintlify documentation only. No application code, APIs, auth, billing logic, infrastructure, or docs.json changes.
• No CODEOWNERS file in the repo.

Why Low (not Very Low)

Earlier commits on this PR relocate and tighten copy-paste coding-agent prompts (trusted merchant order record as the success bar, recovery_required / no-retry language). Prompt-text edits can change agent behavior, so this stays Low rather than Very Low. The latest delta is localized and more conservative.

Why not Medium or higher

No shared runtime systems, production logic, or infrastructure are modified. Blast radius is this docs page. The latest commit does not relax isolation, retry, or approval-outside-the-agent constraints.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[hiroTamada]

what is AGENTCARD_MODE? Is this env variable in the users application code?

[hiroTamada]

if this is like an example env variable name, we should not specify this?