AppPaywall

Access gate for monetized built apps: renders children when the end-user has access, otherwise shows a paywall overlay with the unlock CTA. The default way to charge users of an app.

import { AppPaywall } from 'flowstack-sdk/paywall'

Wraps app content and surfaces the platform paywall when useAppAccess reports the user is blocked, or immediately when the backend emits an app_paywall SSE event mid-conversation (metered credits running out). It does NOT replace backend enforcement — the backend's AppAccessGate always has the final say (402 / SSE event).

This is the monetization entry point for built apps: the owner sets pricing with setMonetization (platform-level config), the app wraps its content in AppPaywall, done. Do not wire raw Stripe calls to charge app users — the owner-registered Stripe integration is for operating the OWNER'S Stripe account, not for app monetization. 0.3.0 (P0-162): when the builder configures a monthly subscription plan, the paywall renders the plan CTA above the one-time unlock. Since 0.3.3 (P0-167) subscriptions are status-only: a subscriber with an open paid period has full access and never reaches this paywall, so the subscribe CTA shows only for lapsed or never-subscribed users.

Signature

<AppPaywall siteId={config.appScope} builderTenantId?={...} onBlocked?={(reason) => ...}>{children}</AppPaywall>

Parameters

Examples

import { AppPaywall } from 'flowstack-sdk/paywall';

export default function App() {
  return (
    <AppPaywall siteId={config.appScope}>
      <YourAppContent />
    </AppPaywall>
  );
}

See also

useAppAccess · setMonetization · getMonetization · PaymentRequired · AppSubscriptionStatus

Source: wallet/AppPaywall.tsx · Also available in llms-full.txt and registry.json.