中文

Home / Articles

Choosing a cross-border payment stack as an indie developer

2026-10-05 · Cross-borderPayments

Indie developers selling internationally face three separate problems: collecting subscriptions, collecting one-off purchases, and settling funds back home. We kept notes on every provider decision and replacement while operating an overseas SaaS from zero to steady revenue. This post is organized as scenario → stack → measured results, as a reference for solo founders.

Separate the three scenarios first

Cross-border payments are not "pick the best provider" but "assemble the right combination":

No single provider wins all three — internalizing that saves weeks of deliberation.

Subscriptions and one-offs: the hosted-checkout trade-off

For individual founders, developer-focused Merchant-of-Record platforms such as Polar offer the lowest-friction start: no overseas entity required, subscriptions/tax/webhooks built in, and a single payment link gets you selling. The cost is a higher fee than raw card rails, and funds resting on the platform.

Our measured experience: webhook signature verification and retries were rock solid, and the order state machine is clean. At small revenue levels, the fee premium costs far less than the compliance and engineering you avoid — start here.

The threshold for direct card acquiring

At higher volume, direct acquiring saves real fees, but demands an overseas entity, compliance review, and your own subscription/chargeback machinery. We deliberately deferred this step: the labor of dispute handling and tax filing outweighed the fee savings at our scale.

Settlement: the Airwallex + Wise pairing

For moving money we hold two account types:

Measured over a year: large consolidations via Airwallex win on fees and speed; small experimental flows are easier through Wise. Both require genuine business documentation — a product link plus transaction statements is enough for individuals.

Engineering: a webhook-driven state machine

Whichever provider you choose, the critical architecture point is driving local order state from webhooks, not from the browser redirect. We learned this the hard way: users who close the tab after paying never return to your success page — only the webhook completes that order. Every webhook must be signature-verified, idempotently persisted, and backstopped by scheduled reconciliation.

Three recommendations for solo founders

  1. Ship your first revenue through a hosted MoR platform; over-engineer later;
  2. Negotiate direct acquiring only when volume justifies the added operations;
  3. Open settlement accounts early and keep them warm — one complete document package beats scrambling later.

There is no "best" cross-border stack, only the combination matching your scale, entity, and product. Ours changed three times in a year, each time driven by the same metric: net settlement rate.

Related reading

Between bulk generation and human editing: our content pipeline

Bulk-generated content gets flagged; purely manual is slow and expensive. Our pipeline: machine drafts, human authority, realistic cadence.

2026-10-28 · ContentMethod

A hands-on method for evaluating AI cutout edge quality

Hair, glassware, cluttered shelves: the three hard scenes for AI cutouts. A reproducible edge-quality evaluation method, plus what our tool bake-off found.

2026-10-24 · AI ToolsEvaluation

Static-site SEO fundamentals: sitemap, internal links, and crawl speed — measured

No tricks: five baseline moves that doubled Google's indexing speed on our static sites within three weeks — each with its own verification method.

2026-10-22 · SEOWeb