# Checkout studio Launch, configure, and monitor Checkout integrations from the Dashboard. Checkout studio is a [Dashboard page](https://dashboard.stripe.com/checkout) that lets you create, design, and monitor different [Stripe Checkout](https://docs.stripe.com/payments/checkout.md) integrations. Because it’s entirely contained in the Dashboard, it doesn’t require any coding to set up and use. If you [already use Checkout](https://docs.stripe.com/payments/checkout-studio/how-it-works.md#determine-whether-you-use-checkout), Checkout studio expands what you can do by letting you: - Configure payment methods, branding, and checkout behavior from one place without updating your code or making individual API calls. - Replay and inspect individual transactions to debug issues directly, rather than piecing together logs from separate tools. - Run controlled A/B experiments against your live traffic to validate configuration changes before rolling them out. - Use [Stripe’s AI assistant](https://docs.stripe.com/assistant.md) to get personalized recommendations for optimizing your Checkout integration. Stripe-provided recommendations don’t guarantee any impact on your business performance. ## Get started [How Checkout studio works](https://docs.stripe.com/payments/checkout-studio/how-it-works.md): Learn about Checkout studio’s capabilities and how it fits into your workflow. [Track analytics](https://docs.stripe.com/payments/checkout-studio/analytics.md): Track and analyze how your checkout integration is performing for your business. ## Features | | | | | **Create and launch checkout integrations** | Use the visual editor to configure a Hosted page, Embedded form, or Payment Links integration. Set up payment methods, customize branding and layout, and configure session behavior—then launch directly from the Dashboard without writing code. After launch, each integration is visible in the **Active** section where you can review session-level transaction details. | | **Monitor performance** | Track key metrics including conversion funnel (broken down by integration and country), payment volume, average order value, and session count. Compare performance across different time horizons and integrations side by side to identify where customers drop off and surface opportunities to improve conversion. | | **Create payment rules and experiments** | Define conditional logic to automatically serve different payment method configurations to different customers—for example, surfacing region-specific methods based on the customer’s country. Run A/B experiments to measure the impact of configuration changes against your live traffic before rolling them out broadly. Your existing configuration is always the control group. | | **Manage payment methods** | See which payment methods are gaining adoption, where they’re most popular by region, and how they contribute to overall payment volume. Use this data to make informed decisions about which methods to enable or prioritize, and drill into detailed volume reports for any method. | ## Request access