Checkout-first guidance required orientation for the server-only audit prompt
Stripe's onboarding documentation recommends Checkout Sessions for most integrations and presents PaymentIntents as a lower-level path. Both agents reported filtering through Checkout-oriented material for this deliberately server-only prompt, then selected PaymentIntents and completed the core workflow without a wrong API call. The documentation priority reflects Stripe's recommended default for the broader customer population. A clearly linked API-only guide could help advanced cases, but the audit measured orientation effort rather than a failed task.
How can I reproduce this?
Requires: None — a browser or HTTP client
- Visit https://docs.stripe.com/payments (or fetch the .md variant).
- Visit https://docs.stripe.com/payments/accept-a-payment.
- Visit the quickstart page.
Expected: The first integration option is the Stripe-hosted Checkout page labelled "Most Popular"; accept-a-payment offers three options, all Checkout-based, with no PaymentIntents-only flow as a peer option; the quickstart states Stripe recommends the Checkout Sessions API for most integrations and to use the Payment Intent API only if explicitly requested.
Evidence · transcript moments