POST to the Checkout.com Hosted Payments Page endpoint with the amount, currency, and customer details to obtain a _links.redirect.href session URL
Configure the success_url, failure_url, and cancel_url in the request body; ensure they include a session identifier so you can look up the payment on return
Optionally customize the page appearance using the billing descriptor and locale fields
When the customer is redirected back, do not trust the URL parameters alone to determine payment outcome; call the GET /payments/{payment_id} endpoint to retrieve the authoritative payment status
Handle the case where the customer closes the browser mid-flow without completing the redirect by polling payment status after a timeout
Log the cko-session-id included in the success redirect for support and reconciliation purposes
Known gotchas
The hosted payment session URL expires after a configurable period; do not cache or share the URL, and regenerate it if the customer returns after expiry
Success redirect parameters are informational only and can be manipulated by a malicious client; always verify payment status via the server-side API call before fulfilling the order
3DS outcomes for hosted page flows are handled entirely by Checkout.com; you do not need a separate 3DS redirect handling but must still check the 3ds.authentication_response field in the payment details
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp