Skip to content
Mobile Apps15 min read

Mobile App Payments: How to Choose a Gateway and Build a Secure Checkout

When an app can use a payment gateway, a scorecard for choosing one, India's RBI rules, and how to build a secure checkout with server-side verification.

01

How do you choose a payment gateway for a mobile app?

First check whether store rules let you use a gateway at all: physical goods and real-world services must use one, while digital content unlocked in the app generally must use Apple's in-app purchase and Google Play Billing. If a gateway is allowed, shortlist providers that can onboard your business in your country, support the payment methods your customers use, offer maintained SDKs for your app's platforms, settle in your currency and handle 3D Secure and recurring payments. Compare their fee structures from their own schedules, then build the checkout so payments are created and confirmed on your server.

Whichever provider you choose, use its mobile SDK so card data stays off your servers, confirm results through webhooks before fulfilling, handle failures and refunds cleanly, and keep the payment UX short and transparent. For the server-side detail of a web integration, see the payment gateway integration guide.

02

Key takeaways

  • Platform rules come first: they decide whether a gateway is even allowed.
  • Score providers on onboarding eligibility and local methods before fees.
  • Ask for the full fee schedule by component; do not compare headline rates alone.
  • Using the provider's SDK keeps card data off your servers and reduces PCI scope.
  • In India, check that the provider is a bank or an RBI-authorised payment aggregator, and follow the 2026 E-mandate Framework for recurring payments.
  • Never fulfil an order until your server has confirmed payment.
03

Can your app use a payment gateway at all?

Apple's App Store Review Guidelines require in-app purchase to unlock features or functionality in the app, such as subscriptions, in-game currencies, premium content or a full version (3.1.1). Apps selling physical goods or services consumed outside the app "must use purchase methods other than in-app purchase", such as Apple Pay or traditional card entry (3.1.3(e)). Real-time one-to-one services, such as tutoring or medical consultations, may use other methods, but one-to-few and one-to-many real-time services must use in-app purchase (3.1.3(d)). Apps sold directly to organisations for their employees or students may also skip in-app purchase (3.1.3(c)).

Google Play's Payments policy requires Play billing for digital goods and services, and says Play billing must not be used for physical goods, physical services, bill payments or peer-to-peer payments (Section 3). Steering users to other payment methods is not allowed except under the policy's exceptions and, in eligible countries, enrolled alternative billing or external offer programmes (Sections 4, 8 and 9). These programmes vary by country and are changing, so check them for each market. This is not legal advice.

If you are still deciding how the app makes money, start with mobile app monetisation models, which maps each model to the payment rail it requires.

What you sellPayment methodExamples
Physical goodsPayment gateway: cards, Apple Pay, Google Pay, local methodsRetail, groceries, marketplace products
Real-world servicesPayment gatewayRides, bookings, food delivery, appointments
Real-time one-to-one servicesGateway allowed on iOS under 3.1.3(d); check Play rules for your caseTutoring, consultations, personal training
Digital goods and subscriptionsApple in-app purchase and Google Play Billing, with regional exceptionsPremium features, content, virtual items
04

Gateway selection scorecard

Score each shortlisted provider 0 (no), 1 (partly or with conditions) or 2 (yes) on each row, using the provider's own documentation and answers in writing. Treat the first two rows as pass or fail: a provider that cannot onboard your entity or does not support your customers' main method is out, whatever it scores elsewhere.

CriterionWhat to checkWhy it matters in an app
1. Onboarding eligibilityCan it onboard a business registered in your country? What documents, licences and website does it require?Some providers are invite-only or in preview in some countries; onboarding can take longer than the build.
2. Methods by marketCards, Apple Pay, Google Pay, and local methods such as UPI, netbanking or wallets in each market you sell inIf the method your customers use most is missing, conversion suffers however good the app is.
3. Native SDKsMaintained SDKs for iOS, Android and your framework (React Native, Flutter); prebuilt payment sheet vs custom UIDetermines build effort, how much card data your app touches, and how quickly OS changes are supported.
4. Apple Pay and Google PaySupported inside the same SDK; setup steps such as merchant IDsWallets reduce typing and card entry errors on phones.
5. Settlement currencyCurrencies you can charge in, which currency you are paid in, payout account countryCurrency conversion and payout limits affect margin and cash flow.
6. Fee structureAsk for the full schedule by component: domestic and international cards, local methods, currency conversion, refunds, chargebacks, payouts, any platform feeHeadline rates hide the components that dominate for your mix of customers.
7. PCI scopeDoes card data go directly from the SDK to the provider, never through your servers?Directly handling card data greatly increases your security and compliance work.
8. 3DS and SCADoes the SDK run the 3D Secure challenge in the app and handle the result?Required for many card payments where strong authentication rules apply; poor handling causes failed payments.
9. Recurring paymentsSaved cards, mandates (for example UPI AutoPay or card e-mandates in India), merchant-initiated paymentsRules for recurring debits differ by market and change; the provider must support them.
10. Webhooks and reconciliationSigned webhooks, event coverage, reporting and settlement reportsYour server depends on these to confirm orders and match payouts.
11. Test modeSandbox with test cards and simulated authentication and failuresYou need to test declines, 3DS and refunds before launch.

Pro tip

Name providers only after checking their current documentation. For example, Stripe's global availability page listed India as "Preview" (via sales) on 15 October 2026, while Australia, the UAE, the UK and Singapore were listed as available; Razorpay's documentation listed cards, UPI, netbanking, wallets and EMI as default methods, with e-mandates needing approval. Both are vendor statements that change.

05

Market notes

India. The Reserve Bank of India's Payment Aggregator Directions of 15 September 2025 set three categories (online, physical and cross-border), require non-bank payment aggregators to be authorised by the RBI (banks do not need authorisation), and require non-bank aggregators to hold merchant funds in an escrow account with a scheduled commercial bank. The baseline technology rules also say customer card credentials must not be stored in any database or server the merchant can access. In practice: confirm that your provider is a bank or an authorised payment aggregator, and never store card numbers yourself.

For recurring payments, the RBI's Digital Payments E-mandate Framework, 2026 (21 April 2026) applies to cards, prepaid payment instruments and UPI. The mandate is registered with additional authentication; after that, recurring debits up to ₹15,000 per transaction can run without it, and up to ₹1,00,000 for insurance premiums, mutual fund subscriptions and credit card bill payments. The customer must be notified at least 24 hours before each debit, can change or withdraw the mandate at any time, and must not be charged for the facility. Digital goods in Indian apps still follow the store rules above.

UK and EU. Strong customer authentication applies when a payer initiates an electronic payment, unless an exemption applies; in the UK it has applied since 14 September 2019. EU exemptions, such as those for recurring and low-value payments, have specific conditions; rely on your provider's SDK and documentation to apply them rather than hard-coding thresholds.

UAE and Singapore. Payment services are licensed by the Central Bank of the UAE and the Monetary Authority of Singapore respectively. Ask any provider for its licence details and check them on the regulator's site; in Singapore, the MAS Financial Institutions Directory lets you look up payment institutions by licence type.

Australia. Surcharging, least-cost routing and PayTo are covered in payment gateway integration in Australia.

06

Questions to ask a provider

Send these in writing to each shortlisted provider before you commit a mobile app build to one of them.

  • Can you onboard a business registered in our country, and how long does activation usually take for a business like ours?
  • Which licence or authorisation do you hold in each market we sell in, and where can we verify it?
  • Which payment methods are enabled by default and which need approval?
  • Which SDK versions support iOS, Android, React Native and Flutter, and how often are they updated?
  • What is the full fee schedule, including international cards, currency conversion, refunds, chargebacks and payouts?
  • Which currencies can we charge and settle in, and to which bank account countries can you pay out?
  • How does your SDK handle 3D Secure and recurring mandates in our markets?
  • Which webhook events do you send, and how are they signed?
  • What do we need to do to stay PCI compliant with your recommended integration?
07

Mobile payment architecture

For physical goods and services, the app requests a payment from your server, which creates it with the payment provider. The provider's SDK collects card or wallet details and handles authentication. The provider notifies your server by webhook, and your server confirms the order. Stripe's iOS documentation, for example, explains that the app cannot create payment objects itself "for security reasons": the server creates them and returns a client secret to the app. For in-app purchases, the store processes the payment and your server verifies the transaction with Apple or Google.

08

Cards, digital wallets, Apple Pay and Google Pay

Use your provider's mobile SDK or payment sheet so card numbers go straight to the provider. Offer Apple Pay and Google Pay where supported: they're fast, familiar and use device authentication, which reduces friction and card entry errors. Payment providers typically support both through the same integration.

09

In-app purchases and subscriptions

Apple's StoreKit and the Google Play Billing Library handle one-time purchases and subscriptions for digital goods. Verify every transaction on your server with Apple's and Google's server APIs, and subscribe to App Store Server Notifications and Google Play real-time developer notifications to track renewals, grace periods, cancellations and refunds. Always offer a way to restore purchases.

10

Payment authorisation and transaction states

StateMeaningApp behaviour
CreatedPayment initiatedShow progress
Requires actionBank authentication neededProvider SDK shows the challenge
ProcessingAwaiting confirmationShow pending status; don't fulfil yet
SucceededConfirmed by webhook or server checkConfirm order, send receipt
FailedDeclined or erroredExplain clearly, allow retry or another method
Refunded / disputedMoney returned or contestedUpdate order and entitlements
11

Webhooks and backend verification

Never trust the app alone to confirm payment. Verify webhook signatures, confirm status with the provider or store, then update orders and entitlements. Process webhooks idempotently because they can arrive more than once or out of order. The server-side payment integration guide covers this in more detail.

12

Failed payments, retries and refunds

Declines, authentication failures and network errors are routine. Keep the cart or order intact, explain what happened in plain language, and offer a retry or alternative method. Use idempotency keys so retries don't double charge. For subscriptions, use store grace periods and billing retry. Refunds should update orders, entitlements and receipts.

13

Fraud prevention concepts

Rely on your payment provider's fraud screening and 3D Secure where appropriate, add velocity limits on your own endpoints, watch for patterns such as many failed attempts, and use app attestation to reject requests from tampered apps. See mobile app security.

14

Secure payment UX

Show the full price, taxes and delivery costs before payment, offer familiar methods first, minimise typing with wallets and autofill, keep users informed during processing, and prevent double taps on the pay button. Present clear receipts and transaction history in the app. See mobile app UX design.

15

PCI considerations

If you accept cards, PCI DSS applies to your business in some form. Stripe's security guide, for example, says businesses accepting payments must do so in a PCI-compliant manner and attest annually, and that integrations which send card data directly to the provider without it passing through your servers reduce your obligations. Keep card data within the provider's SDK or hosted fields, out of your servers and logs, and confirm your specific obligations with your provider.

16

Testing payment flows

  • Successful payment with and without 3D Secure
  • Declined cards and insufficient funds
  • App closed during processing; order resolves via webhook
  • Duplicate webhooks handled once
  • Double tap on the pay button doesn't double charge
  • Refunds update orders, entitlements and receipts
  • Recurring payment with a pre-debit notice, where your market requires one
  • In-app purchase, restore and subscription renewal in sandbox
  • Subscription grace period, cancellation and refund notifications
17

Receipts and transaction history

Send receipts by email or in-app, show order and subscription history, and make it clear how to manage or cancel subscriptions, which the stores handle for in-app purchase subscriptions. Before submitting, run through the mobile app launch checklist, including the payment information the stores ask for.

18

Common mistakes and limits

Common mistakes: choosing a gateway before checking whether store rules require in-app purchase; picking a provider that cannot onboard your entity; comparing headline rates instead of the full fee schedule; confirming orders from the app instead of the server; and building recurring payments without the mandate and notice rules of your market.

This scorecard does not replace legal, tax or compliance advice, and it cannot tell you a provider's real approval time or risk appetite for your business, which you only learn by applying. Regulations and store programmes change, so date-check every rule you rely on.

19

Sources

Platform rules: Apple App Store Review Guidelines, section 3.1; Google Play Payments policy.

Regulators: RBI: Regulation of Payment Aggregators Directions, 2025; RBI press release, 15 September 2025; RBI: Digital Payments E-mandate Framework, 2026; FCA: strong customer authentication; MAS Financial Institutions Directory.

Vendor documentation (examples, not endorsements): Stripe global availability; Stripe: accept a payment on iOS; Stripe: integration security guide; Razorpay: payment methods; Razorpay: international payments.

Accessed 15 October 2026. Payment regulations, store rules, provider availability and fees change; check the current pages and take professional advice.

20

Conclusion

Choosing a payment gateway for an app starts with the store rules, then onboarding and local methods, then SDKs, settlement, fees, PCI scope, authentication and recurring support. A secure checkout keeps card data with the provider, verifies every payment on the server, handles failures and refunds cleanly, and shows a short, transparent flow. Next steps: confirm which of your products need in-app purchase, score two or three providers with the table above, and ask each the questions in writing. For the wider build context, see the mobile app development guide.

Choosing a payment stack for your app?

ZSpace Labs is a remote-first technology studio that works with clients globally on mobile app development. If useful, we can check what store rules allow for your product, shortlist providers for your markets and build the integration with server-side verification.

Start a Project
FAQ

Common questions.

For digital goods and features unlocked in the app, such as subscriptions, premium features and virtual items, generally yes. Physical goods and real-world services must use other payment methods, such as a payment gateway, Apple Pay or Google Pay. There are exceptions (for example, Apple allows real-time one-to-one services and enterprise sales outside in-app purchase) and region-specific programmes, so check the current App Store Review Guidelines and Google Play Payments policy.

Yes, for physical goods and services, usually through a payment provider that supports them. They're not a substitute for in-app purchase where store rules require it.

If you accept cards, PCI DSS applies to your business in some form. Using a payment provider's SDK or hosted fields so card data never touches your servers greatly reduces your scope. Confirm your obligations with your provider.

The app can be tampered with and network responses can be lost. Your server should confirm payment status with the provider or store, through APIs and webhooks, before granting access or fulfilling orders.

Notifications the payment provider or app store sends to your server when a payment, subscription renewal, refund or dispute changes state.

Show a clear message, keep the order recoverable, let the user retry or choose another method, and never fulfil an unpaid order. For subscriptions, use the stores' grace periods and billing retry features.

They renew automatically, can enter grace or retry states, and can be cancelled or refunded outside your app. Track status from store server notifications rather than the device alone.

An authentication step for card payments, often required in regions with strong customer authentication rules. Payment provider SDKs handle the challenge flow inside the app.

Use payment providers' test modes and test cards, Apple's sandbox and StoreKit testing, and Google Play's license testers, covering success, failure, authentication, refunds and subscription renewals.

No. It explains technical and UX practices. Payment, tax and consumer rules depend on your business and markets, so confirm them with qualified advisers and your payment provider.

The RBI's E-mandate Framework of 21 April 2026 covers recurring payments by card, prepaid instrument and UPI. After the mandate is set up with additional authentication, recurring debits up to ₹15,000 each can run without it (₹1 lakh for insurance premiums, mutual fund subscriptions and credit card bills). The customer must be notified at least 24 hours before each debit and cannot be charged for the facility.

Only if it supports the methods, onboarding and settlement you need in each market. One provider is simpler to build and reconcile, but a business selling in India and abroad often needs a provider strong in UPI and Indian onboarding alongside one for international cards. Design your server so a second provider can be added without rewriting the app.

Get in touch

Have a project in mind?

Whether you're building a new digital product, improving an existing website, or looking to automate part of your business — let's talk.