In-App Payments for Physical Goods: Using Your Own Processor
In-app payments for physical goods can generally run through your own processor, not Apple or Google billing. See the rules and how to build the checkout.

Photo: Pixabay
On this page 6 sections
Key takeaways
- Sort every product by where it's used. Things used outside the app generally go through your processor, and things used inside the app generally go through platform billing.
- Apple Pay in an app is a card wallet that settles through your merchant account. It is a separate system from Apple's in-app purchase billing.
- Your app's API is a card-testing target. Give it the same rate limits and velocity rules as your web checkout.
- Run the app and website on one gateway, one customer vault, one descriptor and one set of fraud rules.
If your app sells shoes, groceries, meal kits, auto parts or anything else that ships or gets picked up, Apple's and Google's current policies generally don't require you to use their billing systems, and those sales generally aren't subject to the platform commission. In-app payments for physical goods can run through your own merchant account and payment gateway, the same way your website checkout does. Apple and Google built their in-app billing for digital content used inside the app. Physical goods, and services delivered in the real world, sit outside that requirement under current policy.
Most of the confusion comes from that line between physical and digital, and so do most of the savings. The sections below cover how to sort each product, then how to build the checkout: SDKs, wallets, saved cards, fraud controls, and keeping the app consistent with your website. Treat the policy discussion as general information. Platform rules change, so confirm the current text before each release.
App Store Rules: Physical Goods vs. Digital Content
Apple's App Store Review Guidelines and Google Play's Payments policy both separate two kinds of purchases.
The first is digital content or features unlocked inside the app: premium tiers, extra levels, in-app subscriptions. The platform's own billing usually applies to these, along with its commission. The second is physical goods, and services consumed outside the app. Both platforms generally expect you to take payment for these with your own payment method. A clothing order, a food delivery, a hotel booking and a plumber's service call all fall in this second group. This is the reason the question "does Apple in-app purchase apply to physical goods" has a short answer under current policy: generally, no.
Rules for digital goods have been shifting because of U.S. litigation and EU regulation, and those changes are mostly about digital content. Apps that sell physical products haven't been the target of the platform billing requirement. Both companies revise their policies, though. Read the current text of Apple's guidelines and Google's Payments policy before you submit, and keep a dated copy of the version you relied on.
A Quick Test for What's in the Cart
Ask where the buyer uses what they paid for. If they use it outside the app, your processor typically handles the sale. If they use it inside the app, expect platform billing.
| What the customer buys | Where it's used | Who typically processes the payment |
|---|---|---|
| Sneakers shipped to their door | Outside the app | Your merchant account |
| Takeout order for pickup | Outside the app | Your merchant account |
| Booked haircut or fitness class | Outside the app | Your merchant account |
| Ad-free mode or premium recipes in the app | Inside the app | Platform billing, generally |
| Membership mixing shipping perks with in-app content | Both | Gray area; check current guidelines before launch |
The last row is where apps get flagged in review. A loyalty membership that only discounts shipping on physical orders is a different product from one that also unlocks exclusive in-app videos. If your membership does both, expect the reviewer to ask about it.
Worked Example: A Coffee Roaster's App With Two Checkouts
This case is illustrative, not a real merchant. A roaster's app sells two things: a monthly bean subscription shipped to the customer, and a paid video course on brewing that streams inside the app.
The beans are physical goods. They go through the roaster's own gateway, and the card is saved as a stored credential for the monthly charge. The course is digital content consumed in the app, so it goes through platform billing. The two purchases need separate flows. Keep them out of a single cart, and don't fold the course into the bean price to route it around platform billing. That breaks the platform's rules and can put the whole app at risk of rejection or removal.
Routing In-App Payments for Physical Goods Through Your Processor
To the card networks, an in-app card payment is an e-commerce transaction. The customer's card isn't at a terminal, so the sale is card-not-present and priced that way, even though it starts on a phone. Our explainer on why online card fees cost more than in-store sales covers what that means for your rates.
To accept payments in a mobile app, you need the same two pieces a website needs. One is a merchant account, the banking relationship that lets you accept cards. The other is a gateway, which carries each transaction from your app to the processor. If those terms still blur together, read payment gateway vs. merchant account before you meet with developers.
Tell your processor about the app channel during underwriting. Suppose your application describes only a website, and then app orders show up with a different product mix, ticket size or set of shipping destinations. That mismatch can trigger a review. MannyPay sets up online payment processing for e-commerce merchants and supports gateways including Authorize.net and NMI. Ask your gateway provider directly what mobile tools it offers.
Mobile App Payment SDKs, Apple Pay, and Google Pay
A mobile app payment SDK is a code library your gateway provides for iOS and Android. It collects the card number inside your app and immediately swaps it for a token, a stand-in value that is useless if stolen. Your servers only see the token. That keeps raw card data off your systems, and it keeps your PCI DSS scope much smaller than it would be if your backend received card numbers. (PCI DSS is the security standard every card-accepting business follows.)
Developers usually choose one of two approaches:
- Native SDK fields. Card entry looks and behaves like the rest of your app. This takes more build work, and it usually gives repeat buyers the best experience.
- A hosted payment page in a web view. The gateway's page loads inside the app. It ships faster, but it can feel clunky, and the styling won't always match.
Apple Pay in an app is a different system from Apple's in-app purchase billing. Apple Pay is a wallet. The customer's tokenized card and a one-time cryptogram go to your gateway, and the sale settles through your merchant account like any other card payment. Setup generally involves registering a merchant identifier in your Apple Developer account and creating a payment processing certificate that your gateway uses to decrypt the payment data. Google Pay in an app follows a similar pattern: you configure the Google Pay API to hand a token to your gateway. Check the current steps in Apple's and Google's developer documentation, and ask your gateway whether it handles the certificate work for you.
Wallets matter more in apps than on the web. Typing a 16-digit card number on a phone keyboard is where many mobile checkouts stall. Our guide to adding Apple Pay, Google Pay and PayPal to your checkout covers the web side of the same decision.
Saving Cards Securely for One-Tap Reorders
Shopping apps make their money on repeat orders, and saved cards make those orders quick. Store the card in your gateway's vault, not in your own database. Your app keeps a customer ID and a token reference, and the gateway holds the card.
Many merchants get one point wrong. You can't keep the CVV on file and reuse it, because PCI DSS doesn't permit merchants to store the card security code after authorization. Your gateway or PCI assessor can confirm how that applies to your setup. If you want an extra check on a reorder, use the phone's own authentication, such as Face ID or a fingerprint, to confirm the account owner is the one ordering. Don't build a CVV workaround.
Visa and Mastercard also have rules for stored credentials. These are network rules, not one processor's pricing. Broadly, they cover getting the customer's agreement to save the card and labeling each charge correctly as an initial or later stored-credential transaction. Your gateway handles much of that labeling, so ask your processor for the current requirements and how they apply to your checkout. Subscriptions, like the roaster's monthly beans, may carry more disclosure and cancellation requirements under network rules and some state laws. Those vary by network and jurisdiction, so check with your processor and a qualified attorney. This is general information, not legal advice.
Ask your gateway about network tokens as well. The card networks issue these tokens, and they can update automatically when a customer's card is reissued. That can reduce the "card expired" failures that break reorder flows.
Fraud Signals Unique to Mobile App Orders
Apps give you fraud signals a website lacks, and they open a few gaps a website doesn't have.
The most useful extra signal is the device. A device identifier shows you when one phone has created eight accounts in a week to collect first-order promo codes. It also shows when a long-standing account logs in from a new device, changes the shipping address and adds a new card within minutes. That second pattern is classic account takeover. Apple and Google both offer device-integrity checks that help you tell a real install from an emulator or a tampered app.
The gap is your app's API. Bots don't have to tap through your interface. They can call the endpoints your app uses directly, including the "add a card" endpoint, which makes it an easy target for card testing. Put the same rate limits and velocity rules on your app API that protect your web checkout. Our breakdown of stopping card testing attacks covers the controls that work.
Address and security-code checks still apply, and our guide to which AVS and CVV mismatches to decline holds for app orders as well as web orders. For high-ticket orders, 3-D Secure has an app-based flow that some gateways support. On successfully authenticated transactions, card network rules can generally shift liability for fraud-related chargebacks to the card issuer. It doesn't cover every dispute type, so confirm the details with your processor. MannyPay offers 3-D Secure authentication for online checkouts.
Keeping App and Web Checkout in Sync
Customers don't see your app and your website as two separate stores, and your payment setup shouldn't treat them that way. Keep these consistent across both channels:
- One customer vault. A card saved on the website should appear in the app, and the reverse. That only works if both channels share the same gateway and customer records.
- One billing descriptor. The name on the card statement should match no matter which channel the order came from. An unfamiliar descriptor is a common source of "I don't recognize this charge" disputes. See how your billing descriptor causes chargebacks.
- One set of fraud rules. If the website declines a risky address combination and the app approves it, fraudsters will find the app.
- One refund and cancellation policy. Show it in the app before purchase, not only on the website.
- Tagged order sources. Record whether each order came from the app or the web. Then you can match payouts to orders and compare chargeback rates by channel. Our guide to reconciling processor payouts to store orders shows how.
Before your next app release, list every product and membership the app sells, and mark each one as consumed outside the app or inside it. Items in the first group are generally candidates for your own processor. Check anything ambiguous against the current Apple and Google guidelines before you change the payment flow. When you're ready to price the merchant account and gateway side, request a free quote from MannyPay, and a specialist will respond within one business day.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


