Monetization

Sell subscriptions, unlock app features, and offer usage allowances.

Nuxie helps you connect what you sell to what customers can use in your app. You can offer a subscription for premium access, include a usage allowance, or sell credits that customers spend across several actions.

Use Nuxie’s billing integration or keep an existing provider such as RevenueCat or Superwall. Apple and Google remain the merchant of record for purchases through their stores.

Products, Features, and Entitlements

Products are the items customers buy, such as a monthly subscription or a credit pack. Features describe what those purchases unlock: premium access, exports, or a credit balance. A Product Grant defines the Features included in a Product. An Entitlement is the access the customer receives.

This lets several Products provide the same capability. For example, monthly and annual subscriptions can both grant premium access. Your app checks that one Feature, regardless of which plan the customer bought. An export pack could instead grant a fixed allowance, while a Pro subscription grants unlimited exports.

Purchase integrations

Choose who handles checkout before setting up your paywall. With Nuxie’s store integration, Product grants in Nuxie determine what the customer can use. If you retain an existing purchase provider, keep using its access checks.

App Store

Nuxie’s iOS integration uses StoreKit 2 for checkout and synchronizes verified transactions. Connect App Store Connect to set up the catalog and purchase data for your app.

Google Play

The Android integration uses your Google Play catalog, verifies purchase tokens, and keeps access updated as purchases change. Follow Google Play setup to connect the store app.

Existing billing provider

Keep your provider’s checkout and transaction handling while using Nuxie to design and deliver the paywall. With RevenueCat, Superwall, or a custom purchase delegate, Nuxie receives only the checkout outcome. A successful outcome can complete the Journey, but it does not convert the paywall’s goal or change the customer’s Features. Keep using your provider’s access checks.

RevenueCat and Superwall Connectors feed Automations and server-side Journeys, without granting or maintaining Feature access today. Support for sending signed transactions from delegated checkout without finishing them, and for Feature access through Connector webhooks, is planned. Follow the purchase integration guide to configure the delegate and choose who finishes transactions.

Set up monetization

1. Connect your Product source and sync Products and prices.
2. Create Features and grant them from Products.
3. Add purchase actions to an Experience.
4. Connect the purchase actions to your chosen checkout integration. Use Nuxie Feature checks with Nuxie’s store checkout, or your provider’s access checks with provider-managed checkout.
5. Publish the Experience and test a purchase in the store’s test environment.

Choose the access model that fits what you’re selling:

• Boolean Features unlock a capability while the customer has an active grant. Use them for access such as premium content or offline mode.
• Metered Features give the customer units of one capability, such as 100 exports. Your app records usage as those units are spent.
• Credit systems provide a shared balance. Your app can charge different numbers of credits for different actions.

Products can grant fixed or unlimited usage. See Feature entitlements to create the Features and choose what each Product includes.

Paywalls

Use an Experience to explain your offer, let the customer choose a plan, and open checkout. The paywall’s prices and trial terms come from the selected store Product. On iOS, the SDK resolves those terms before showing the offer and uses the same Product for the purchase.

With Nuxie’s store checkout, Boolean and unlimited access can become available immediately on the device after a verified purchase. Fixed allowances and credits are confirmed by the server. See Paywalls to put the offer and purchase behavior together.

Feature access

Check a Feature’s key wherever your app needs to decide whether the customer has access. For example, in Swift:

// 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 an action with a usage allowance, include the number of units it requires:

// 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
}

Replace the sample keys with your own Feature keys. An access check reads the customer’s allowance without spending it. Before performing an action that costs units or credits, use useFeatureAndWait() and check the result’s success field. Each SDK reference includes the equivalent methods for its platform.

Purchase lifecycle

For Nuxie’s store checkout, access follows the purchase, including renewals, cancellations, and restores. Purchases and subscriptions explains those changes and the current limits for existing billing providers. To try the full path from purchase to access, follow Verify iOS purchases.

Your team’s Nuxie subscription, credits, and attributed-revenue fees are covered in Workspace billing.