Quick Start Guide
Get your first checkout session running in under 5 minutes
API Reference & Live Testing
Explore the full API documentation and interactively test Checkout Session requests and responses.
Preview Checkout
Calculate pricing, taxes, and totals before creating a session.
Session Validity: Checkout sessions are valid for 24 hours by default. If you pass
confirm=true in your request, the session will only be valid for 15 minutes.Prerequisites
1
Dodo Payments Account
You’ll need an active Dodo Payments merchant account with API access.
2
API Credentials
Generate your API credentials from the Dodo Payments dashboard:
3
Products Setup
Create your products in the Dodo Payments dashboard before implementing checkout sessions.
Creating Your First Checkout Session
- Node.js SDK
- Python SDK
- REST API
API Response
All methods above return the same response structure:1
Get the checkout URL
Extract the
checkout_url from the API response.2
Redirect your customer
Direct your customer to the checkout URL to complete their purchase.
3
Handle the return
After payment, customers are redirected to your
return_url with query parameters including payment/subscription ID, status, customer email, and any license keys. See the return_url parameter docs for the full list.Request Body
Required Fields
Essential fields needed for every checkout session
Optional Fields
Additional configuration to customize your checkout experience
Required Fields
Array of products to include in the checkout session. Each product must have a valid
product_id from your Dodo Payments dashboard.Optional Fields
Configure these fields to customize the checkout experience and add business logic to your payment flow.Customer Information
Customer Information
Customer information. You can either attach an existing customer using their ID or create a new customer record during checkout.
- Attach Existing Customer
- New Customer
Attach an existing customer to the checkout session using their ID.
Billing address information for accurate tax calculation, fraud prevention, and regulatory compliance.
When
confirm is set to true, all billing address fields become required for successful session creation.Payment Configuration
Payment Configuration
Control which payment methods are available to customers during checkout. This helps optimize for specific markets or business requirements.Available Options:
credit, debit, upi_collect, apple_pay, google_pay, amazon_pay, klarna, affirm, afterpay_clearpay, cashapp, multibanco, bancontact_card, eps, ideal, przelewy24, paypal, sunbitExample:Override the default currency selection with a fixed billing currency. Uses ISO 4217 currency codes.Supported Currencies:
USD, EUR, GBP, CAD, AUD, INR, and moreExample: "USD" for US Dollars, "EUR" for EurosThis field is only effective when adaptive pricing is enabled. If adaptive pricing is disabled, the product’s default currency will be used.
Display previously saved payment methods for returning customers, improving checkout speed and user experience.
Session Management
Session Management
URL to redirect customers after payment completion. Dodo Payments appends the following query parameters to your URL on redirect:
Example redirect URLs:
URL to redirect customers when they click the back button or cancel the checkout session. If not provided, the back button will not be displayed.
If true, finalizes all session details immediately. API will throw an error if required data is missing.
Apply one or more stacked discount codes to the checkout session. Codes are applied in array order (the first code reduces the base price, the second reduces the already-discounted price, and so on), up to a maximum of 20 codes per session.
The singular
discount_code field below is deprecated but still fully supported — existing integrations continue to work without changes. It cannot be combined with discount_codes in the same request. Migrate to discount_codes when convenient to take advantage of stacking.Deprecated — prefer
discount_codes for new integrations. This field still works for backward compatibility, but cannot be combined with discount_codes in the same request.Custom key-value pairs to store additional information about the session.
Override merchant default 3DS behaviour for this session.
Enable minimal address collection mode. When enabled, the checkout only collects:
- Country: Always required for tax determination
- ZIP/Postal code: Only in regions where it’s necessary for sales tax, VAT, or GST calculation
UI Customization & Features
UI Customization & Features
Custom Fields
Custom Fields
Collect additional information from customers during checkout with custom form fields. You can define up to 5 custom fields per checkout session. Customer responses are included in webhook payloads and available via the API.
Customer responses to custom fields are included in:
- Webhooks:
payment.succeeded,subscription.active, and other relevant event payloads contain thecustom_field_responsesarray - API responses: Payment and subscription objects include
custom_field_responses
Subscription Configuration
Subscription Configuration
Additional configuration for checkout sessions containing subscription products.
Usage Examples
Here are 10 comprehensive examples showcasing different checkout session configurations for various business scenarios:1. Simple Single Product Checkout
2. Multi-Product Cart
3. Subscription with Trial Period
4. Pre-confirmed Checkout
When
confirm is set to true, the customer will be taken directly to the checkout page, bypassing any confirmation steps.5. Checkout with Currency Override
The
billing_currency override only takes effect when adaptive currency is enabled in your account settings. If adaptive currency is disabled, this parameter will have no effect.6. Saved Payment Methods for Returning Customers
7. B2B Checkout with Tax ID Collection
8. Dark Theme Checkout with Stacked Discount Codes
9. Regional Payment Methods (UPI for India)
For detailed information about UPI configuration and testing, see the India Payment Methods page.10. BNPL (Buy Now Pay Later) Checkout
For detailed information about BNPL configuration and testing, see the Buy Now Pay Later (BNPL) page.11. Using Existing Payment Methods for Instant Checkout
Use a customer’s saved payment method to create a checkout session that processes immediately, skipping payment method collection:The payment method must belong to the customer and be compatible with the payment currency. This enables one-click purchases for returning customers.
12. Short Links for Cleaner Payment URLs
Generate shortened, shareable payment links with custom slugs:13. Skip Payment Success Page with Immediate Redirect
Redirect customers immediately after payment completion, bypassing the default success page:When
redirect_immediately is enabled, customers are redirected to your return_url immediately after payment completion, skipping the default success page entirely.14. Forcing a Language
Force the checkout to display in a specific language, overriding the customer’s browser language detection:ar), Catalan (ca), Chinese (zh), Dutch (nl), English (en), French (fr), German (de), Hebrew (he), Indonesian (id), Italian (it), Japanese (ja), Korean (ko), Malay (ms), Polish (pl), Portuguese (pt), Romanian (ro), Russian (ru), Spanish (es), Swedish (sv), Thai (th), Turkish (tr)
15. Collecting Custom Fields
Collect additional information from customers during checkout using custom fields:Custom field responses are automatically included in webhook payloads (
payment.succeeded, subscription.active, etc.) and can be retrieved via the API. Use them to enrich your CRM, trigger onboarding flows, or customize the customer experience.text, number, email, url, date, dropdown, boolean
Previewing Checkout Sessions
Before creating a checkout session, you can preview the pricing breakdown including taxes, discounts, and totals. This is useful for displaying accurate pricing to customers before they proceed to checkout.- Node.js SDK
- Python SDK
Preview API Reference
View the complete preview endpoint documentation.
Moving from Dynamic Links to Checkout Sessions
Key Differences
Previously, when creating a payment link with Dynamic Links, you were required to provide the customer’s complete billing address. With Checkout Sessions, this is no longer necessary. You can simply pass along whatever information you have, and we’ll handle the rest. For example:- If you only know the customer’s billing country, just provide that.
- The checkout flow will automatically collect the missing details before moving the customer to the payment page.
- On the other hand, if you already have all the required information and want to skip directly to the payment page, you can pass the full data set and include
confirm=truein your request body.
Migration Process
Migrating from Dynamic Links to Checkout Sessions is straightforward:1
Update your integration
Update your integration to use the new API or SDK method.
2
Adjust request payload
Adjust the request payload according to the Checkout Sessions format.
3
That's it!
Yes. No additional handling or special migration steps are needed on your side.
Related API Reference
Create Checkout Session
Complete API reference for creating checkout sessions with all available parameters and options
Preview Checkout Session
API reference for previewing pricing, taxes, and totals before creating a session