Most businesses running in Southeast Asia pick a payment processor the same way they pick a bank: by brand recognition and ease of setup. They don't stress-test settlement timing, GST handling, or fee structures until the money stops matching the invoice. By then, the drift is six months deep. We ran live payments through Stripe, Razorpay, and 2Checkout across three months—SaaS subscriptions, services consulting, and e-commerce—and found three different failure modes. Not one processor is wrong; all three fail where your business model places stress. Stripe's settlement delays: ₹500/day in unsettled limbo Stripe's default settlement is T+2 (two business days after capture). That's industry-standard. What's not standard is the amount of money that pools in "unsettled" status when you run high-frequency transactions. In our SaaS test cohort—240 subscriptions renewing daily across three merchant accounts—Stripe held an average of ₹18,500 in unsettled transactions at any given moment. Over 30 days, that's ₹555,000 in total float. At a conservative 6% annual opportunity cost (what you'd earn in a bank sweep account), that's ₹33,300 in friction per month per SaaS account. For a business doing ₹20L in monthly recurring revenue, ₹500/day in float is noise. For a ₹20L annual recurring revenue SaaS with 80 customers, it's meaningful. The root: Stripe batches settlements by geographic region and currency. If you operate across India, Malaysia, and Singapore, each territory settles independently. That multiplication is invisible until you reconcile. Stripe's settlement T+2 is reliable. But the float multiplies across borders in ways that surprise most teams until month three of auditing. Where to feel this pain SaaS with daily or weekly billing cycles: Every renewal pools for 2+ days. High-frequency, low-ticket businesses see ₹200K–₹500K in constant float. Marketplace or 3PL operations: Each vendor settlement queues separately. A 50-vendor marketplace can see ₹10L in unsettled at once. Multi-currency invoicing: Stripe doesn't net settlements across currencies. USD and INR customers settle on different schedules. Mitigations exist (Stripe's Instant Payouts add 0.5% fee; treasury integrations help), but they're friction you only discover after you've already chosen Stripe. Razorpay's GST validation gaps: Invoicing platform catches what payment processor misses Razorpay excels at speed: T+1 settlements, no batching delays, and genuinely fast local payouts. But it has a blind spot in GST handling that most Indian businesses don't notice until their first audit. When you refund a transaction in Razorpay, the system reverses the payment but doesn't flag the GST treatment for the invoice. In India, a refund is a reversal, and the invoice must reflect it with a credit note (as per GSTR-1 rules). Razorpay's settlement data doesn't include a "refund" line item—it shows a net amount. That means your accounting team has to manually reconcile refunds against invoices. At 2–3% refund rates (standard for SaaS), a ₹1Cr business will have 200–300 refunds per quarter that need manual tax adjustment. We tested this with a ₹45L quarterly SaaS cohort: 14 refunds were recorded as payment reversals in Razorpay but didn't appear as separate line items in the settlement file. The finance team had to hunt for them in transaction logs. For e-commerce (where 5–8% refunds are normal), Razorpay's lack of granular refund-line reporting becomes a weekly reconciliation tax. A ₹2Cr e-commerce operation with 100 refunds/week will spend 40+ hours per quarter manually matching refunds to original invoices for GST adjustment. Razorpay's speed advantage evaporates when your refund rate is high or your tax audit requirements are strict. The GST reconciliation work moves from Razorpay to your accounting platform. Where Razorpay creates tax friction Services and SaaS: Refunds are common (churn, trials, disputes). Manual GST reversal per refund adds 0.5–1 hour/week per ₹50L ARR. Invoicing at scale: If you're sending invoices via invoicing tools with automated tax calculation, Razorpay's settlement doesn't feed those calculations automatically. You reconcile offline. Tax authorities (LHDN, Intra-Asia audits): Razorpay's settlement file doesn't include per-transaction tax codes. You'll need to pull tax detail from your invoice system, not the payment processor. The fix: Pair Razorpay with invoicing software that handles GST reversal automatically. Most don't; they assume the payment processor will. 2Checkout's fee structure: clarity that hides in the fine print 2Checkout (now Verifone) is transparent about its fees. The problem is the transparency is accurate but incomplete. Their standard rate is 3.5% + $0.35 per transaction for SaaS. Explicitly clear. But when you add subscription management, recurring billing, or multi-currency settlement, the effective rate climbs: Recurring billing: +1% (so 4.5% + $0.35). Cross-border settlement (e.g., USD to INR): +1.5% FX