Purchases and subscriptions

Track checkout, subscription changes, and customer access.

Nuxie keeps track of what your customers have purchased and what those purchases unlock. With Nuxie’s store checkout, verified purchases and store subscription updates keep Feature access current. If your app uses an existing billing provider, keep using that provider’s access checks.

This means your app can ask “Can this customer export?” without deciding which subscription, lifetime purchase, or credit pack gives them access. Apple and Google remain the merchant of record for purchases made through their stores.

Feature access

Use the SDK’s Feature checks to decide what a customer can do. Nuxie combines their active grants, including access from more than one Product.

A customer who cancels renewal may still have the rest of their paid month left. Someone whose monthly subscription expires might also own a lifetime plan. Checking the Feature accounts for those sources together instead of relying on one subscription’s status.

Boolean and unlimited access tell you whether a capability is available. Fixed allowances also tell you how much the customer has left. Feature entitlements explains how to configure each.

Checkout

Your Experience presents the offer and opens checkout with the store or configured billing provider. The customer buys the Product selected on the paywall, with the price and offer terms shown to them.

With Nuxie’s store checkout, Boolean and unlimited access can become available immediately after a verified purchase. Fixed quotas, credit balances, and deductions wait for server confirmation, so the app doesn’t let a customer spend units that haven’t been granted yet.

App Store purchases

The paywall uses current Product information from StoreKit, including the price and offer available to that customer. With Nuxie’s checkout and no purchase delegate, Nuxie saves and sends the signed purchase to verify it and update access and balances. This also works in .observer mode, where your app finishes the transaction. If the store reports the same transaction again, Nuxie recognizes the existing purchase.

Match the Nuxie Product’s processor ID to its StoreKit product identifier. See App Store Connect for store setup and Purchases (SDK) for the app integration.

Google Play purchases

The customer checks out through Google Play Billing. Nuxie verifies the purchase with Google, matches it to the Product or subscription base plan in your catalog, and grants the included Features.

Configure subscription notifications as well as purchase reporting. They let Nuxie receive renewals and other changes while the app is closed. The Google Play guide covers both.

Existing billing providers

If your app already uses a purchase provider, you can keep its checkout and restore flow. Configure the SDK to send the Experience’s purchase and restore requests to that integration.

With RevenueCat, Superwall, or a custom purchase delegate, Nuxie receives only the checkout outcome. A successful purchase can complete the Journey, but no receipt is saved or sent from the device, so the paywall’s goal does not convert and the customer’s Features do not change. Keep using your provider’s access checks.

RevenueCat and Superwall Connectors feed Automations and server-side Journeys. They do not grant or keep Feature access current today. Support for sending the signed store transaction from delegated checkout without finishing it, and for Connector webhooks that grant and maintain Feature access, is planned. The SDK purchase guide explains checkout and transaction finishing.

Identify the signed-in customer with the same ID in Nuxie and your billing provider before checkout. Otherwise, a successful purchase can be associated with a different customer from the one your app checks for access.

Purchase outcomes

Connect each checkout outcome to the experience you want the customer to have. A completed purchase might close the paywall; cancellation might leave it open; a failure might offer a retry.

Pending payment is still waiting for completion. Keep paid Features locked until your access check confirms they are available. If the Product can’t be loaded, use your unavailable or retry path rather than substituting another offer’s terms.

Restore purchases

Add a restore action for customers who already own a Product, such as someone reinstalling your app. With Nuxie’s store checkout, Nuxie asks the store for their purchases and updates the access those purchases provide. With a purchase delegate, the provider handles restoration and Nuxie receives only the restore outcome. That outcome does not update Nuxie Feature access.

Restoring recovers ownership. It doesn’t create a new sale or count as a new-subscription conversion just because access returned. With Nuxie’s store checkout, Boolean and unlimited access can be restored locally; fixed quotas and credits still use the server’s current balance. With a purchase delegate, read access from your provider.

Subscription lifecycle

For purchases through Nuxie’s store checkout, store notifications keep Nuxie up to date between app visits. The device picks up access changes when its profile refreshes. These access updates do not apply to checkout handled by RevenueCat, Superwall, or a custom purchase delegate.

Billing retry also follows the store’s state and access policy. Keep store notifications active so Nuxie can receive those changes. For provider-managed checkout, your provider keeps access current; its Connector supplies events for Automations and server-side Journeys. Connector updates to Nuxie Feature access are planned.

Spending quota or credits is a separate operation. Checking access tells you what’s available; consuming usage deducts the amount used.

Integration

Start with Products and prices to connect your catalog, then add Feature entitlements. The iOS purchase walkthrough takes you through a purchase and restore in an installed app.