Monetization

Contrast supports two payment providers, each connected per project in Project Settings → Integrations:

• RevenueCat for native subscriptions and in-app purchases on iOS.
• Stripe for web checkout and web subscriptions.

Connecting a provider does three things at once:

1. Your agents learn the integration. Connecting installs a skill into the project that teaches agents the production patterns: one app-owned subscription row as durable truth, webhook-first reconciliation, a single access-policy helper, and stable plan and entitlement identifiers. An app built by an agent after you connect gets a real subscription architecture, not just a paywall screen.
2. The native preview sells your real products. With RevenueCat connected, the simulator’s built-in store mirrors your project’s actual offerings, packages, products, prices, and entitlements. You tap Subscribe in the browser preview, the purchase completes, and the entitlement unlocks, with no device, no sandbox account, and no App Store Connect setup. See Testing purchases in preview.
3. Revenue shows up in the workspace. A verified provider feeds the Revenue pane in the Production section and the MRR chip in the left bar: monthly recurring revenue, 7/30/90-day revenue, active subscriptions, and trials, broken down by platform.

#The path to a paid app

• Build and test free. Connect RevenueCat, let an agent add the paywall and subscription model, and run the whole purchase flow in preview. Nothing here requires an Apple Developer account.
• Ship. When you are ready for the App Store, real products must exist in App Store Connect and RevenueCat needs Apple credentials. That setup, and the review pitfalls that reject most first submissions, are covered in Shipping paid apps.
• Web checkout is independent: connect Stripe and deploy. Contrast registers the Stripe webhook for your production deploy automatically.

#Where things live