Create a checkout.com Payment Session and render Flow to complete a payment in a mobile or web app

domain: www.checkout.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Server-side, call POST /payment-sessions with the amount, currency, a reference, and billing.address.country, plus success_url and failure_url, to create the session.
  2. Read payment_session_token from the response — this is what the client-side Flow component consumes, and is a different value from the session_secret used by checkout.com's older, separate Sessions/3DS-only flow.
  3. Client-side, initialize the Checkout Web Components (or native mobile SDK) with the payment session token and your public key to render Flow's payment form.
  4. Let Flow handle card entry, wallet buttons, and any inline 3DS challenge, then listen for its completion callback.
  5. Confirm the resulting payment status server-side (via the Payments API or a webhook) rather than trusting only the client-side completion event.

Known gotchas

Related routes

Create a Klarna Payments session directly via the Klarna API (not Stripe) and render the Klarna widget in a checkout page
klarna.com · 5 steps · unrated
Create an Afterpay/Clearpay direct checkout session and capture payment using the Afterpay direct API (outside of Stripe)
afterpay.com · 5 steps · unrated
Create a Klarna payment session, present the widget, and manage the order lifecycle
klarna · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans