You built an app in an afternoon with Cursor, Claude Code, or Lovable. It works. Users are signing up. Now comes the hard part: getting paid.

This is the exact moment where most vibe-coded apps die. RevenueCat now powers in-app purchases for over 50% of all AI-built iOS apps (Source), and AI-referred signups surged to over 35% of all new RevenueCat customers in Q2 2025. That means thousands of vibe coders have already solved this problem — and this playbook shows you exactly how.

The Monetization Gap Is Real

The data is stark. According to multiple 2025 analyses, vibe-coded apps struggle with monetization despite the AI coding boom (Source). The State of Vibe Coding 2025 report found that 63% of vibe coding users are non-developers (Source). These creators can build functional apps but often lack the experience to implement subscription billing, configure App Store products, or set up entitlement logic.

RevenueCat eliminates this gap with three tools that work together:

  1. The MCP Server — Configure your entire subscription backend using natural language in your AI coding tool
  2. Paywalls — Drop in pre-built, customizable paywall UI with zero design work
  3. Web Billing — Sell subscriptions on the web and avoid the App Store's 30% cut (for eligible U.S. users)

Phase 1: Set Up RevenueCat MCP in Your AI Coding Tool (5 Minutes)

The RevenueCat MCP Server enables AI assistants to manage subscription apps, products, entitlements, and everything in-between without requiring direct dashboard access. It provides 26 different capabilities for complete subscription management through natural language interactions (Source).

For Cursor Users

Add RevenueCat MCP to your project's mcp.json:

{
    "servers": {
        "revenuecat": {
            "url": "https://mcp.revenuecat.ai/mcp",
            "headers": {
                "Authorization": "Bearer {your API v2 token}"
            }
        }
    }
}

Cursor supports OAuth authentication, meaning you can authenticate seamlessly without managing API keys manually (Source).

For Claude Code Users

Add the server via the CLI:

claude mcp add --transport http revenuecat https://mcp.revenuecat.ai/mcp --header "Authorization: Bearer YOUR_API_V2_SECRET_KEY"

For VS Code Copilot Users

Add to your VS Code mcp.json:

{
    "servers": {
        "revenuecat-mcp": {
            "url": "https://mcp.revenuecat.ai/mcp",
            "type": "http"
        }
    },
    "inputs": []
}

VS Code also supports OAuth authentication for seamless setup (Source).

Getting Your API Key

  1. Open your RevenueCat dashboard
  2. Navigate to your project's API Keys page
  3. Create a new API v2 secret key and copy it
  4. Use a write-enabled key if you plan to create/modify resources (Source)

Pro tip: Every new RevenueCat project comes with a Test Store automatically configured, so you can start immediately without connecting to Apple or Google (Source).

Phase 2: Configure Your Subscription Products with Natural Language (10 Minutes)

This is where the magic happens. Instead of navigating dashboards and reading documentation about product configuration, you talk to your AI assistant.

The MCP usage examples show how natural language maps to RevenueCat operations (Source):

Step 1: Create Your App

Tell your AI assistant:

Create a new iOS app called "My Awesome App" with bundle ID com.mycompany.awesomeapp

Step 2: Create Subscription Products

Create a monthly subscription product called "Pro Monthly" priced at $9.99 for my iOS app

Create an annual subscription product called "Pro Annual" priced at $79.99 for my iOS app

Step 3: Create Entitlements

Entitlements define what your users unlock when they pay:

Create an entitlement called "pro_access" with display name "Pro Access"

Step 4: Wire Products to Entitlements

Attach the Pro Monthly and Pro Annual products to the pro_access entitlement

Step 5: Create an Offering

Offerings organize your products for display:

Create a new offering called "default" and add packages for monthly and annual subscriptions

Step 6: Verify Everything

Show me the complete configuration for my default offering including all packages and their attached products

You can perform all of these operations in sequence with a single batch prompt (Source):

Create a new iOS app called "My Awesome App", then create monthly and annual 
subscription products, create an entitlement called "pro_access", and attach 
both products to it. Finally, create an offering with packages for both.

Phase 3: Add the SDK and Paywall to Your App (10 Minutes)

Now tell your AI coding agent to integrate RevenueCat into your app. Here's the pattern that works:

The Prompt That Works

Give your AI assistant this context:

I need to add RevenueCat subscriptions to my app. Here's what I need:

1. Install the RevenueCat SDK (use the latest version)
2. Initialize Purchases with my public API key on app launch
3. Add a paywall using RevenueCat's pre-built paywall UI
4. Gate my premium features behind the "pro_access" entitlement
5. Add a restore purchases button

My public API key is: [YOUR_PUBLIC_KEY]
My entitlement identifier is: "pro_access"

What the SDK Does

The RevenueCat SDK seamlessly implements purchases and subscriptions across platforms while syncing tokens with the RevenueCat server. The SDK will automatically fetch your configured Offerings and retrieve product information (Source).

Checking Subscription Status

The core pattern for gating content is checking CustomerInfo:

Check if the current user has an active "pro_access" entitlement.
If they do, show the premium content.
If not, present the paywall.

The SDK makes it easy to check what active subscriptions the current customer has by checking a user's CustomerInfo object to see if a specific Entitlement is active. This method pulls from cache and runs very fast (Source).

Using Pre-Built Paywalls

RevenueCat provides customizable paywall templates that you can configure remotely — no app update required. See Creating Paywalls to design your paywall, then Displaying Paywalls for platform-specific implementation (Source).

The paywall includes a built-in "Restore Purchases" button, which Apple requires in the event a user loses access to their purchases (Source).

Phase 4: Add Web Billing to Keep More Revenue (5 Minutes)

Here's the move most vibe coders miss: you can sell subscriptions on the web and avoid the App Store's 30% commission for eligible U.S. users.

In April 2025, a U.S. District Court ruling found Apple in violation of a 2021 injunction meant to allow developers to direct users to external payment options, like Web Billing. iOS developers are now permitted to guide users to web-based payment flows without additional Apple fees or restrictive design requirements (Source).

RevenueCat Web Billing Features

RevenueCat Web Billing provides (Source):

  • Web SDK: A JavaScript SDK to integrate web purchases into your web app
  • Web Purchase Links: A hosted, customizable purchase flow — enable web purchases with no code
  • Web Purchase Button: Link to a web checkout from in-app (app to web)
  • Web Paywalls: Component-based dynamic paywalls, rendered on the web
  • Redemption Links: Let anonymous users purchase on the web and redeem in-app via deep linking

If you don't have a web app, Web Purchase Links give you a hosted, customizable purchase flow that you can distribute from emails, social media, or a landing page (Source). This is perfect for vibe coders who want to start collecting payments immediately.

Fee Comparison

RevenueCat Web is included in RevenueCat's pricing — there are no additional RevenueCat fees for web subscriptions. The only additional cost is the Stripe transaction fee (2.9% + 30¢), compared to Apple's 30% or Google's 15-30% (Source).

That's a 27% revenue increase on every web subscription.

Cross-Platform Entitlements

The best part: web purchases sync with the same entitlements on mobile. A user who buys on the web gets instant access in your iOS and Android apps. RevenueCat Web provides tools that allow you to easily start selling subscriptions on the web, and connect them with the same subscriptions and entitlements on mobile (Source).

Phase 5: Test and Launch (5 Minutes)

Test with the Built-In Test Store

Every new RevenueCat project comes with a Test Store. Test Store purchases work immediately without any additional setup, behave just like real subscriptions, and no real money is charged (Source).

Verify in the Dashboard

When a purchase is complete, you can find it associated with the customer in the RevenueCat dashboard. RevenueCat always validates transactions — Test Store purchases are validated by RevenueCat; real store purchases are validated by the respective platform (Source).

Go Live Checklist

  • [ ] Products configured in RevenueCat (via MCP or dashboard)
  • [ ] SDK initialized with public API key
  • [ ] Paywall displaying correct offerings
  • [ ] Entitlement checks gating premium features
  • [ ] Restore purchases working
  • [ ] Web Billing configured (optional but recommended)
  • [ ] Real store products created in App Store Connect / Google Play Console

What You Just Built

In roughly 30 minutes, you've gone from a vibe-coded app to a fully functioning subscription business with:

  • Server-side receipt validation — no server code required
  • Cross-platform subscription management — iOS, Android, and web
  • Pre-built paywall UI — remotely configurable
  • Web billing — keep 97% of revenue instead of 70%
  • Analytics and metrics — MRR, churn, LTV out of the box

RevenueCat handles the subscription infrastructure so you can stay focused on your idea. That's the same pattern that's powering over 50% of AI-built iOS apps today.

Next Steps

Sources