Contents
- The Core Rule: Digital Goods vs. Physical Goods and Services
- How StoreKit and Google Play Billing Work
- Stripe, PayPal and Others for Physical Goods and Services
- Security and Regulation: PCI DSS, SCA and GDPR
- Step by Step: The Integration Process
- Effort, Cost and Common Mistakes
- Conclusion
- Frequently Asked Questions
Before integrating in-app payments, answer one question: are you selling digital content or physical goods and real-world services? That decides whether Apple and Google require their own billing systems or whether you can freely choose a provider such as Stripe, PayPal or Adyen. This guide covers the rules, the technical building blocks and the mistakes we see most often.
The Core Rule: Digital Goods vs. Physical Goods and Services
Apple's App Store Review Guidelines and Google Play's payments policy essentially distinguish two cases:
- Digital content and features consumed in the app – premium features, content subscriptions, virtual currencies, unlocked levels or online courses. Both stores generally require their own billing (In-App Purchase or Google Play Billing).
- Physical goods and services delivered in the real world – an online shop, food delivery, event tickets, ride-hailing or booking a tradesperson. Here you may, and should, use external payment providers such as Stripe, PayPal, Adyen, Mollie or Klarna.
There are special cases in between: "reader" apps (magazines, music), enterprise software licensed outside the app, or one-to-one live services. In addition, the EU Digital Markets Act and court rulings in several countries have led Apple and Google to allow alternative payment methods or links to external offers under certain conditions – often with their own fee models. These rules change regularly, so check the current policies before you start. Our article on the Digital Markets Act and alternative app stores gives more background.
How StoreKit and Google Play Billing Work
With in-app purchases, the store handles the entire payment process: card management, tax calculation, receipts and refunds. You create products in App Store Connect or the Google Play Console and load them in the app via StoreKit (iOS) or the Play Billing Library (Android). There are three product types:
- Consumables: credits or game currency that can be bought repeatedly.
- Non-consumables: one-time unlocks such as a pro version.
- Subscriptions: recurring payments with free trials, introductory offers, upgrades and downgrades.
Store commissions typically range from 15 to 30 percent depending on the programme, product type and subscription duration; smaller developers and long-running subscriptions often qualify for the reduced rate. Factor this into your pricing before committing to a business model – see app monetization: subscription, freemium, ads or one-time purchase.
Technically, never rely on the app alone. Validate purchases on your server and process the stores' server notifications (App Store Server Notifications on iOS, Real-time Developer Notifications on Google Play). That is the only reliable way to learn about renewals, cancellations, refunds and billing failures. Services such as RevenueCat or Adapty can take this off your hands, at the price of extra fees and another dependency.
Stripe, PayPal and Others for Physical Goods and Services
Shops, booking apps and marketplaces integrate a payment service provider (PSP). The most common options in Europe:
| Provider | Strengths | Typical use |
|---|---|---|
| Stripe | Excellent developer docs, native SDKs, many payment methods, subscription logic, marketplace features (Connect) | Startups, SaaS, marketplaces, booking apps |
| PayPal / Braintree | High recognition and customer trust, PayPal checkout | E-commerce, PayPal-loving audiences |
| Adyen | Wide coverage of international payment methods, including point of sale | Larger merchants, omnichannel retail |
| Mollie | Quick setup, European payment methods | SMEs, online shops |
| Klarna | Invoice, instalments, "pay later" | Merchants with larger baskets |
Most apps combine one PSP with several methods: cards, Apple Pay, Google Pay, PayPal and SEPA direct debit. Apple Pay and Google Pay noticeably improve mobile conversion because users don't have to type card details. Fees vary by provider, method and volume – request current terms and model them against your expected basket size.
Security and Regulation: PCI DSS, SCA and GDPR
- PCI DSS: the card industry's security standard. If you use the PSP's prebuilt payment forms and SDKs, card data never touches your servers – you only receive a token, which drastically reduces your compliance scope. Never build custom card fields that send numbers to your backend.
- Strong Customer Authentication (SCA) under PSD2: online card payments in the European Economic Area often require two-factor confirmation, usually via 3-D Secure. Modern PSP SDKs handle this, but your app must cope with the intermediate step (confirming in the banking app, then returning to yours).
- GDPR: put the required agreements in place with your PSP, list it in your privacy policy and store only what you need. Our GDPR checklist for apps helps.
This is a technical overview, not legal advice. Marketplaces that collect money on behalf of third parties face additional regulatory questions – solutions like Stripe Connect or Adyen for Platforms exist precisely for that.
Step by Step: The Integration Process
- Clarify the business model: what is sold, one-off or recurring, to consumers or businesses? This tells you whether in-app purchases are required.
- Choose a provider: compare payment methods, countries, fees, payout schedules and marketplace features.
- Model the payment flow: create order, authorise payment, confirm via webhook, unlock the service, send the receipt. Include partial payments, cancellations and refunds.
- Make the backend the single source of truth: order status is set only server-side from webhooks, never from a message sent by the app.
- Build in idempotency: webhooks may arrive twice or out of order; every handler must detect duplicates.
- Test in the sandbox: successful payments, declines, abandoned 3-D Secure, renewals and refunds.
- Connect accounting: exports or an API link to your accounting software, correct VAT and invoice numbers.
- Monitor: failed payments and webhook errors should trigger alerts before customers complain.
Effort, Cost and Common Mistakes
The effort depends less on the SDK than on the business logic behind it. A simple one-off payment via Stripe Checkout or a single in-app subscription is manageable. It gets demanding with marketplaces (commissions, payouts to sellers), tiered subscriptions with coupons and trials, or when web and app subscriptions must be managed together.
As a rough guide based on our price ranges: apps with login, payments and API integration for iOS and Android typically cost EUR 15,000–50,000 and take two to four months. Complex marketplace platforms start at around EUR 50,000. AI-assisted development can cut time and cost by up to 40 %, for example on standard integrations and tests. For shop-specific figures, see the cost of an e-commerce app.
Common Mistakes
- Selling digital content via Stripe and getting rejected in app review.
- Checking entitlements only on the client – easy to manipulate and error-prone.
- No plan for cancellations, refunds and chargebacks.
- Web and app subscriptions out of sync, so customers pay twice or lose access.
- Thinking about VAT on cross-border EU sales too late.
- No dunning process for failed renewals, such as expired cards.
Conclusion
Payments in an app are not just an SDK task but a combination of store rules, business model, security and backend logic. First determine whether in-app purchases are mandatory, then choose a provider that fits your audience, and let the backend own payment status and entitlements. If you are planning an app with payments, request a fixed-price offer after a free analysis via our offer wizard.
Frequently Asked Questions
Can I use Stripe instead of in-app purchases?
For physical goods and real-world services, yes; for digital content and features used in the app, Apple and Google generally require their own billing. The EU and some other markets now allow exceptions under specific conditions, which you should check before starting.
Does my app need PCI DSS certification?
If you use a payment provider's hosted forms and SDKs, card data never reaches your servers and your compliance effort is minimal. Avoid custom forms that send card data to your backend.
How high are app store commissions?
Apple and Google typically keep between 15 and 30 percent, depending on programme, revenue and subscription duration. Check the stores' current terms for exact rates.
How long does a payment integration take?
A simple one-off payment can often be built in a few days; subscription models or marketplaces with payouts to third parties usually need several weeks including testing.