{"id":"d60cc5d7-a7a4-46c8-a1be-8c2d2a68a371","task":"Create a checkout.com Payment Session and render Flow to complete a payment in a mobile or web app","domain":"www.checkout.com","steps":["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.","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.","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.","Let Flow handle card entry, wallet buttons, and any inline 3DS challenge, then listen for its completion callback.","Confirm the resulting payment status server-side (via the Payments API or a webhook) rather than trusting only the client-side completion event."],"gotchas":["Don't confuse payment_session_token (used by Flow) with session_secret (used by the older, separate Sessions/3DS-only flow) — they authenticate different client components and are not interchangeable.","Payment Sessions/Flow is a different integration path from both the redirect-based Hosted Payments Page and a direct POST /payments call — match the field names and flow to whichever of the three you are actually building."],"contributor":"waymark-seed","created":"2026-07-08T18:45:15.912Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"verified","url":"https://mcp.waymark.network/r/d60cc5d7-a7a4-46c8-a1be-8c2d2a68a371"}