Private preview

How Checkout studio works Private preview

Learn about and set up Checkout studio's core capabilities.

Checkout studio lets you manage checkout integrations, track metrics, and define your payment method strategy by running experiments. It centralises information that’s normally spread across multiple Dashboard pages and API parameters, including:

• Active checkout integrations and transaction details.
• Payment method usage and rules.
• Performance metrics and running experiments.

You can tag each Checkout integration created in Checkout Studio with an integration_identifier – an optional string that you set on the Checkout Session. Use it to attribute and compare performance across different Checkout contexts, such as distinguishing a consumer-facing flow from a wholesale or B2B flow.

Determine whether you use Checkout

You use Checkout if your integration creates Checkout Sessions with the POST /the relevant part of the product API. To confirm:

• Search your server-side code for checkout/sessions API calls or a stripe. checkout. sessions. create SDK call.
• Look for a checkout. session. completed webhook handler in your codebase.
• Visit the Checkouts page in the Dashboard. If you have existing sessions listed, you’re already using Checkout.

Checkout studio supports all three Checkout integration types:

• Hosted page : Stripe hosts the entire payment page. You create a session server-side and redirect the customer to the returned URL. Requires the least ongoing maintenance.
• Embedded form : The embedded form renders directly on your site using a client secret. Customers complete payment without leaving your page.
• Payment Links : A no-code option that generates shareable links or an embeddable buy button, with no API integration required.

Checkout studio and the Checkout Sessions API

Checkout studio configures your Checkout integration through the same APIs you use in code. When you make changes in Checkout studio:

• Settings map to Checkout Session parameters.
• Payment method configurations apply to your existing integration.
• Experiments create separate Checkout Session configurations that are served based on traffic allocation.
• All configuration remains accessible through the API.

This means you can:

• Use Checkout studio for some configurations and the API for others.
• Migrate existing API-based configurations to Checkout studio management.
• Continue using your current deployment and CI/CD processes.
• Access Checkout studio configurations programmatically if needed.

Customise and launch a checkout integration

The Checkouts tab lets you customise, launch, and manage a Checkout integration without writing code. To get started:

1. Click Create checkout, and select Web or In-app purchases.
2. Choose an existing integration type: Full page or embedded form.
3. Set up the integration’s capabilities, and customise its design.
4. To go live, click Implement and complete the checklist, which includes creating a Checkout Session and setting up webhooks.

After you launch an integration, it appears under the Active section. Clicking Review lets you inspect sessions transactions. Like the Checkouts tab, the Payment Links tab lets you create, edit, and manage payment links.

Monitor performance

The Performance tab lets you compare metrics across different time horizons and checkout integrations. Here, you can see:

• Conversion funnels broken down by Checkout integration and country
• Payment volume and average order value
• Session count by month

Create payment rules and experiments

While the Logic tab lets you create payment rules to automatically apply different configurations to different customers, the Experiments tab lets you run experiments to test different configurations.

Define a payment rule

To define a payment rule:

1. Click Create rule from the Logic tab.
2. Select a payment method configuration.
3. Select a payment method.

Any custom rules you create determine when the select payment method displays as an option for your users.

Create an experiment

To create an experiment:

1. Click Create experiment from the Experiments tab.
2. Select a payment configuration.
3. Create a treatment group by toggling on payment methods.
4. Start the experiment by giving it a name, and defining the treatment traffic allocation.

Only sessions that meet the experiment criteria are eligible. All other sessions see your standard configuration. Your existing configuration is your control group, and you can’t edit payment methods for it while the experiment is running.

Data and privacy

Checkout studio accesses the same transaction data your Checkout integration already generates. All data handling follows the Stripe standard security and privacy practices:

• Transaction details are only visible to users with appropriate Dashboard permissions.
• The AI assistant doesn’t train on your specific transaction data.
• Analytics aggregations follow the same privacy controls as other Stripe reports.
• You control which team members can access Checkout studio.