Skip to content
Nuxie
Esc
navigateopen⌘Jpreview
On this page

Monetization

Products, features, and entitlements for subscription monetization

Nuxie gives you a unified system for defining what you sell, what it unlocks, and how your app checks access at runtime. Instead of scattering billing logic across your codebase, you model everything in the dashboard and let the SDK handle the rest.

The mental model

Monetization in Nuxie follows a three-layer structure:

  • Products are what your customers buy – monthly plans, yearly subscriptions, one-time add-ons.
  • Features are the capabilities your app exposes – “premium_export”, “api_calls”, “unlimited_storage”.
  • Entitlements are the rules that connect the two. When a customer buys a product, Nuxie grants the entitlements attached to it, unlocking features with the allowances you configured.

Think of it like this: a product is the package on the shelf, features are what is inside, and entitlements are the packing slip that says what each purchase includes.

Product (Pro Plan)
  |
  |-- Entitlement: "premium_export" (boolean, lifetime)
  |-- Entitlement: "api_calls" (metered, 10,000/month)
  |-- Entitlement: "storage_gb" (metered, 50 GB/month)

How it works end to end

  1. Define products and prices in the Nuxie dashboard. Set billing intervals, amounts, and link to your payment processor.
  2. Create features that represent capabilities in your app. Choose boolean for simple on/off access, metered for usage-tracked limits, or credit systems for flexible unit-based billing.
  3. Attach entitlements to products. Configure allowances (fixed amounts or unlimited) and reset intervals (monthly, yearly, or lifetime).
  4. Present paywalls using Experiences. A signed Placement resolves the live store terms, and StoreKit or the configured provider processes checkout without a pre-purchase Nuxie request.
  5. Check access from your app. The iOS SDK serves fresh authenticated profile state locally and refreshes from the server when needed.

Connecting to experiences

Experiences are how you present paywalls and onboarding experiences to your users. When an experience includes a paywall, the purchase buttons map to products you have defined in Monetization. After a verified purchase, Boolean and unlimited feature access can update immediately on the device. Fixed quotas and credit balances update only from authoritative server state. On iOS, the SDK can combine a new native purchase and first confirmed use in one server operation without inventing a local balance.

See Experiences for details on triggers, targeting, and experience delivery.

Connecting to the SDK

The iOS SDK keeps a local profile of the user’s current features and balances. Verified purchases can update Boolean and unlimited access locally while the SDK synchronizes in the background. Fixed quotas and credit balances are never invented from an unsynchronized purchase; the authoritative server response updates them. Your app checks access with a single method call:

// nuxie-doc-fragment: monetization-overview-boolean-access harness=async-body
let access = try await NuxieSDK.shared.hasFeature("premium_export")
if access.allowed {
    // User has access
}

For metered features, you can check whether enough balance remains:

// nuxie-doc-fragment: monetization-overview-metered-access harness=async-body
let access = try await NuxieSDK.shared.hasFeature(
    "api_calls",
    requiredBalance: 1
)
if access.allowed {
    // Sufficient balance
}

See Presenting Experiences and Features & Entitlements (SDK) for integration details.

Supported payment processors

Processor Status Use case
App Store Supported iOS in-app purchases and subscriptions via StoreKit 2
Google Play Backend supported Catalog, purchase-token, and lifecycle processing are supported; an Android SDK checkout surface is a later milestone.

See App Store Connect and Google Play for configuration details.

The dashboard

The Monetization section of the dashboard provides dedicated pages for managing each layer:

  • Products – create and configure plans, add-ons, and their prices
  • Features – define boolean, metered, and credit system capabilities
  • Credits – build credit systems that convert across multiple metered features
  • Settings – connect payment processors and configure webhook URLs

Next steps

Last updated on August 20, 2026

Was this page helpful?