TL;DR: Major payment processors exclude or freeze creators in whole regions, with no appeal. PainHunt's data shows this is intense and recurring among indie builders. The opening isn't a new Stripe — it's a resilient routing-and-failover layer for the regions Stripe leaves out.
The evidence
Across PainHunt's payment categories — Payment Processing (329 posts), Payment Infrastructure (232), and Payment Processing Infrastructure (173), all at the 10+/15 bar — the signal is unusually concentrated on BlueSky, where indie hackers gather and compare notes rather than file app-store reviews.
The reports share a hard edge: Stripe excludes Pakistan and has blocked Nigeria; second-choice processors like Lemon Squeezy are also unavailable there; PayPal freezes or closes accounts without an appeal path; and the fallback, Paddle, carries materially higher fees. The workaround — stitching together a local gateway, Wise, and a local bank — is fragile and hard to maintain. The feature requests are specific: a Stripe-compatible gateway that works in these regions, a unified API that routes by geography, and automatic failover when the primary processor freezes.
Why this exists now
Incumbents optimize their supported-country list for fraud and compliance risk, not for the long tail of legitimate creators. As digital products go global, more builders sit on the wrong side of that line — earning international demand they can't actually collect.
The wedge
Resilience over reinvention:
- Access: onboard merchants in excluded regions through whatever compliant local rails exist, abstracting them behind one checkout.
- Failover: route across multiple providers and switch automatically when one blocks or freezes, so a single processor decision isn't existential.
The narrative is survival: "get paid by global customers without one provider's policy ending your business."
Risks and honest caveats
- Compliance is the product: moving money across borders invites licensing, KYC and AML obligations. This is heavy, regulated territory — scope a single corridor and get legal advice before you touch funds.
- Adverse selection: the creators most desperate for access may be the highest-risk to underwrite.
- Rail fragility: you inherit the reliability of the local providers you depend on; instant payouts are hard where the underlying rails are slow.
How to validate this further
Read the firsthand reports in the Pain Point Browser, then test which corridor pulls hardest using how to validate a startup idea. Related: protecting merchants from frozen funds.