A Singapore fintech hit ₹12M ARR on product sales. They'd been running Stripe since day one, accepting SGD and USD. When invoices arrived from Indonesia and Malaysia clients, they noticed the margin math wasn't working—Stripe's regional markup on PHP and IDR was costing them 1.8 bps more than a local processor would have charged. By the time they switched processors to handle IDR, MYR, and THB natively, they'd already left ₹18 lakhs on the table. Payment processor choice is one of the few decisions you'll make that compounds every month. At ₹5M ARR you don't feel it. At ₹50M, it's a six-figure decision. The problem: global processors like Stripe optimize for US and EU margins. Local processors optimize for their home country. Regional processors like Razorpay bet they can win at cross-border. Wise is built for currency, not commerce. Each has a real use case. None works for all of them. The fee structure that actually matters: effective rate, not headline rate Stripe publishes 2.9% + ₹10 for Indian domestic transactions. That's the headline. The real rate depends on what currency your customers use and where they're based. Stripe IDR (Indonesia): 2.9% + ₹10 on card transactions, 1.75% on bank transfers. But Stripe's IDR settlement eats 0.35–0.55 bps extra in their favor on the conversion. Effective cost: 3.25–3.45%. Stripe MYR (Malaysia): 2.45% + flat fee, but FX markup on MYR-to-SGD or MYR-to-USD settlement adds another 0.4–0.6 bps. Effective: 2.85–3.05%. Razorpay INR (India): 2% + ₹3 on domestic cards, 2.5% on international. No hidden FX. Straightforward. Razorpay cross-border (IDR, MYR, THB): 2.9% + local fee, plus 1.2–1.8 bps on settlement FX. Effective: 4.1–4.8%. Local processors (e.g., Curlec in Indonesia, Xendit in Indonesia/Philippines, ipay88 in Malaysia): 1.8–2.4% on domestic cards, 3.5–4.2% on cross-border. But settlement is same-day to next-day in local currency. No FX surprise. Wise (formerly TransferWise for payments): 1.5% on transfers, but only available for wire/ACH. Not suitable for card processing at scale. At ₹12M ARR, where Stripe was costing 3.4% on IDR and a local processor charged 2.2%, the difference was ₹3.2 lakhs per year. Not trivial. Settlement speed: when T+1 becomes T+7 Stripe settles in 2 business days in India, Singapore, and Malaysia. Stripe also settles in 2 business days in Indonesia and Thailand, but the clock doesn't start until the payment fully clears, which can take an extra day depending on the bank. That's effectively T+3. Razorpay settles in 1 day for India, 2 days for cross-border (starting from payment authorization, not clearing). Local processors: Indonesia (Xendit, Fintech Karya): T+1 for same-bank transfers, T+1 EOD for cards. Malaysia (ipay88, Fintech Genius): T+1 for most banks, T+2 for Affin and CIMB. Thailand (2C2P, Omise): T+2 standard, T+1 for Thai baht domestic. Philippines (PayMongo, DragonPay): T+1 standard. The catch: local processors often require minimum settlement amounts (₹50K–₹500K per batch) and won't settle weekends or public holidays. In December and January, cash flow tightens. At ₹12M ARR, T+1 settlement vs. T+3 means ₹20–₹30 lakhs more cash on hand every month. That's not small. Multi-currency margins: how Stripe and Razorpay hide FX costs Say a Malaysian customer pays you 5,000 MYR. You want it settled to your SGD account. Stripe's FX rate: mid-market + 0.85–1.2 bps markup. On 5,000 MYR, that's an extra ₹200–320 hidden in the conversion. Happens every transaction. Razorpay: mid-market + 1.2–1.8 bps on cross-border USD conversions; slightly better on IDR-to-SGD (0.9–1.4 bps). Still hidden in the settlement, not shown in your dashboard. Local processors often publish rates daily or let you lock rates manually. Wise is transparent by design—you see the exact rate, pay their flat fee (1.5% for transfers), and you know what you get. But Wise doesn't process cards directly; you'd need a card processor + Wise for FX. The hybrid approach that wins at ₹5M–₹50M ACV: Use Razorpay or Stripe for your primary market (India, Singapore) where fees are tight and settlement is 1–2 days. Use a local processor for secondary markets (Indonesia, Malaysia, Thailand) where fees are 1–1.5 bps cheaper and settlement is guaranteed T+1. Use Wise for manual wire payouts and currency consolidation only—don't try to route card payments through it. Integration cost and operational drag: when consolidation saves money Every processor you add requires: A separate dashboard and settlement account. Reconciliation logic in your accounting software (or a manual monthly check). Customer support training: which processor failed and why. A redundancy plan: if one processor goes down, you have a fallback. Stripe and Razorpay both integrate cleanly with Orin's invoicing , QuickBooks, and Xero. Settlement data syncs automatically. Local processors (Xendit, ipay88, 2C2P) have APIs but less plug-and-play integration. You're likely writing a custom webhook handler to record settleme