[hiroTamada]

Description

The "enable payments in a browser agent" walkthrough only covered Link and AgentCard, and the wallets overview pointed KERNEL card users there anyway. A KERNEL card user had no end-to-end path from a verified purchase through fill, submission, and reporting the outcome. This adds that path.

• browsers/enable-payments-in-browser-agent:
  • New KERNEL card tab in step 4 (first, matching the wallets overview order):
    • create the purchase with merchant_url set to the top-level checkout page, since fill is locked to that url's exact origin
    • authorize with no browser or page parameters, presenting any returned spend_approval action through the controller (Visa approval, or the fresh security code for cards without network tokens)
    • wait for ready
    • fill number, expiration / exp_month + exp_year, and cvc. Notes: 403 destination_denied off-origin, no stored billing fields (billing_* returns field_unavailable), fill only visible fields
    • submit promptly, before the one-time code expires
    • report the merchant outcome once with confirm_transaction when advertised
    • TypeScript, Python, and CLI examples
  • "Before you start" covers KERNEL card's checkout requirement, and wallet setup links to the KERNEL card guide.
  • New KERNEL card prompt under "Try with a coding agent", parallel to the Link and AgentCard prompts.
• integrations/wallets/overview: "Next step" now includes KERNEL card in the walkthrough's scope.
• browsers/payments: "How payments work" step 4 describes KERNEL card authorization alongside Link and AgentCard.
• integrations/wallets/kernel: links the walkthrough from its reference list.

This documents the default single-card wallet flow. It doesn't depend on the payment-methods docs, and choosing a card with payment_method_id can be linked in once that page lands.

Testing

• Snippet typecheck against the published SDKs (v0.136.0):
  • TypeScript: every TS block in the new tab through tsc --strict --noEmit against @onkernel/sdk. 0 errors.
  • Python: every Python block through pyright against kernel. 0 errors.
  • The snippets were typechecked, not executed against the live API.
• mint broken-links: no broken links.
• mint broken-links --check-anchors: no broken anchors in the changed files. The remaining reports are pre-existing on other pages.
• mint validate: build and validation passed.
• git diff --check: clean.
• Not rendered locally (mint dev couldn't start in this environment). Check the Mintlify preview for tab rendering.

---

Note

Low Risk
Documentation-only changes with no runtime, auth, or payment logic modifications.

Overview
The browser-agent payments guide previously covered only Link and AgentCard; this PR adds a full KERNEL card path and cross-links it from the wallets overview and kernel integration page.

In enable-payments-in-browser-agent, prerequisites now call out KERNEL card’s live-only mode, merchant_url origin lock for fill, and wallet setup via the kernel guide. Step 4 gains a KERNEL card tab (first in the tab order) covering pre-checkout authorize (no browser/page args, optional spend_approval), polling until ready, fill with origin and billing constraints, one-shot checkout submit, and optional confirm_transaction—with TypeScript, Python, and CLI examples. A matching KERNEL card coding-agent CLI prompt was added alongside Link and AgentCard.

payments, integrations/wallets/overview, and integrations/wallets/kernel were updated so the high-level flow and “next step” copy explicitly include KERNEL card.

^{Reviewed by Cursor Bugbot for commit fc1c4af. 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	Oct 31, 2026, 12:16 AM

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

[yummybomb]

two fixes before merge:

• keep polling while pending_authorization. one 60s wait doesn’t mean approval failed.
• uppercase order.currency before confirm_transaction; passing usd returns 400.

[yummybomb]

lgtm.

note

agent found an edge case: the loop can still poll forever if the funding card is removed: status stays pending_authorization with funding_status: removed. check funding_status and add an expiry/deadline in both snippets.