Taking money in a mobile app is mostly not about the checkout screen. It is about orders that cannot be paid twice, webhooks that actually arrive, subscriptions that renew, and a ledger that reconciles at the end of the month. I build that whole path.
Razorpay · Stripe · PhonePe · PayU · UPI · Subscriptions · GST invoices
The visible part of payments is a screen with a pay button. The rest is state: an order created on your server, a payment intent or order id passed to the gateway, a result returned to the app, and a webhook that confirms the truth even when the user closes the app mid-payment.
Most production payment bugs come from trusting the client. A Flutter app can be interrupted, backgrounded or killed during a redirect, so the server and the webhook must be the source of truth for whether money moved.
For Indian customers, Razorpay and PhonePe cover UPI, cards, netbanking and wallets with familiar flows. Stripe is usually the better fit for international cards and subscription billing outside India, and PayPal still matters for some export and freelance use cases. Cashfree and PayU appear where payouts or enterprise contracts require them.
I integrate the provider that matches your customers and settlement needs, and can support more than one so domestic and international payments take the right route.
Subscriptions add plan changes, trials, proration, retries on failed cards, dunning messages, cancellation and access control tied to billing state. If entitlement is checked only at purchase, users keep access after a failed renewal — or lose it while a retry is still in progress.
The backend owns subscription state; the app asks for entitlement and renders accordingly. That keeps web, mobile and TV products consistent when they share one account.
Every payment needs to appear in your books with the right reference. That means storing gateway order ids, payment ids, amounts, fees, tax and status, then matching them against settlement reports instead of guessing from app logs.
Refunds, partial refunds, failed payouts and GST invoices are part of the build, not an afterthought. I also make the test path realistic: sandbox keys, test cards, UPI success and failure simulation, and webhook replay.
Explore examples of mobile, Smart TV and integrated product work.
Razorpay or PhonePe usually suit Indian customers because UPI, cards and netbanking are first-class. Stripe is better for international cards and subscription billing. Many products support two providers so domestic and cross-border payments route correctly.
The app is confirming what the client saw, not what the bank did. The reliable source is the server-side verification and the gateway webhook. Building around the webhook instead of the client callback removes most duplicate and phantom-payment problems.
Yes. That usually means adding plan definitions, a billing record on your backend, webhook handling for renewals and failures, and entitlement checks in the app.
Where Apple or Google require their billing for digital goods, yes. Physical goods and services can use a normal gateway. Getting this distinction right avoids store rejections.
