How to Add Payments to Your App: Stripe, Apple Pay, and Google Pay

To add payments to your app, the rule is simple: sell physical goods or real-world services and you use a normal card processor like Stripe at about 2.9 percent plus 30 cents per transaction; sell digital goods or subscriptions consumed inside the app and you must use Apple App Store and Google Play Store in-app billing, which take roughly 30 percent (or 15 percent for small businesses). Apple Pay and Google Pay sit on top as faster checkout. Picking the wrong path can get your app rejected or quietly cost you a third of your revenue. The worldwide digital payments market is projected to reach 37.45 trillion US dollars in transaction value in 2026, according to Statista. This guide shows you exactly which payment method to use and when.

Key Takeaways

• Physical goods and real-world services use a standard processor like Stripe at about 2.9 percent plus 30 cents per successful card charge in the United States.
• Digital goods and subscriptions consumed in the app must use Apple App Store and Google Play Store in-app billing, which take about 30 percent, or 15 percent for qualifying small businesses.
• Apple Pay and Google Pay are not separate processors; they are fast, secure checkout layers that ride on top of your card processor.
• Marketplaces that pay out third-party sellers should use Stripe Connect to split payments and route payouts globally.
• Choosing the right path early protects both your store approval and your margins, so decide before you build, not after.

The One Question That Decides Everything

Before you write a line of payment code, answer this: what exactly is the customer buying, and where is it consumed? That single question determines which rails you are allowed and required to use.

If the customer buys a physical product or a service delivered in the real world, a ride, a cleaning, a meal, a hotel night, you process with a normal payment processor and Apple takes no cut. If the customer buys something digital that lives inside the app, a subscription, premium features, in-app currency, or digital content, Apple and Google require you to use their in-app billing systems and they take a commission. Getting this distinction wrong is the most common payments mistake we see, and it is one of the fastest ways to fail App Review. Our development team sorts this out during planning so nothing gets built twice.

Stripe for Cards, Services, and Physical Goods

Stripe is the default processor for selling physical goods and real-world services. Standard online card pricing in the United States is 2.9 percent plus 30 cents per successful card charge, with manually entered cards priced higher. Stripe handles the card data, fraud tooling, payouts to your bank, and the application programming interface (API) your app calls to take money. For ecommerce, on-demand services, marketplaces, and booking apps, this is the path, and Apple and Google do not take a commission because the value is delivered outside the app.

Stripe also gives you tools that matter as you grow: subscription billing for real-world services, invoicing, tax handling, and fraud prevention. Because it is so widely used, almost any developer can integrate it cleanly, which keeps both build cost and long-term maintenance reasonable.

Apple Pay and Google Pay: Faster Checkout, Not a Separate Processor

People often assume Apple Pay and Google Pay are alternative payment processors. They are not. They are accelerated, secure checkout methods that sit on top of your processor. When a customer taps Apple Pay or Google Pay, the card on file is passed through to Stripe (or your processor of choice) and charged at the same processing rate. The win is conversion: no typing card numbers, biometric confirmation, and far less checkout friction, especially on mobile.

Our dining-membership partner Mangia Rewards is a clean example. Members subscribe to monthly or annual plans through Apple Pay and Google Pay, which makes signing up nearly effortless on a phone, while luxury partners distribute unique codes for extended memberships. The lesson: offer Apple Pay and Google Pay anywhere customers check out, because removing friction directly lifts completed purchases.

In-App Billing for Digital Goods and Subscriptions

If you sell digital goods or subscriptions consumed inside the app, Apple App Store and Google Play Store require you to use their in-app purchase systems. The standard commission is about 30 percent. Apple’s App Store Small Business Program drops that to 15 percent on paid apps and in-app purchases for developers earning up to 1 million US dollars in proceeds per year. Google Play applies a similar structure, with a 15 percent service fee on the first 1 million US dollars of earnings each year and 30 percent above that, and Google is further restructuring fees in 2026 with lower rates for subscriptions.

This commission is non-negotiable for in-app digital sales, so design your pricing and your product with it in mind from the start. Many subscription apps build that commission into their pricing rather than letting it erode margin after launch. If you want the deeper mechanics, see our guide on mobile app development.

Marketplaces: Splitting Payments and Paying Out Sellers

If your app is a two-sided marketplace, you are not just collecting money, you are routing it to third parties. That is where Stripe Connect comes in. Connect lets your platform take a payment, keep your fee, and pay out the seller, driver, host, or provider, with support for splitting funds and sending payouts across 118-plus countries. It handles onboarding and verification of your sellers too, so you are not building banking infrastructure yourself.

For marketplaces selling physical goods or real-world services, this is the standard card-rail path and Apple takes no cut. The key is to plan the money flow, who gets paid, when, and after what conditions, before you build, because rework here is expensive.

When to Use Which Payment Method

What you are selling	Use this	Typical cost	Apple or Google commission?
Physical goods (ecommerce, retail)	Stripe (cards), plus Apple Pay and Google Pay for checkout	About 2.9% + 30 cents per charge	No
Real-world services (rides, cleaning, dining, bookings)	Stripe, plus Apple Pay and Google Pay	About 2.9% + 30 cents per charge	No
Marketplace payouts to sellers or providers	Stripe Connect	Processing plus Connect fees	No (for physical goods and services)
Digital goods and in-app subscriptions	Apple App Store and Google Play Store in-app billing	About 30% (15% small business)	Yes (required)
Faster mobile checkout (any card sale)	Apple Pay and Google Pay on top of your processor	Same as your processor rate	No (it is just checkout)

Plan Payments Before You Build

The costliest payment mistakes happen when teams build first and check the rules later. Map your money flow during planning: what is sold, where it is consumed, who gets paid, and which fees apply. That single exercise tells you whether you are on card rails or in-app billing, what your real margins look like, and how to price. It also keeps you on the right side of App Review. This is exactly the kind of decision our proven process locks down early, and it is part of what we do for you as a product partner.

Frequently Asked Questions

Does Apple take 30 percent of all payments in my app?

No. Apple only takes a commission on digital goods and subscriptions consumed inside the app, at about 30 percent, or 15 percent under the Small Business Program. Physical goods and real-world services processed through a normal card processor like Stripe owe Apple nothing, because the value is delivered outside the app rather than as digital content.

Is Apple Pay a payment processor I integrate instead of Stripe?

No. Apple Pay and Google Pay are checkout methods, not processors. They pass a stored card to your actual processor, such as Stripe, which charges it at the normal rate. You still integrate Stripe to move money; Apple Pay and Google Pay simply make the checkout faster and more secure, which improves conversion on mobile devices.

What does Stripe cost in 2026?

Stripe’s standard online card pricing in the United States is about 2.9 percent plus 30 cents per successful charge, per Stripe’s pricing page. Manually entered cards cost more, and marketplace payouts through Stripe Connect carry additional fees. Always confirm current rates directly with Stripe, since pricing and available products can change over time.

How do marketplace apps pay their sellers?

Marketplaces use Stripe Connect, which collects the buyer’s payment, keeps your platform fee, and routes the rest to the seller, driver, or provider. Connect supports splitting payments and global payouts across many countries, and it handles seller onboarding and verification so you do not have to build banking infrastructure yourself.

Can I avoid Apple and Google fees on digital subscriptions?

Generally no. If the subscription unlocks digital content or features inside the app, Apple and Google require their in-app billing and the associated commission. Trying to route around it usually causes rejection. The practical move is to build the commission into your pricing and, where eligible, enroll in the small business programs to pay 15 percent instead of 30.

Should I offer both Apple Pay and Google Pay?

Yes, on the relevant platform. Offer Apple Pay to iPhone users and Google Pay to Android users wherever they check out for card-based purchases. Both reduce friction dramatically by removing manual card entry, which lifts completed-purchase rates. They cost the same as your underlying processor, so there is little downside to supporting them.

Let’s Build Payments That Protect Your Margins

Payments are where a lot of apps quietly lose money or run into store rejections. Whether you are a new founder pricing your first product or an existing company adding or fixing payments in an app already in market, we help you get it right, with the correct rails for what you sell, clean Stripe, Apple Pay, and Google Pay integrations, and a money flow that holds up as you scale. Chop Dawg is a partner, not an agency: you work directly with our senior, United States-led product and engineering team, backed by in-house design and development teams in Brazil, Pakistan, and India, you own all of your code, and you budget on a fixed monthly rate. Enterprise organizations that have trusted Chop Dawg include Siemens and Hilton. We have earned 300-plus five-star reviews across trusted directories like Clutch, GoodFirms, G2, Google, and TopDevelopers. Book your free 45-minute consultation and we will map your payment strategy together, no obligation.