<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts on Tahseen Khan</title><link>https://tahseenkhan.dev/posts/</link><description>Recent content in Posts on Tahseen Khan</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><lastBuildDate>Tue, 01 Oct 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://tahseenkhan.dev/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Integrating Payment Gateways in React Native — Lessons from the Trenches</title><link>https://tahseenkhan.dev/posts/payment-gateways-in-react-native/</link><pubDate>Tue, 01 Oct 2024 00:00:00 +0000</pubDate><guid>https://tahseenkhan.dev/posts/payment-gateways-in-react-native/</guid><description>&lt;p&gt;Payments are one of the trickiest parts of any mobile app. Over the past couple of years, I&amp;rsquo;ve worked with multiple payment systems — Razorpay, PhonePe, Apple/Google In-App Purchases, UPI AutoPay subscriptions, and vendor split payments. Here&amp;rsquo;s what I learned the hard way.&lt;/p&gt;
&lt;h2 id="why-payments-are-hard-in-mobile"&gt;Why Payments Are Hard in Mobile&lt;/h2&gt;
&lt;p&gt;Unlike web, mobile apps have to deal with:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;OS-level restrictions&lt;/strong&gt; (especially iOS for in-app purchases)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Deep links and app switches&lt;/strong&gt; (UPI apps like GPay, PhonePe, Paytm)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Async payment flows&lt;/strong&gt; where success/failure comes via webhook, not response&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Test mode vs live mode&lt;/strong&gt; behaving very differently&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="razorpay--the-workhorse"&gt;Razorpay — The Workhorse&lt;/h2&gt;
&lt;p&gt;Razorpay is the go-to for Indian apps. The React Native SDK is solid but has some quirks.&lt;/p&gt;</description></item></channel></rss>