Document supported AgentCard processors - #599
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
There was a problem hiding this comment.
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 76c8723. Configure here.
| to an ordinary hold. The ordinary Square hold flow is retained for compatibility | ||
| with deployments that haven't enabled prepared checkout. Encrypted payloads, | ||
| different request layouts, and | ||
| unrecognized processor endpoints pass through without native handoff. |
There was a problem hiding this comment.
Dense processor notes need bullets
Low Severity
The new processor-coverage paragraph packs several separate facts into one dense block: ordinary-hold matching rules, the prepare_checkout requirement, which adapters lack a hold path, current Square rejection behavior, leftover hold compatibility, and unrecognized-endpoint passthrough.
Triggered by learned rule: Use bullet lists when covering multiple distinct points in guides
Reviewed by Cursor Bugbot for commit 76c8723. Configure here.


summary
testing
git diff --checkNote
Low Risk
Documentation-only update to Agentcard integration guidance; no runtime or API behavior changes in this diff.
Overview
Expands the Agentcard checkout coverage table from five to nine processors and adds a flow column that labels each adapter as either an ordinary approval hold or prepared single-use checkout (with Square marked as prepared while that mode is enabled in the current deployment).
New rows document Braintree, Worldpay, Bambora, and Mercado Pago with their recognized HTTPS
POSTendpoints; existing rows (Stripe, Shopify, Recurly, Razorpay) now spell out flow type and Razorpay’s merchant status reconciliation note.Replaces the short alias-matching paragraph with guidance on when requests must match adapter layout for ordinary holds versus when cards must complete
prepare_checkoutfirst, which processors are prepared-only, and that Square on the current KERNEL deployment rejects unprepared checkouts instead of falling back to an ordinary hold.Reviewed by Cursor Bugbot for commit 76c8723. Bugbot is set up for automated code reviews on this repo. Configure here.