If your app sells goods, delivery or services that people use outside the app, you cannot charge for them through Apple and Google in-app purchase — you need a card payment via Click, Payme or Apple Pay. If you sell access to features inside the app, the rule is the opposite: both stores allow subscriptions and paid sections to be paid for only through their own in-app purchase.
Key takeaways
The payment method is chosen by store rules rather than by the business, and those rules turn on one question: where does the customer use what they bought. A purchase consumed outside the app goes around in-app purchase; anything that unlocks capabilities inside the app goes only through it.
Apple states it plainly: if an app lets people buy physical goods or services that will be consumed outside of the app, you must use purchase methods other than in-app purchase to collect those payments, such as Apple Pay or traditional credit card entry (App Store Review Guidelines, clause 3.1.3(e)).
The flip side is clause 3.1.1 of the same guidelines. To unlock features or functionality within the app — subscriptions, levels, access to premium content, a full version — you must use in-app purchase, and your own unlocking mechanisms such as licence keys or QR codes are banned. Certificates get their own line: digital gift cards, vouchers and coupons redeemable for digital goods may be sold in the app only through in-app purchase, while physical gift cards mailed to the customer may use other methods.
Google Play follows the same logic, but spells out the exceptions as a list. Google Play's billing system must not be used when the payment is primarily for the purchase or rental of physical goods, for physical services such as transportation, cleaning, airfare, gym memberships, food delivery or live event tickets, for a credit card or utility bill remittance, or for peer-to-peer payments, online auctions and tax exempt donations (Google Play payments policy).
| What you sell | App Store | Google Play | How the customer pays |
|---|---|---|---|
| Goods with delivery, food, on-site services, event tickets | In-app purchase not allowed | Google Play billing not allowed | Card via Click, Payme or Uzum Bank, Apple Pay |
| Subscription to app features, paid sections, in-app currency | In-app purchase only | Google Play billing only | Store account, money arrives as a payout |
| Utility bills, credit card bill remittance, a transfer to another person | In-app purchase not allowed | Google Play billing not allowed | Card via a local provider |
| Gift card: digital for digital goods, or physical with delivery | Digital by in-app purchase, physical by other methods | Digital falls under no exception, physical is a good, so billing is not allowed | Store account or card, depending on what you sell |
The wording in both documents is precise, and both are revised over time. Check your own case against the current version through the links at the end of this article: the «in-app purchase or card» decision is made once and is expensive to redo.
Important The rule covers more than the payment button. If access to a paid section is unlocked by a key or QR code bought elsewhere, the App Store treats that as a violation even when you take no money inside the app.
The rate depends on the store and on the developer's earnings. Apple reduces it for members of its small business programme: 15% on paid apps and in-app purchases for developers whose proceeds across all their apps in the prior calendar year did not exceed 1 million USD, and for developers new to the App Store. If the threshold is passed during the current year, the standard commission rate applies to future sales (App Store Small Business Program).
For markets outside the US, the European Economic Area, the UK, Japan and Australia, Google Play charges 15% on the first 1 million USD of earnings each year and 30% above that; subscriptions stay at 15% regardless of revenue (Google Play service fees).
That is why the type of purchase is settled before development rather than after release: the store fee applies to every subscription and every payment for access inside the app, while a local provider's acquiring works on the terms of your contract with it.
The difference in rules matters more than the difference in platform shares. Android runs on most devices in Uzbekistan and is the platform with a ready-made library, so it is the easier place to start. Apple is the stricter reviewer, though, so the payment flow is designed against App Store requirements from the outset: otherwise the iPhone version has to be rebuilt along with the backend.
With both providers, payment acceptance rests on the server: the app never talks to the bank directly, it passes the order to your server, and the provider confirms payment through your server's methods. Ready-made mobile libraries exist only for Android with both of them.
Click is connected through the Shop API scheme: your server implements the Prepare and Complete requests, after which the service can be paid for in any Click interface — its own app, the web account, USSD or a bot. Separately there is the Merchant API with a data fiscalisation section, and web payments: a payment link and card payment (Click documentation).
For Android, Click publishes the android-msdk library, which embeds the payment screen directly in the app. Its configuration takes the service identifier, the merchant identifier, the user's identifier in your system, the amount and the interface language; the library is pulled in through the JitPack repository and needs internet permission. The description notes separately that a provider with its own billing can do without the library, but will still have to implement the Shop API on the app's server (android-msdk on GitHub).
Payme has two protocols. The Merchant API handles core payment acceptance: the provider calls your server's methods to check, create, perform and cancel a transaction. The Subscribe API covers work with the customer's card and recurring charges, and it is the one an app needs when the card is saved once.
The page on mobile app integration describes the Android SDK this way: the library provides the client-side interface and the card methods from the Subscribe API, while you implement the card and receipt methods on the server side (Payme Business). The library returns the payment result to the app without card data: a masked number, the expiry date, a payment token and flags for recurring payment and SMS verification. The app passes the token to its own server, which completes the payment through the Subscribe API.
Mistake Planning the iOS version around a ready provider SDK. Payme's public Android repository was archived by its owner on 2 August 2023 and is now read-only (PaycomUZ on GitHub), and the Click organisation has no iOS library at all. The iPhone version is built on the provider's server methods and payment page, not on a mobile library.
On iOS the payment flow has three parts: your server creates the invoice, the app opens the provider's payment page, and the server receives confirmation and changes the order status. The provider shows the payment screen, so card data never reaches the app.
Step six is where the logic usually breaks. A parameter in the return address only says that the person closed the payment page, and it is easy to forge. The source of truth is your server after the provider's call. How to split responsibility between the app and the backend is covered in the article on the backend and API for a mobile app.
Apple Pay in an app does not replace acquiring: the payment still runs through your provider, and Apple only supplies the card and the owner's confirmation. For the «goods and services outside the app» case, Apple's rules name Apple Pay directly as an acceptable payment method.
Payment in an app is not a single screen but an order state that the customer sees after closing the app too. The minimum you have to design looks like this.
Save the transaction identifier next to the order the moment it arrives: it is what you search by when a dispute is investigated and a refund is issued. The same rule applies to a web platform's payment flow, described in the article on billing and payment acceptance on a web platform.
If sales already run through a messenger, there is no need to move them into the app wholesale: a bot and an app serve different customer habits. How order acceptance with payment works in Telegram is covered in the article on taking orders in a Telegram bot with Click and Payme.
Most rejections come not from the code but from a payment method that does not match the type of purchase. The reviewer opens the payment screen and compares it with the rule.
Another common cause is a mismatch between the store listing and what happens on screen. If the listing promises a subscription and the app asks for a card, the build will not pass. What else is checked before publication is collected in the article on publishing an app in the App Store and Google Play.
Go through this list before the build goes to review: it covers both the store rules and the technical side.
Syntra Systems starts projects like this not with code but with a look at the sales: what exactly the customer buys and where they use it. The answer decides what becomes in-app purchase and what goes to Click, Payme or Uzum Bank, and what the payment flow on the server looks like.
Then we build the server side — orders, statuses, handling of provider notifications and protection against duplicate payments — connect the provider's library on Android and the payment page on iOS, work through the test environment on every scenario, and prepare the build so that the payment screen matches the store rules. What the work includes and how to discuss your task is shown in our service catalogue.
Let’s discuss your project
Tell us what you need, and we will estimate the timeline and cost and suggest a solution.
Yes, if everything you sell is received outside the app: goods with delivery, food, on-site services, tickets. As soon as the app offers paid access to its own features, that part of your sales will need the store’s in-app purchase.
Check this with the provider: in the Click and Payme documentation a mobile app is described as one more provider interface rather than a separate service. On the development side you reuse the server methods already implemented for the website, and the app adds the payment screen and result handling.
A parameter in the return address only means that the payment page has closed, and it is easy to forge. The only confirmation is the provider’s call to your server, after which the app asks the server for the new order status.
With the provider, not with you. At Payme the Subscribe API handles saving the card and recurring charges, and the app receives a masked number, the expiry date and a payment token. Card data must not pass through your server or be stored in the app.
You will run the subscription in both store systems at once, and your server has to reduce them to a single access state for the customer. Otherwise someone who bought a subscription on Android will not have it when they sign in from an iPhone.
For goods and services used outside the app this is a working scenario: the rules explicitly allow card entry. For paid access inside the app the workarounds are limited — Google’s alternative billing systems operate only in the countries included in the relevant programme.
As many as your customers actually use: a card through a local provider and, on iPhone, Apple Pay. Every method you add has to be taken through the test environment in full and maintained with each release.
Sources
Cover photo: Hasan Albari, Pexels