Purchases and paywalls

Build the access chain

1. Select the intended Test app.
2. Configure the billing provider and app mapping under Integrations.
3. In Catalog, create or inspect the product and its exact provider identifiers and prices.
4. Attach the project entitlement that the product should unlock.
5. Choose the supported paid-access policy under Auth → Paid access.
6. Create a paywall using the app’s catalog products.
7. Present it directly, or connect it to a placement and campaign.

The app must gate its feature using effective SDK access. Do not unlock from a button tap, a checkout redirect, a support email, or the existence of a historical transaction.

Direct presentation or campaigns

Direct presentation is appropriate for a known upgrade button or fixed onboarding step. The app owns when to show the creative.

A campaign is appropriate when One should choose an audience, schedule, or variant remotely. The app triggers a placement; the result may be a paywall, a surface, a custom payload, or no presentation. Handle the no-presentation result normally.

Placement fallback is explicit. Do not infer it from a campaign variant or a default-paywall flag. For iOS, generate the bundled app fallback from current One configuration for the exact submitted SDK version.

Verify purchases and restores

Use provider test facilities with disposable test customers. Check successful purchase, cancellation, pending purchase where supported, restore, subscription expiration, and relaunch. Confirm the exact product, verified transaction, effective entitlement, and visible app behavior.

For App Store access, account authentication and store ownership are separate. Signing into a support account is not purchase proof. See Paid access for the ownership model and compatibility limits.

Apple offers and pricing

Catalog includes Apple offer discovery and pricing previews for mapped apps. Review the exact provider preview, territory changes, subscriber-price policy, warnings, and operation result before treating a change as complete. Provider configuration and sandbox behavior do not establish production purchase acceptance.

An offer operation may need recovery if Apple created a batch but One did not finish importing it. Inspect the saved operation before requesting another batch.