Purchase Button vs. Paywall

Supertab offers two main ways to monetize your content: the Purchase Button and the Paywall. Both allow users to buy access, but they serve slightly different use cases depending on how you want to integrate Supertab into your site or app.

The Purchase Button is mainly used for "single item" purchases. Such as: downloadable content, a pdf, or a podcast episode. You can place it anywhere: on a landing page, inside a video player, or next to a downloadable file. When a user clicks it, Supertab handles the purchase flow and charges the users accordingly.

Note: Supertab does not handle entitlement checks with purchases made with the button. A user is able to purchase the same content multiple times.

Best for:

• Selling access to a single piece of content.
• Situations where you want to keep the content visible (e.g. previews, samples, or partial access).

Pros

• Lightweight and fully customizable placement.
• Doesn’t interfere with normal page rendering or indexing.
• Ideal for testing conversion placement or A/B experiments.

Cons

• Requires custom code to perform entitlement checks.
• Less immersive than a traditional paywall experience.

The Paywall automatically replaces or overlays protected content until a valid purchase or access condition is met. It’s a way to gate premium material without modifying your layout or inserting custom triggers.

Supertab automatically handles any entitlement checks for you and will either display or hide the paywall accordingly.

Best for:

• Articles, videos, or pages where you want automatic gating.
• Publishers who want “set it and forget it” monetization.
• Use cases where entitlement enforcement must be automatic.

Pros

• Handles access control automatically. No custom unlock logic needed.
• Can display multiple offering types: time passes, subscriptions, and upsell offers.
• Creates a consistent purchase experience across your site.

Cons

• Less control over placement and design compared to a purchase button.

• May not integrate cleanly with certain single-page applications or dynamic front-end frameworks.