Stripe for international cards and subscription billing — Payment Intents, 3D Secure, webhooks and a billing model that keeps access in sync with what was actually charged.
Payment Intents · Checkout · Subscriptions · 3D Secure · Webhooks
Stripe is usually the better choice when most of your revenue comes from international cards, when you need strong subscription tooling, or when your business entity and settlement account sit outside India. For Indian retail customers paying by UPI, a domestic gateway is normally smoother.
Some products support both: Stripe for international customers, Razorpay or PhonePe for domestic ones, with one entitlement system behind them.
Stripe's modern flow is built around Payment Intents, which track a payment through authentication and confirmation. The app requests a client secret from your backend, confirms the payment, and the backend listens for the payment_intent.succeeded webhook before granting access.
3D Secure and regional authentication are handled by Stripe, but the app still needs to deal with the next-action step and the case where the user abandons it.
Stripe Billing handles plans, trials, proration, invoices and dunning. The app never decides who is subscribed; it asks your backend, which reflects Stripe's subscription status and stores a customer id per account.
A customer portal link lets people update cards and cancel without you building a billing screen — a real saving on support load.
Webhooks arrive out of order, occasionally twice, and sometimes late. Handlers need to be idempotent and tolerate events for objects that no longer exist. Test mode plus the Stripe CLI makes it possible to replay the awkward cases before launch.
I also wire basic fraud and dispute handling so chargebacks do not silently eat revenue.
Explore examples of mobile, Smart TV and integrated product work.
Stripe availability depends on your entity and account status. Many Indian businesses use a domestic gateway for local customers and Stripe for international billing. I can support both behind one entitlement model.
Yes. Payment Intents, subscription changes and webhook verification require a backend. The Flutter app should never hold the secret key.
Digital goods sold inside iOS and Android apps generally must use the platform's billing. Stripe is used for web purchases, physical goods and services, and markets where external payment is allowed.
