Which Payment Integration Does Your App Need?
Choosing a payment gateway or in-app purchase for a mobile app starts with what the customer buys. For digital access used inside the app, check the store’s current billing requirements before choosing an integration. For physical goods and services delivered outside the app, assess a payment gateway against your checkout and fulfilment needs, then confirm the applicable store rules.
What exactly is the customer buying?
Describe each purchase in one sentence: “The customer pays for ___, and receives it ___.”
A paid feature, a delivered product and an appointment are different purchases, even when all three appear behind a Buy button. Classify them separately before discussing payment providers.
Use this table to organise the decision. It is a planning guide; confirm the permitted payment route against current store documentation.
| Purchase | Example | Question to resolve first |
|---|---|---|
| Digital access | Unlocking an advanced feature | Which billing route does the store require or permit? |
| Digital subscription | Continued access to an app library | How will renewals and access changes be confirmed? |
| Physical goods | A product delivered to an address | How will payment connect to stock, delivery and refunds? |
| Offline service | A repair appointment | When should payment happen relative to booking and completion? |
| Service delivered online | A remote session | How does the store classify this particular service? |
| Mixed purchase | A physical product bundled with digital access | Does each part need a separate payment route? |
Keep this purchase list in your app MVP scope. It gives the build a clearer starting point than “add payments”.
When should you consider store billing for digital access?
Start with the store’s current requirements when payment unlocks content, functionality or continued access inside the app.
The permitted route can depend on the store, distribution method, customer location, product category and participation in applicable programmes. On Google Play, the Payments policy requires Google Play's billing system for in-app digital items, features and subscriptions, while some eligible regions have programmes for alternative billing. Do not treat a general explanation as a permanent rule for every release.
Write down the access rules before implementation:
- What does the purchase unlock?
- Is access permanent, time-limited or recurring?
- Which account owns it?
- How should the customer recover access on another device?
- What should happen after a refund or subscription expiry?
For a subscription, define cancellation separately from access expiry. Specify the intended behaviour, then check that it matches the store’s current subscription lifecycle. Google documents states such as cancellation, grace period, expiry and revocation in its subscription lifecycle guide.
When should you consider a payment gateway?
For physical goods and services delivered outside the app, begin by evaluating a gateway against the actual order or booking flow. Google Play's Payments policy does not require its billing system when payment is mainly for physical goods or physical services. Confirm that the proposed integration is permitted under the relevant store’s current rules.
Ask practical questions before comparing providers. Which customer locations and currencies must checkout support? Which payment methods matter? Do you need deposits, partial refunds or payment after service completion?
Decide when payment should happen. For a booking, specify whether payment reserves the slot or follows confirmation. For goods, define what happens if stock becomes unavailable after payment starts.
Require the developer to demonstrate these flows using the provider’s supported test environment. A working Pay button alone is too narrow an acceptance condition.
Why do services and mixed purchases need closer review?
“Service” is not a complete payment classification. Describe who delivers it, where the customer receives it, whether it includes digital content and whether payment unlocks anything inside the app.
Consider an illustrative fitness app selling an in-person appointment alongside a recorded exercise library. Treat these as separate purchase types during planning. Review each against current policy before deciding whether they can share checkout.
Avoid choosing one payment route merely because a single cart looks simpler. Ask the team to document the permitted route for each item and explain how customers will understand separate charges.
If classification remains unclear, resolve it through the store’s official guidance or support before building the purchase flow.
What should your server verify before granting access?
Make server-side verification an acceptance requirement: the phone’s success screen should not be the authority for delivering an order or unlocking paid access.
Ask the implementation team to confirm payment through the provider’s supported server mechanism, validate incoming notifications as its documentation requires, and check:
- The purchase belongs to the expected customer and order.
- The product, amount and currency match the intended purchase.
- The payment status permits the planned fulfilment.
- The same transaction has not already triggered fulfilment.
Use the provider’s current documentation for the exact verification procedure. For Google Play billing, Google advises sending each purchase token to your backend and verifying it there before granting access.
Require fulfilment to be safe to repeat. Processing the same verified transaction again should not create another shipment, booking or access grant.
What should happen when a transaction fails or stays pending?
Design the uncertain outcome as carefully as the successful one. Set an acceptance case where checkout closes or the connection disappears before the app receives a final result.
Keep payment status separate from order status. “Payment confirmed” and “order delivered” should represent different events.
| Situation | Recommended customer experience | Required handling |
|---|---|---|
| Payment is pending | Show that confirmation is still in progress | Check the existing transaction before offering another attempt |
| Payment is declined | Explain that payment was unsuccessful | Offer a supported retry route |
| Checkout is closed | Return to the order with a clear status | Retrieve the latest status before assuming failure |
| Payment succeeds but delivery fails | Show payment received and fulfilment pending | Recover fulfilment without collecting payment again |
| Refund is requested | Show the request separately from completion | Update the status when the provider confirms the outcome |
Avoid messages that claim certainty the app does not have. “We’re checking your payment” is appropriate while confirmation is unresolved.
Define a recovery route too: an order history entry, a status refresh and a support reference.
Which payment tests should be required before release?
Turn the purchase rules into observable checks. For an illustrative paid-feature purchase, success means verified payment grants the correct access once, and the account can recover that access after signing in again.
Include these cases in Android release testing:
- A successful purchase grants the correct product.
- A pending purchase remains visibly pending.
- Repeated taps do not create duplicate fulfilment.
- Closing and reopening the app retrieves the current status.
- An interrupted connection does not cause a second charge during recovery.
- Replayed or invalid confirmation does not grant access.
- Refund and subscription changes produce the intended access state.
- A customer can find the purchase and request help.
Test the interface and the server’s recorded outcome. A reassuring screen is insufficient if the order or access state is wrong.
What common mistakes should you avoid?
Choosing the provider before classifying the purchase. First establish what is sold and which payment routes are permitted.
Treating a phone callback as payment proof. Require server verification before fulfilment.
Calling every unresolved payment a failure. Give pending transactions a clear state and a recovery path.
Ignoring refunds and access recovery. Include both in the initial scope.
Assuming billing rules remain unchanged. Add a review of applicable requirements to the release checklist and the maintenance plan.
Adding every possible payment feature to the first release. Start with the purchase types the product needs, while covering their complete success, failure and recovery paths.
What do founders commonly ask about app payments?
Can one app use both store billing and a payment gateway?
Plan each purchase category separately, then confirm which integrations current store rules permit. Do not assume one approved purchase flow establishes permission for every other product in the app.
Does a subscription always need store billing?
Do not decide from the word “subscription” alone. Identify what the recurring payment provides, where it is consumed and which rules apply to that purchase.
Can customers pay on a website instead?
Check the applicable store’s current rules before adding external purchase links or directing customers elsewhere. Treat permission to link, promote or offer another payment route as a separate policy question. On Google Play, directing users to other payment options is limited to specific programmes in eligible regions, described in the Payments policy.
What should I give a developer before requesting a quote?
Provide the purchase list, intended markets, target stores, access rules, refund expectations and failure scenarios. Ask the quote to include verification, recovery and testing alongside checkout.
Need help defining the purchase flow? Our app development services cover payment integration as part of the build. Bring a description of what customers buy and what they should receive. If the app sells subscriptions, see how to design an app subscription paywall for the screen itself.