If you invoice across Malaysia, Indonesia, or Singapore, you've probably discovered that one payment rail doesn't cover your customers. A Singapore client pays via instant FAST transfer. An Indonesian invoice sits in a customer's Stripe wallet because they don't trust cards. A Malaysian contractor needs FPX before they'll release work. The temptation is to bolt on every rail—Stripe for global reach, a local gateway for volume, ACH equivalents for speed, and direct bank transfers as a fallback. But without a coherent routing logic and native integration into your invoicing platform, you end up with four reconciliation streams, four settlement lags, and four places where money disappears into the float. This guide maps the four rails you'll actually need, how they integrate with Orin, Xero, and QuickBooks, and the routing rules that keep cash moving instead of pooling. The four rails and what they solve Each rail handles a different customer type and cash-flow problem: Stripe : Global card acceptance, subscription renewals, foreign-currency deals. Settlement in 2–3 days. High fees (2.9% + ₹10–15) but lowest friction for international customers. Local gateways (2Checkout, Xendit): Domestic payment methods—credit cards at lower rates, e-wallets, OTC bank transfers. Settlement 1–2 days. 2Checkout reaches 195 countries; Xendit dominates Indonesia with 1.8% card fees vs. Stripe's 2.9%. ACH equivalents (Singapore FAST, Malaysia FPX): Same-day or next-day settlement, zero or minimal fees, but only for customers with accounts at participating banks. FAST covers 12 Singapore banks; FPX covers 80% of Malaysian business banking. Direct bank transfers : Lowest fees (sometimes zero), highest friction—requires manual routing, manual receipt, and manual reconciliation. Use only for high-value contracts, retainers, or customers who demand it. The mistake is treating all four rails equally. Route by customer, not by invoice. Corporate retainers should land in FAST or FPX. SME customers default to Stripe or a local gateway. Pay-per-invoice jobs should offer a choice but nudge toward gateways. Stripe: still the global default, but bleeding fees Stripe remains the easiest onboard because it works everywhere and integrates natively into most invoicing tools. But in Southeast Asia, the 2.9% + fixed fee compounds quickly. A ₹1L invoice via Stripe costs ₹2,913 in fees. Routed through Xendit or a local processor, it costs ₹1,800. The difference is ₹1,113 per invoice—₹13.4K a month at volume. Use Stripe for: Customers with no local payment method (international clients paying in USD or EUR) Subscription recurring billing (Stripe's automation is solid) One-off invoices where customer friction is higher than fee cost Stripe integrates natively with Orin's invoicing module , QuickBooks Online, and Xero. When a customer pays via Stripe link, the transaction syncs to your GL automatically within 4 hours. Local gateways: 1.2–1.8% fees, but reconciliation gets messy Xendit (Indonesia), 2Checkout (Malaysia, Singapore), and Doku (Indonesia) offer lower fees and local payment methods that Stripe buries behind extra friction. Xendit's 1.8% card rate saves money but splits your customer inbox—some pay Stripe, some pay Xendit, some use e-wallets that only Xendit supports. The integration problem: Most invoicing platforms assume one payment processor. If you embed a Xendit link in one invoice and a Stripe link in another, your invoicing software can't automatically match inbound transactions to invoice numbers. You manually reconcile twice. Orin's invoicing allows multiple payment methods per invoice and auto-routes based on customer country. An invoice to a Jakarta customer defaults to Xendit; one to Singapore defaults to FAST; one to a US client defaults to Stripe. The payment lands in your Orin inbox, reconciliation happens in-platform, and your GL syncs one transaction instead of three. Xero and QuickBooks require you to reconcile each rail separately, which is why many teams set up virtual accounts (one Xendit account per region) and consolidate via a middle layer—adding 1–2 days of float and reconciliation labor. ACH equivalents: same-day settlement, no fees, but low coverage Singapore FAST (Fast And Secure Transfers) and Malaysia FPX (Financial Process Exchange) are the closest thing Southeast Asia has to ACH. FAST settles in seconds or minutes and is free for participating banks. FPX settles in 10–30 minutes and costs businesses nothing. The catch: coverage is limited to large corporate customers and banks on the network. FAST covers DBS, OCBC, UOB, and 9 others—about 95% of Singapore business banking. FPX covers 15 Malaysian banks—roughly 80% of the market. Neither works for customer payments to you unless your customer has an account at a participating bank. When to use FAST or FPX: Retainer invoices to corporations. Multi-month projects where you have a relationship and can request their preferred rail. Deposits before work begins. Colle