How to add payments to a mobile app depends on whether you sell digital goods, physical goods or subscriptions — store rules differ, and India adds UPI and GST complexity.
Pick the right payment rail
- Physical goods / services — gateway (Razorpay, PayU, Stripe) inside the app or webview per policy
- Digital goods on iOS — usually Apple IAP; Android has Play Billing for digital
- Subscriptions — plan store billing vs external billing carefully by content type
- UPI intent / QR — common for India consumer checkout
Implementation checklist
- Server-side order creation and signature verification
- Idempotent webhooks for success/failure
- Receipt validation for store purchases
- Refund and chargeback handling paths
- GST invoices where required
Security basics that are non-negotiable
Never trust the client for price or entitlement. Keep secrets on the server. Log payment states for support. Pair payment work with solid API development and mobile release discipline.
Store policy traps
- Routing around IAP for digital content on iOS
- Missing privacy nutrition labels for payment data
- Incomplete restore-purchase flows for subscriptions
Test plan before real money
Use sandbox/test keys, failed payment states, network drops mid-checkout and duplicate webhook delivery. See also common mobile mistakes.
Design payments with entitlement logic
Contact Altron Technologies to map gateway vs store billing for your monetisation model.
