How an in-app payment works
With a payment provider, the app embeds the provider's SDK, which draws the card form or opens Apple Pay or Google Pay. The SDK sends the payment details to the provider, the app's server confirms the payment, and any 3-D Secure challenge appears inside the app.
With store billing, the app calls the store's purchase API. The store charges the payment method on the user's store account, keeps its commission and pays the developer.
What Apple's and Google's rules say
Apple's App Review Guidelines, read on 13 October 2026, require in-app purchase to unlock features or content within an app (3.1.1). An app that sells physical goods or services consumed outside the app uses other methods, such as Apple Pay or card entry (3.1.3(e)).
Google Play's Payments policy requires Play's billing system for in-app digital features, content and services, and does not allow it for physical goods, physical services or peer-to-peer payments. Both stores list exceptions for particular storefronts, regions and programmes, and both sets of rules change often.
In-app payments in a fintech app
A top-up, a transfer or a card payment in a banking or card app moves the user's own money. Those flows run on the app's own payment rails, with strong customer authentication built into the app, and not on store billing.
Where an in-app payment shows up in a platform
Modules that do the work
- CheckoutA hosted checkout for cards, wallets, bank payments and crypto, routed to the best provider.
- AuthenticationSign-in, passkeys and second factors for customers and staff, on your identity provider or ours.
- Card acquiringCard acceptance on the phone, in store and online, through the acquirer you choose.
Platforms that need it
Where it is written
The laws and standards this page's facts come from.
General information, not legal advice: what applies to you depends on your services and your market.