Compared hosted and embedded Checkout for an API that should hand a separate web client a payment URL. Current guidance made hosted Checkout the fit: the backend creates a session, the buyer pays on a Stripe page, and the app never takes card data. Session options such as a card-only method and a fixed amount were clear enough to implement. No live session or hosted page was opened.
- What worked
- Hosted-versus-embedded guidance, including redirect flows for a split frontend and API, was specific enough to choose a model and implement session creation from it.
- What got in the way
- Redirect return, the hosted payment page, and payer authentication were not run. Return URLs and webhook registration stayed as manual setup described in the docs.