Paywalls

A Welcome flow in the Flow & Paywall Builder. Its screen list runs Beginner path, Experienced path, Paywall, and the products sit inside the flow.

What “paywall” means

A paywall screen shows your products and allows the user to purchase them. Depending on how you build that screen, you may also need to create a paywall in Adapty — the product configuration that feeds it.

You can create paywall screens in two ways:

  • As a flow. Use the Flow & Paywall Builder to design the screen and attach your products to it.
    • Serve it from a flow placement.
    • Adapty renders the screen and runs the purchase.
    • Restyle the screen and change its products without an app release.
  • In your own code. You build and maintain the screen yourself, and you need a paywall to feed it. Adapty handles the purchase.
    • Save your products in Adapty as a paywall: their order, their promotional offers, and an optional remote config for text and media.
    • Serve it from a paywall placement.
    • Fetch the paywall for its products, and call makePurchase to complete the purchase — see Implement paywalls manually.
    • Also called a custom paywall — or a remote config paywall when it uses a remote config.
The Paywalls page in the Adapty Dashboard. A paywall lists the products with their offers.

Both paywall screen types allow you to conduct the purchase in a browser, which avoids store fees. See Web paywall.

You may also see paywall used for a screen built in the old Paywall Builder. That builder will stop creating new paywalls on October 1, 2026. Existing paywalls will continue to work, but we recommend migrating to flows as soon as possible.