TL;DR: Legitimate merchants — especially non-US owners with ITIN/EIN — get trapped when automated KYC verification loops and fails, locking their funds for days with no expedite path. PainHunt's data shows this as high-intensity, money-on-hold pain. A service that provides an alternative verification route and expedited human review when the automated system fails is a real fintech wedge.
The evidence
Payment Processing surfaced as a high-value cluster in the latest batch (478 posts scored 10+/15, intensity 7.7/10), voiced on BlueSky and Discourse by e-commerce merchants and non-US owners running US businesses.
The sharpest thread is verification failure with funds attached. Merchants report an "automated facial recognition/ID verification system (via Stripe) fails 35+ times despite perfect conditions" across multiple documents and devices; a "manual review process takes 3-5 business days with no way to expedite despite clear system failure"; and an "endless verification loop — successful initial verification triggers another immediately after." The stakes are concrete: "$2,500 in business funds locked during verification," with "business and tax documents (ITIN, EIN) already provided but still blocked by automated system." A parallel Shopify Payments failure traps users whose bank-update flow "requires old bank credentials that don't match."
The feature requests are specific: identity verification "that works reliably for non-US citizens with ITIN," an "expedited manual review option when automated system fails after multiple attempts," and an "alternative payment processor with simpler verification for non-citizen US business owners."
Why now
KYC moved from a back-office check to a fully automated gate — face match, liveness, document OCR — optimized for the median US applicant. For everyone off that median (foreign passports, ITIN-based US LLCs, non-standard documents), the automated system fails silently and routes to a manual queue that isn't staffed for urgency. Meanwhile the funds are already held, so a verification bug becomes a cash-flow emergency.
The rise of cross-border, remote-first commerce means the non-median applicant is now a large, growing share — and the incumbents' automated gates weren't built for them. That mismatch, with money on hold, is exactly where a focused product can stand.
The wedge
Stand between the stuck merchant and the frozen funds.
- A verification-failover concierge: when the automated flow fails N times, collect the documents once and drive an expedited human review through the right channel, instead of the merchant re-looping.
- An onboarding-fit pre-check for non-US/ITIN owners: tell them before they apply which processor will actually clear them, so they don't get trapped after taking payments.
- A monitored status + escalation layer so held funds have an ETA and a human on the other end, not a support macro.
Land on "get your locked payout unstuck," then expand into onboarding advisory for cross-border sellers.
Risks and honest caveats
- Platform dependency: the final verification is Stripe's/Shopify's to grant; the product wins on navigation, persistence, and fit-prediction, and must be honest about what it can't directly force.
- Compliance sensitivity: anything touching KYC handles identity documents — security, data minimization, and staying clearly on the right side of AML rules are entry requirements, not features.
- Adversarial edge: a "help you pass verification" pitch attracts exactly the fraud KYC exists to stop; the product has to serve provably legitimate merchants and design against misuse from day one.
How to validate this further
Read the verification and held-funds threads in the Pain Point Browser, pressure-test demand with how to validate a startup idea, and check the exact wording in the Idea Validator. Related: protection against merchant fund freezes and migrating between payment processors.