Note:
The information in this article is provided as a general overview. Platform policies change over time, and the authoritative sources are the official documentation from each platform:
App Store Review Guidelines — Apple
Google Play Payments policy — Google
Always refer to these documents for the most up-to-date requirements before publishing your app.
Payments in native mobile apps work differently from payments on the web. While a web app can integrate with any payment processor and charge users directly, native mobile apps are subject to platform rules set by Apple and Google. Understanding these rules is essential when planning monetization for your mobile app.
Why mobile payments are different
Apple’s App Store and Google Play have strict policies on how apps can charge users for digital goods and services. Both platforms require that purchases of digital content, features, or subscriptions go through their own in-app purchase systems — Apple’s StoreKit and Google’s Play Billing. These systems handle the transaction, take a commission, and distribute the remainder to the developer.
This rule is enforced at the platform level. Submitting an app that bypasses these systems to charge users for digital goods will typically result in rejection during the review process.
When in-app purchases are required
In-app purchases are required for any digital goods or services consumed within the app. This includes:
Subscriptions to premium content or features
Unlocking app features or removing ads
Virtual currency or in-game items
Digital content such as articles, videos, or audio
The platform takes a commission on these transactions — typically 15% to 30%, depending on the developer’s agreement and revenue thresholds.
When in-app purchases are not required
Apple and Google allow external payment methods for certain categories of goods and services. These include:
Physical goods and services (such as ecommerce purchases or ride bookings)
Services consumed outside the app (such as a meal delivered or a ride taken)
Business-to-business transactions
Donations to nonprofit organizations
For these categories, you can use any payment processor, including Stripe, PayPal, or others integrated through Bubble’s API connector or plugins.
In-app purchases in Bubble
Bubble currently supports subscriptions through in-app purchases. This means you can offer recurring subscription products in your native mobile app and have them processed through Apple’s or Google’s billing systems. You can read more about in-app purchases in the article series below:
Article series: In-app purchases
Choosing a payment approach
When planning payments in your native mobile app, consider what you’re charging for:
If you’re selling digital subscriptions, use Bubble’s in-app purchase support.
If you’re selling physical goods or services consumed outside the app, you can use external payment processors like Stripe.
If your app combines both — for example, an ecommerce store with a premium subscription tier — you may need to use both approaches, with each transaction routed through the appropriate system.
Platform commission and pricing
The rates below are provided as a general overview and may change over time. Always refer to the official platform documentation for current rates and terms.
Apple and Google take a commission on all in-app purchases, which affects your pricing strategy. The standard rates are:
30% on most purchases in the first year of a subscription
15% on subscription renewals after the first year
Reduced rates for developers earning under a certain revenue threshold (currently $1 million per year)
Factor these commissions into your subscription pricing to ensure your revenue targets are met after the platform’s cut.
Testing in-app purchases
Both Apple and Google provide sandbox environments for testing in-app purchases without charging real money. Use these environments to verify that your purchase flows, subscription renewals, and cancellation handling work correctly before submitting your app for review.
FAQ: Payments in mobile apps
Why can’t I just use Stripe to charge for subscriptions in my mobile app?
Why can’t I just use Stripe to charge for subscriptions in my mobile app?
Apple and Google require all purchases of digital goods and services, including subscriptions to digital content or features, to go through their own billing systems. Using an external payment processor like Stripe for these purchases will typically result in app store rejection.
Can I use Stripe at all in my mobile app?
Can I use Stripe at all in my mobile app?
Stripe for mobile is not officially supported by Bubble as of now.
Technically, you can set up payments with any provider, but only for physical goods and services consumed outside the app. Examples include eCommerce purchases, food delivery, ride bookings, and event tickets.
Can I offer the same subscription on web and mobile?
Can I offer the same subscription on web and mobile?
Yes, but you’ll need to handle each platform’s billing system separately. Web subscriptions can use any payment processor, while mobile subscriptions must go through Apple’s or Google’s billing systems. Most apps maintain a single user account that recognizes subscriptions purchased on either platform.
Can I link to my website to let users subscribe there instead?
Can I link to my website to let users subscribe there instead?
Both Apple and Google have strict rules about steering users to external payment methods. The rules vary by region and have been changing in response to recent legal developments. Refer to the official platform documentation for current guidance.
What if my app is rejected for payment-related reasons?
What if my app is rejected for payment-related reasons?
The most common reasons for rejection are using external payment methods for digital goods, or failing to use the platform’s in-app purchase system where required. Review the platform’s payment guidelines carefully and update your app to comply before resubmitting.