Developer Resources · Checkout Session
Overview
Overview of Monime Checkout Sessions and how to use them
A Checkout Session is a short-lived object that creates a hosted checkout page for collecting payments on your behalf. Use it to accept payments quickly without building your own payment UI. You control the line items, available payment options, and where Monime returns the customer after payment.
When to use Checkout Session
- You want a fast, secure way to accept payments with minimal UI work
- You need a hosted page that supports multiple payment methods out-of-the-box
- You want Monime to handle payment state, redirection, and receipt UI
How it works
Create a Checkout Session (server)
Your server calls the API with a name, one or more line items, and optional payment and redirect settings.
Redirect customer
Redirect the customer to the hosted checkout URL returned in the session.
Customer pays
The customer completes payment on Monime's secure page.
Webhook + Return URL
Receive payment status via webhook and/or redirect back to your site.
Session lifecycle
A session starts pending and ends in one of three states.
Each final state has a matching webhook event: checkout_session.completed, checkout_session.cancelled and checkout_session.expired.
Quick start
Create Session API
Create a new checkout session from your backend
Retrieve Session
Look up a session to check its latest status
List Sessions
Browse sessions for reporting or debugging
Key session fields
Webhooks
We recommend handling payment lifecycle events using webhooks to ensure your system is updated even if the customer closes the browser before redirecting.
Webhook Overview
Learn how webhooks work on Monime
HMAC Verification
Verify webhook signatures securely
Environments: Test vs Live
Use Test mode for development and Live for production. Tokens, behavior, and prefixes differ between environments.