Nuxie/Docs
Monetization

Overview

Products, features, and entitlements for subscription monetization

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.

text
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 campaigns. When a user taps "Subscribe", the SDK sends the purchase to Nuxie for processing.
  5. Check access from your app. The SDK evaluates entitlements on-device using a cached profile, so checks are fast and work offline.

Connecting to campaigns

Campaigns are how you present paywalls and onboarding flows to your users. When a campaign includes a paywall, the purchase buttons map to products you have defined in Monetization. A completed purchase triggers entitlement grants, and the user immediately gains access to the features your product unlocks.

See Campaigns for details on triggers, targeting, and flow delivery.

Connecting to the SDK

The iOS SDK keeps a local profile of the user's current features and balances. After a purchase completes, the profile updates automatically. Your app checks access with a single method call:

swift
let result = Nuxie.shared.entitled(feature: "premium_export")
if result.allowed {
    // User has access
}

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

swift
let result = Nuxie.shared.entitled(feature: "api_calls", requiredBalance: 1)
if result.allowed {
    // Sufficient balance
}

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

Supported payment processors

ProcessorStatusUse case
App StoreSupportediOS in-app purchases and subscriptions via StoreKit 2

See App Store Connect 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