Docs

Inline checkout

Inline checkout lets you create integrated checkout experiences. You display information about items and totals, letting Paddle take care of capturing customer and payment details.

Build integrated checkout experiences with inline checkout. Customers sign up and pay for subscriptions as part of your app or website, making for a seamless experience.

Using inline checkout, you can:

  • Create checkout experiences that are fully integrated with your app or website.
  • Choose whether to present a one-page or a multi-page checkout experience.
  • Let Paddle securely capture customer and payment information in an optimized checkout frame.
  • Display items, totals, and other information from Paddle on your page.
  • Use Paddle.js methods and events to build advanced checkout experiences.

Illustration showing an inline checkout implementation. The Paddle Checkout frame is on the left and is on the payment page. It shows buttons for card, Apple Pay, and PayPal, followed by a card payment form that includes email address, country, and ZIP code. On the right is an items list and totals. The grand total is $3,600 billed monthly and is at the top.

How it works

Inline checkout works by embedding a frame with Paddle Checkout into your website or app.

The checkout frame handles collecting customer information and capturing payment details. Your page displays the items list, totals, and options for changing what's on the checkout. Paddle.js lets your page and the checkout frame interact with each other.

Paddle automatically creates a subscription when a checkout completes, ready for you to provision.

It's important that customers know who they're buying from, what they're buying, and how much they're paying.

To build an inline checkout that's compliant and optimized for conversion, your implementation must include:

Illustration of an inline checkout implementation. On the left is the Paddle Checkout frame, and on the right is an items list. At the top of the items list is some text that says $3600, free for 14 days then billed monthly (1). Under this is an items list (2), followed by a totals table that includes subtotal, tax, and grand total (3). At the bottom is the Paddle.com footer (4) and a link to a refund policy (5).

  1. If recurring, how often it recurs and the total to pay on renewal. If a trial, how long the trial lasts.
  2. A description of what's being purchased.
  3. Transaction totals, including subtotal, total tax, and grand total. Be sure to include the currency too.
  4. The full inline checkout frame, including the checkout footer that has information about Paddle, our terms of sale, and our privacy policy.
  5. A link to your refund policy, if it differs from the Paddle.com standard refund policy.

Customer journey

Customer opens a checkout

You can open inline checkout by passing items or an existing transaction. Use Paddle.js to show and update on-page information, and Paddle.js methods to update items based on customer interaction.

Illustration showing a sample inline checkout implementation. The Paddle Checkout frame is on the left, and the items list is on the right.

Customer enters their details on one screen

Inline checkout asks customers for their email, country, and (in some regions) ZIP or postal code. On the same screen, customers are presented with the card payment form, as well as options to pay with PayPal, Apple Pay, Google Pay, or other local payment method.

You can prefill customer details and present saved payment methods to speed up checkout.

Illustration showing a sample inline checkout implementation. The Paddle Checkout frame is on the left and shows fields for email address, country, ZIP code, and card details. There's a blue 'Continue' button at the bottom.

Checkout completed

Paddle routes every payment to the best acquirer for that sale to get the best possible chance of success. Customers enter a success workflow that you can build.

Illustration showing a sample inline checkout implementation. The Paddle Checkout frame is on the left and shows a large green checkmark.

Paddle creates a subscription

Paddle automatically creates a subscription for the customer, ready for you to provision. The payment method the customer used is held on file for renewals or subscription changes.

Illustration showing a created subscription in Paddle. This is an abstract illustration, rather than a representation of an interface. In the background is a sheet with a user icon, recurring amount, MasterCard symbol, and an active tag. It's meant to represent a subscription page in the Paddle web app. In the foreground is a card that says 'webhook received: new subscription for premium plan.' It's meant to represent a subscription.created webhook event.

Customer opens a checkout

You can open inline checkout by passing items or an existing transaction. Use Paddle.js to show and update on-page information, and Paddle.js methods to update items based on customer interaction.

Illustration showing a sample inline checkout implementation. The Paddle Checkout frame is on the left, and the items list is on the right.

Customer enters their details

Inline checkout asks customers for their email, country, and (in some regions) ZIP or postal code. You can prefill this information to skip this step entirely.

Illustration showing a sample inline checkout implementation. The Paddle Checkout frame is on the left and shows fields for email address, country, and ZIP code. There is a blue 'Continue' button at the bottom.

Customer chooses a payment method

Customers land on a card payment form, or they can choose to pay with PayPal, Apple Pay, Google Pay, or other local payment method.

Illustration showing a sample inline checkout implementation. The Paddle Checkout frame is on the left and includes two buttons for Apple Pay and PayPal, with the card payment form underneath. There is a button that says 'Pay by card' at the bottom.

Checkout completed

Paddle routes every payment to the best acquirer for that sale to get the best possible chance of success. Customers enter a success workflow that you can build.

Illustration showing a sample inline checkout implementation. The Paddle Checkout frame is on the left and shows a large green checkmark.

Paddle creates a subscription

Paddle automatically creates a subscription for the customer, ready for you to provision. The payment method the customer used is held on file for renewals or subscription changes.

Illustration showing a created subscription in Paddle. This is an abstract illustration, rather than a representation of an interface. In the background is a sheet with a user icon, recurring amount, MasterCard symbol, and an active tag. It's meant to represent a subscription page in the Paddle web app. In the foreground is a card that says 'webhook received: new subscription for premium plan.' It's meant to represent a subscription.created webhook event.

Was this page helpful?