Skip to content
Engineering deep-divesAll articles

RevenueCat vs Adapty in 2026: Paywalls, MTR & Mobile TCO

Engineering and 36-month TCO teardown of RevenueCat vs Adapty in 2026 alongside Superwall: 1% MTR vs MAR double-tax traps, StoreKit 2 JWS verification, US App Store Stripe web-to-app link-outs, and owned entitlement ledgers.

Artem Zaitsev
Artem ZaitsevCTO · Idealogic
Author: Artem ZaitsevPublished: Updated: Reading time: 20 minHow we write →
On this page
Idealogic 2026 engineering comparison of RevenueCat vs Adapty and Superwall covering 1% MTR billing, remote paywall experiments, StoreKit 2 JWS verification, US Stripe web-to-app checkout, and 36-month TCO

RevenueCat vs Adapty is usually the first billing decision a subscription app makes after it finds paying users. A sprint or two later, marketers comparing Adapty vs RevenueCat start asking about a remote campaign tool, and Superwall vs RevenueCat lands in the architecture review too.

Our guides on iOS app development cost, React Native app development cost, Flutter app development cost and Android app development cost model full app budgets (the mobile app development cost guide has the cross-platform view). This teardown covers one slice of the RevenueCat vs Adapty question: subscription infrastructure, remote paywalls and post-2025 external web checkout economics. A 1% Monthly Tracked Revenue (MTR) fee is easy to ignore at $8,000/mo. At $150,000/mo, RevenueCat alone costs $18,000 a year, Superwall stacked on 80% of revenue pushes that to $32,400, and around then you cross Apple's $1M Small Business Program threshold, where first-year subscription commissions go from 15% to 30%.

At Idealogic, our mobile app development, iOS app development, React Native app development, and custom software development teams deploy RevenueCat, Adapty, Superwall, and owned StoreKit 2 + Play Billing + Stripe engines across social and creator economy, fintech, and healthtech apps. Below: the comparison, an Apple JWS V2 + Stripe + Play RTDN TypeScript and PostgreSQL blueprint, and a 36-month TCO ledger at $150,000/mo. Still choosing a stack? Start with how to build a mobile app and React Native vs Flutter.

Pick RevenueCat for SDK reliability and exports, Adapty for paywall iteration speed and built-in refund defense.

The short version

  • RevenueCat leads on SDK reliability and data exports. RevenueCat pricing is $0 up to $2,500 MTR, then 1% of total MTR on Pro, which replaced the legacy 1.2% Pro rate. Enterprise is negotiated. Paywalls, Experiments and Web Billing are bundled.
  • Adapty leads on visual paywall velocity and refund defense: Adapty pricing is $0 up to $5,000 MTR (down from $10k), then 1% MTR on Pro, plus 0.2% MTR for its Apple CONSUMPTION_REQUEST Refund Saver (1.2% combined).
  • Avoid the Superwall + RevenueCat double tax of up to ~1.8%. Superwall moved new accounts from $0.20 per conversion to 1% of Monthly Attributed Revenue (MAR) above $10k, so stacking it on RevenueCat charges converted dollars twice.
  • US web-to-app Stripe checkouts change the margin math. After the April 2025 Epic v. Apple order, US apps can route iOS buyers to Stripe Billing web checkouts. In our model that cuts an assumed 24% blended App Store fee to about 4%. EU Digital Markets Act (DMA) link-outs also work, but Apple still takes a commission there.
  • At $150k/mo MTR, over 36 months, an owned billing stack ($73,500) beats Superwall + RevenueCat ($130,200) by $56,700 and Adapty + Saver ($82,800) by $9,300. It roughly ties RevenueCat Pro ($72,000), runs $7.5k/yr after Year 1, and saves $432,000 in App Store fees on 40% of revenue moved to US web checkout.

RevenueCat vs Adapty vs Superwall: 2026 subscription architecture internals

RevenueCat and Adapty are subscription infrastructure SDKs that validate store receipts, keep entitlements in sync and run remote paywalls. Both charge 1% of monthly tracked revenue above a free threshold ($2,500 RevenueCat, $5,000 Adapty). Superwall is a paywall and campaign layer on top.

The hard part is state. An iPhone user buys an annual trial on the subway, cancels auto-renew, upgrades through a US web promo link two weeks later, then opens an iPad and expects instant access everywhere.

Four commercial and architectural boundaries separating RevenueCat, Adapty, Superwall, and owned cross-platform entitlement engines in 2026

1. RevenueCat: cross-platform receipt ledger, Web Billing and data exports

RevenueCat hides the Apple, Google, Amazon, Roku and Stripe state machines behind one CustomerInfo object:

  1. Flat 1% MTR above $2,500. SDK and growth tools are free up to $2,500 MTR. Above that, Pro charges 1% of gross MTR (before store commissions and VAT). Enterprise pricing is negotiated; RevenueCat doesn't publish the discount.
  2. Paywalls, Experiments and integrations. You get native SwiftUI/Compose remote paywalls and price Experiments, and integrations include retention flows, data exports and attribution partners.
  3. Web Billing: wraps Stripe Checkout to grant mobile entitlements. Web revenue counts toward tracked MTR, so the same 1% applies on top of Stripe's 2.9% + $0.30 (check RevenueCat's Billing terms).

2. Adapty vs RevenueCat: visual paywall builder, LTV cohorts and 0.2% Refund Saver

Teams weighing Adapty vs RevenueCat tend to pick Adapty when fast paywall iteration drives paid UA:

  1. $5,000 free, then 1% MTR. The old $10k free tier and Pro/Pro+ brackets are gone; Pro bills 1% of gross MTR, with custom Enterprise plans.
  2. A no-code paywall builder with LTV cohort analytics. Marketers ship hero layouts, timers, localization and onboarding quizzes over the air without waiting on App Review, and run price A/B tests on them.
  3. Refund Saver (+0.2% MTR): answers Apple CONSUMPTION_REQUEST notifications with usage data for an extra 0.2% MTR above $5k, 1.2% total.

3. Superwall vs RevenueCat, plus post-2025 US and EU web-to-app steering

  • Superwall vs RevenueCat (MAR + MTR stacking): Superwall is strong on behavioral campaign triggers. It bills 1% of MAR above $10,000/mo (Indie $0 base, Startup $49/mo, Scale $199/mo, Enterprise custom). Run Superwall paywalls on top of RevenueCat's PurchaseController and, if 80% of revenue flows through them, you pay about 1.8% of gross revenue (1% MTR plus 1% on that 80%).
  • US injunction and EU DMA external checkout. The April 2025 Epic Games v. Apple contempt order barred Apple's 27% US link-out fee and scare screens. The Ninth Circuit affirmed the contempt finding in December 2025 but reversed the outright ban on any commission and sent it back to the district court. US apps now pair native Apple StoreKit 2 with external Next.js + Stripe Billing + Apple Pay web checkouts: 0% Apple commission under the current order, plus Stripe fees of about 4% on larger tickets.

Watch the remand. 0% holds under the current order only. The district court can allow a narrower commission and further appellate review is pending, so model a non-zero Apple fee as your downside case.

EU link-outs aren't free. Under Apple's DMA terms for apps in the EU, link-outs still pay Apple a commission. Check current rates there before modeling EU revenue; the savings math below is US only.

RevenueCat vs Adapty at a glanceRevenueCatAdapty
Price1% of total MTR on Pro; Enterprise negotiated1% of total MTR on Pro; custom Enterprise
Free tierUp to $2,500 MTRUp to $5,000 MTR
PaywallsNative Paywalls + ExperimentsNo-code visual builder + A/B tests
Refund defenseWebhook data, partner hooksRefund Saver add-on (+0.2% MTR)
ExportsData export integrationsWebhooks and ETL integrations
Monetization dimensionRevenueCat (2026)Adapty (2026)Superwall (2026)Owned (StoreKit 2 + RTDN + Stripe)
Free developer threshold$2,500 MTR ($0/mo)$5,000 MTR ($0/mo)$10,000 MAR (Indie $0/mo)Unlimited ($0 MTR/MAR tax)
Paid revenue take rate1.0% total MTR (Ent. negotiated)1.0% total MTR (Pro)1.0% MAR (+$49/$199 base; legacy $0.20/conv)$0 platform % (~$250/mo AWS)
Stacked w/ RevenueCatBaseline 1.0% MTRRarely stacked (1.0% MTR)Up to ~1.8% combined tax (80% attributed)Replaces both (0.0% tax)
Remote Paywall BuilderNative Paywalls v2 + ExperimentsDeep visual builder + LTV cohortsBest trigger/campaign rulesTokenized RN/SwiftUI + PostHog
Apple Refund SaverWebhook data / partner hooksBuilt-in add-on (+0.2% MTR)Scale ($199/mo) refund guardNative sendConsumptionInformation ($0)
US / EU Web-to-App StripeHosted Web Billing (1.0% MTR)Stripe connector (1.0% MTR)Web checkout campaigns (1% MAR)Custom Next.js + Stripe (0% SaaS fee)
Data ownership & complianceData export integrationsWebhook / ETL streamsDashboard SQL + webhooksIn-VPC Postgres 17 + PCI DSS v4.0.1

Owned entitlement ledger for Apple JWS V2, Google Play RTDN and Stripe

Owning entitlements is far less painful than in the verifyReceipt days, because Apple, Google and Stripe all send signed server notifications:

  1. Apple StoreKit 2: App Store Server Notifications V2 and the App Store Server API sign transactions as JWS payloads verified via @apple/app-store-server-library, binding purchases to your user UUID through appAccountToken.
  2. Google Play: Google Play Billing Library binds obfuscatedAccountId and delivers Real-Time Developer Notifications (RTDN) via Cloud Pub/Sub. Treat an RTDN as a signal and call the Play Developer API for the authoritative state, keyed on the latest purchaseToken.
  3. US / EU Web-to-App: Stripe Webhooks (customer.subscription.updated, invoice.paid, charge.refunded) verify HMAC payloads with client_reference_id.

We write all three feeds into one PostgreSQL 17 or 18 entitlement table protected by Row-Level Security. Six design decisions carry most of the weight:

Design decisionEnforced inWhat it prevents
One row per store subscription, keyed by tenant, source (Apple, Play or Stripe web) and the store's subscription IDDatabaseSplit brain across platforms: one query tells you whether a user is premium on iOS, Android and web
Event IDs go into a dedup table first, in the same transaction as the entitlement writeDatabaseDouble grants, since Apple, Play and Stripe all deliver at least once and retry
Every upsert is fenced on a monotonic event timestampDatabaseA late DID_FAIL_TO_RENEW overwriting a newer DID_RENEW or invoice.paid during a retry storm
FORCE RLS plus a restrictive tenant policy, and the worker never runs as a superuser or BYPASSRLS roleDatabaseCross-app or cross-workspace leaks, because PostgreSQL ORs permissive policies together when someone adds a support-read policy later
JWS, HMAC and Play Developer API checks run before any writeApp workerForged or stale payloads changing access
Refund defense replies only with recorded consentApp workerBreaking Apple's consent rule for consumption data

Two vendor details bite in practice. Apple reports price in milliunits of the transaction currency, so store the currency next to the amount instead of assuming two decimals. And the Send Consumption Information request fields differ between library versions, so check the ConsumptionRequest type in the version you install. The multi-tenant side is covered in our multi-tenant SaaS architecture guide.

The part that replaces Adapty's 0.2% Refund Saver is short. Apple sends a CONSUMPTION_REQUEST and you have 12 hours to answer. Your worker answers through the App Store Server API's sendConsumptionInformation call, and only when the customer agreed to share usage data: no consent on the user record means no call. The refund preference you send (for example decline) follows your own refund policy.

Consent comes first. Apple's Send Consumption Information docs say to respond only when the customer has consented to share consumption data. Store that consent on the user record and skip the call when it's missing.

Stripe web checkouts and Play purchases (keyed on the latest linked purchaseToken) land in the same table behind the same timestamp fence. One query for active or grace-period rows with a future expiry then unlocks premium features on iOS (Swift), Android, React Native and web.

Paying 1% to 1.8% in MTR fees or leaving App Store commission savings on the table?
Share your Monthly Tracked Revenue, iOS/Android split, and paywall stack. Our mobile architects will model your US/EU Stripe web-to-app checkout funnel and 36-month entitlement TCO.
Model your subscription & web-to-app ROI

Worked 36-month TCO and US web-to-app arbitrage at $150,000/mo MTR ($5.4M gross)

Take a consumer or prosumer subscription app making $150,000/mo in Monthly Tracked Revenue ($1.8M a year, $5.4M over 36 months) across iOS, Android and web. At $1.8M/yr, two things are true:

  1. You're well past every free tier: RevenueCat's $2.5k, Adapty's $5k and Superwall's $10k.
  2. You've left Apple's Small Business Program. Above $1M a year in proceeds, first-year subscription commission goes from 15% to 30% (15% after year one). We assume a 24% blend for a roughly 3-year cohort mix; that's our model, not an Apple number.

Labor uses Idealogic's own rates: $75/hr senior CEE versus $165/hr US domestic agency (2.2x). For context, Eurostat puts the 2025 EU whole-economy average labour cost at EUR 34.9/hr, and O*NET tracks US software developer (15-1252.00) wages:

  1. Option A: Superwall + RevenueCat Pro Stacked ($150k/mo MTR; 80% = $120k/mo Superwall MAR):
    • Initial setup (80 hrs @ $75/hr CEE = $6,000; vs $165/hr US = $13,200): Dual SDK bridge (PurchaseController), Superwall campaign triggers, and RevenueCat webhooks.
    • 36-month stacked SaaS fees ($2,700/mo x 36 = $97,200): RevenueCat Pro 1.0% MTR ($1,500/mo) + Superwall 1.0% MAR on $120,000/mo paywall conversions ($1,200/mo on $0 Indie base; add $199/mo if using Scale), plus 10 hrs/mo (360 hrs) ops reconciling dual attribution ($27,000 CEE / $59,400 US) = $130,200.
  2. Option B: Adapty Pro + Refund Saver ($150k/mo MTR):
    • Initial setup (60 hrs @ $75/hr CEE = $4,500; vs $165/hr US = $9,900): Adapty SDK, remote Paywall Builder placements, App Store .p8 key, and webhook sync.
    • 36-month 1.2% MTR fees ($1,800/mo x 36 = $64,800): Adapty Pro 1.0% MTR ($1,500/mo) + Refund Saver 0.2% MTR ($300/mo), plus 5 hrs/mo (180 hrs) paywall & SDK ops ($13,500 CEE / $29,700 US) = $82,800.
  3. Option C: RevenueCat Pro ($150k/mo MTR):
    • Initial setup (60 hrs @ $75/hr CEE = $4,500; vs $165/hr US = $9,900): Purchases SDK, Paywalls v2, Customer Center, Web Billing link, and S3 exports.
    • 36-month 1.0% MTR fees ($1,500/mo x 36 = $54,000): 1.0% of $150,000/mo ($18,000/yr), plus 5 hrs/mo (180 hrs) ops ($13,500 CEE / $29,700 US) = $72,000. A negotiated Enterprise contract would lower this, but RevenueCat doesn't publish those rates, so we don't model one.
  4. Option D: Owned Cross-Platform Entitlement & US/EU Web-to-App Engine (StoreKit 2 JWS + Play RTDN + Stripe Billing + PostHog) built by Idealogic:
    • Build (680 hrs @ $75/hr CEE = $51,000; vs $165/hr US = $112,200): Apple V2 JWS verification + Google Play RTDN + custom Next.js/Apple Pay Stripe Billing web-to-app funnel, PostgreSQL 17 FORCE RLS ledger, server-driven paywall JSON + PostHog A/B experiments, and native sendConsumptionInformation Refund Saver.
    • 36-month AWS ECS/RDS/PubSub infra ($250/mo x 36 = $9,000): Webhook workers ($90/mo), Multi-AZ Postgres 17 + Redis ($110/mo), GCP Pub/Sub + WAF ($50/mo), and PostHog 1M free events ($0) at $0 MTR tax, plus 5 hrs/mo (180 hrs) store SDK ops ($13,500 CEE / $29,700 US) = $73,500.
Worked 36-month billing infrastructure TCO ($k) at $150k/mo MTR ($5.4M gross): Owned Stack beats Stacked by $56.7k, beats Adapty + Saver by $9.3k, and drops Year-2+ run-rate to $7.5k/yr
36-month line item ($150k/mo MTR = $5.4M gross)Option A: Superwall + RCOption B: Adapty + SaverOption C: RevenueCat ProOption D: Owned Billing StackPrimary economic driver
1. Initial build & setup (@ $75/hr CEE)$6,000 (80h; $13.2k US)$4,500 (60h; $9.9k US)$4,500 (60h; $9.9k US)$51,000 (680h; $112.2k US)Option D builds JWS, RTDN, Stripe Web & Refund bot
2. 36-mo MTR / MAR fees or AWS$97,200 ($2,700/mo)$64,800 ($1,800/mo)$54,000 ($1,500/mo)$9,000 ($250/mo AWS)Eliminates 1.0% to 1.8% gross revenue tax
3. 36-mo paywall & SDK ops (@ $75/hr)$27,000 (10h/mo; 360h)$13,500 (5h/mo; 180h)$13,500 (5h/mo; 180h)$13,500 (5h/mo; 180h)Single ledger avoids MAR/MTR attribution drift
36-Month Billing Infra TCO (CEE)$130,200$82,800$72,000$73,500 (CapEx incl.)Saves $56,700 vs Stacked; ties RC Pro at 36m
Year-2+ Annual Infra Run-Rate$41,400/yr$26,100/yr$22,500/yr$7,500/yrCuts ongoing annual run-rate by 66.7% to 81.9%
36-mo Store Fee on $2.16M Shifted US Web$518,400 (if 100% IAP)$518,400 (if 100% IAP)$108,000 (4% Stripe + 1% RC)$86,400 (4% Stripe, 0% MTR)Saves $432,000 vs corporate IAP (+$21.6k vs RC Web)

US web-to-app commission math: where the $432,000 comes from

The money sits in the bottom row. Say your owned US checkout moves 40% of $150,000/mo ($60,000/mo, or $2,160,000 over 36 months) off StoreKit 2. At the assumed 24% blend (30% Year 1, 15% after), Apple would take $518,400 of it. On a 1-tap Apple Pay + Stripe Billing web checkout at about 4% in Stripe fees (2.9% + $0.30 per charge, plus Stripe Billing's 0.7%, so smaller tickets pay more) and 0% Apple link-out fee under the current US order, you pay $86,400 instead:

  • Net savings: $518,400 minus $86,400 is $432,000 ($12,000/mo). That pays back the $51,000 CEE build in 4.25 months (9.35 months at $112,200 US rates). Fair warning: a US commission on remand shrinks this, and EU traffic doesn't qualify.
  • Owned web vs RevenueCat Web Billing: web revenue counts toward RevenueCat's tracked MTR, so the same 1% on $2,160,000 adds an estimated +$21,600. It also limits B2B seat, bundle and dunning flows and deepens vendor lock-in. At $350k/mo MTR, Option D saves $70,500+ on 36-month infra TCO alone versus RevenueCat Pro.

2026 subscription, paywall and web-to-app build costs (senior CEE vs US)

Creator apps add payout wrinkles (see creator monetization platforms). Our iOS app development, React Native app development, and custom software development squads deliver subscription monetization builds at $75/hr senior CEE versus $165/hr US agency rates:

Engagement tierTimelineHoursSenior CEE ($75/hr)US Agency ($165/hr)Scope & deliverables
RevenueCat or Adapty Launch2 to 3 wks160 to 240h$12,000 to $18,000$26,400 to $39,600StoreKit 2 / Play SDK, remote paywalls, trials & MMP attribution
US & EU Web-to-App Funnel4 to 6 wks280 to 440h$21,000 to $33,000$46,200 to $72,600Next.js + Stripe Apple Pay checkout, deep-link return & compliance
Owned Billing Engine (680h)8 to 12 wks600 to 880h$45,000 to $66,000 ($51k)$99,000 to $145,200 ($112.2k)Apple JWS V2, Play RTDN, Stripe Web, PG17 RLS & PostHog A/B
Multi-App Enterprise Vault12 to 18 wks960 to 1,400h$72,000 to $105,000$158,400 to $231,000Portfolio SSO entitlements, BigQuery LTV warehouse & PCI DSS v4.0.1
Dedicated Monetization PodOngoing240h/mo (2)From $18,000/moFrom $39,600/moSenior Swift/RN + TypeScript billing & conversion engineers

Inside the worked 680-hour ($51,000 CEE vs $112,200 US) owned billing engine

Worked model, assumptions in text: 680-hour ($51,000 at $75/hr CEE vs $112,200 at $165/hr US) owned StoreKit 2 JWS, Google Play RTDN, US/EU Stripe Web-to-App & PostHog paywall stack
  • 1. StoreKit 2 JWS V2 & Play RTDN (30% / 204 hrs / $15,300 CEE vs $33,660 US): Swift/Kotlin/RN purchase wrappers, @apple/app-store-server-library SignedDataVerifier, Cloud Pub/Sub RTDN consumers, grace periods, and win-back offers (mobile app development).
  • 2. US & EU Stripe Billing Web-to-App (25% / 170 hrs / $12,750 CEE vs $28,050 US): Next.js checkout with 1-tap Apple Pay / Google Pay, Stripe Tax, Universal Link session handoff, and compliant steering UI.
  • 3. PG17 Ledger & FORCE RLS (20% / 136 hrs / $10,200 CEE vs $22,440 US): Idempotent webhook event table, monotonic event-timestamp fencing, a restrictive tenant-isolation policy, and Redis cache.
  • 4. Server Paywalls & PostHog A/B (15% / 102 hrs / $7,650 CEE vs $16,830 US): Remote JSON paywalls, multivariate price/trial flags via PostHog, and Meta CAPI / Apple Ads server events.
  • 5. Refund Saver and no-churn cutover (10% / 68 hrs / $5,100 CEE vs $11,220 US): CONSUMPTION_REQUEST sendConsumptionInformation bot plus dual-read shadow migration importing originalTransactionId and purchaseToken mappings without forced renewals.

Use RevenueCat or Adapty through your first fifty thousand dollars in monthly recurring revenue; they save two sprints when survival depends on shipping your core loop. Avoid stacking Superwall atop RevenueCat past scale, and build your owned StoreKit 2 plus Stripe web-to-app checkout as you approach Apple's one-million-dollar Small Business cliff.

Artem Zaitsev · CTO at Idealogic

RevenueCat vs Adapty: 5-step CTO decision checklist and shipped proof

Idealogic runs mobile billing, compliant payment rails and real-time entitlement ledgers in production:

These five checks cover most 2026 subscription stacks:

  1. Under $50,000/mo MTR and want turnkey entitlements? Pick RevenueCat ($0 up to $2.5k, then 1% MTR).
  2. Paid-UA app at $5k to $100k/mo MTR, shipping no-code paywall tests every week? Pick Adapty ($0 up to $5k, then 1% MTR).
  3. Using Superwall triggers? Run Superwall's own StoreKit wrapper alone rather than paying both 1% MAR and 1% RevenueCat MTR.
  4. Passing roughly $85k to $100k/mo gross on iOS (Apple's $1M Small Business threshold counts proceeds, not gross) with US iOS users? Launch a Next.js + Stripe Billing web-to-app funnel. Expect up to ~20 points of fee reduction on the revenue that moves to web.
  5. At $150k+/mo MTR or running several apps? Deploy an owned StoreKit 2 + Play RTDN + Stripe engine ($250/mo AWS, no MTR tax). Contact our team for a 48-hour TCO audit.

So, RevenueCat vs Adapty? Below $50k/mo, pick whichever fits your team; the 1% fees match unless you add Adapty's Refund Saver. Adapty vs RevenueCat becomes a real cost question once you stack Superwall or cross Apple's $1M threshold. That's when to price an owned stack.

Planning RevenueCat / Adapty setup, US Stripe web-to-app checkout, or an owned entitlement migration?
Send your current MTR volume, iOS/Android split, and paywall goals. Our senior mobile and billing architects will return a concrete blueprint and fixed-milestone quote within 48 hours.
Request a mobile billing estimate

Occasional field notes on building software, no spam

Protected by Cloudflare Turnstile · Privacy · Terms

Artem Zaitsev
Artem ZaitsevCTO · Idealogic Development OÜ

CTO and Co-founder at Idealogic. Directing engineering, systems architecture, security, and full-stack delivery across web, mobile, and blockchain.

Frequently asked questions

  • Pick RevenueCat when SDK reliability and data exports top your list. Pick Adapty when growth marketers want to ship no code paywall tests every week and get built in Apple refund defense. Both cost 1 percent of tracked revenue past the free tier, so it usually comes down to who owns the paywall.

  • Both charge 1 percent of Monthly Tracked Revenue above a free threshold, measured on gross billings before store commissions and taxes. RevenueCat is free up to $2,500 in monthly tracked revenue and charges 1 percent of total MTR on Pro above $2,500; Enterprise pricing is negotiated and isn't published. Adapty is free up to $5,000 MTR (replacing legacy $10,000 free and fixed Pro+ tiers) and charges 1 percent MTR above $5,000 plus 0.2 percent for its Refund Saver add on.

  • Teams often add Superwall for paywall triggers while keeping RevenueCat underneath for entitlements. Superwall dropped $0.20 per conversion pricing and now charges 1 percent of Monthly Attributed Revenue above $10,000 on Indie (plus $49 on Startup or $199 on Scale). Stacking both taxes every Superwall converted dollar twice. If 80 percent of revenue comes through Superwall paywalls, that works out to roughly 1.8 percent of gross revenue; it only reaches 2 percent when every dollar is Superwall attributed.

  • In the US, the April 2025 Epic Games v. Apple contempt order lets iOS apps link out to a Stripe Billing web checkout without Apple's 27 percent fee. The Ninth Circuit upheld the contempt finding in December 2025 but sent the total commission ban back to the district court, so a narrower fee could return. EU link-outs under the Digital Markets Act still pay Apple a commission. Either way you need one backend ledger that reconciles Apple JWS V2 notifications, Google Play RTDN events and Stripe webhooks under one user ID.

  • When an iOS subscriber asks Apple for a refund, Apple sends a CONSUMPTION_REQUEST through App Store Server Notifications V2 and gives you 12 hours to reply with Send Consumption Information. Only reply if the customer consented to sharing that data; skip the call otherwise. Done right, it helps push back on abusive refund claims without a 0.2 percent add on.

  • Apple, Google Play RTDN and Stripe all promise at least once delivery, not ordering. During retry storms an older DID_FAIL_TO_RENEW can land right after a newer DID_RENEW or invoice.paid. Deduplicate event IDs and fence updates behind a monotonic last_event_ms column inside a row locked PostgreSQL transaction.

  • Yes. The subscriptions live in App Store Connect, Google Play Console and Stripe, not in RevenueCat or Adapty. You export historical appAccountToken and latest purchaseToken mappings (Play can issue a new linked token on plan changes or resubscribes), point App Store V2 and Play RTDN webhooks at your own endpoint with dual read shadow verification, then ship an app update that reads entitlements from your API. Nobody gets rebilled.

  • Below $50,000 per month in tracked revenue, RevenueCat Pro or Adapty Pro at $0 to $500 per month is almost always cheaper than maintaining your own. At $150,000 per month ($5.4 million over 36 months), an owned cross platform entitlement and US web to app Stripe checkout engine costs $51,000 for a 680 hour senior CEE build ($112,200 at $165 per hour US rates), beats stacked Superwall plus RevenueCat by $56,700, cuts Year 2+ run rate to $7,500 per year, and saves $432,000 in App Store fees.

Still unanswered
Ask us directly

A senior engineer replies under 4 hours.

Related expertise