On Stripe Connect, the support tickets that never end are the verification ones: an account that looks finished but is "restricted", a payout that won't release, a document rejected for a reason the seller can't parse. It isn't your integration - it's where the KYC burden sits. Here's exactly why connected-account verification gets stuck, mapped to Stripe's own requirements (July 2026), and the structural way to stop fighting it.
When Stripe can't automatically confirm a representative, it escalates to Stripe Identity - a document check plus a live selfie matched against the ID photo. Real people fail it: Stripe lists rejection when "the captured face image did not match with the document's face", when it "couldn't verify the provided selfie", or when the image is flagged as "manipulated". It's typically one shot on a phone camera, and there's no fast human override - so a legitimate director can be locked out of their own onboarding over lighting or a camera glitch. Source: Stripe Identity - selfie checks · Connect identity verification
An ID often isn't enough. For many representatives Stripe additionally requires a proof of address, and it's fussy about it - recent enough, matching the name, an accepted document type. The seller believed they were finished at the ID step, so this extra round arrives as a surprise and a delay, and each rejected utility bill is another day the account can't go live. Source: Stripe - required verification information
Stripe must identify and verify every individual owning 25% or more of the business. A generic incorporation document won't clear it - the proof has to show each beneficial owner's full legal name and their exact ownership percentage. Layered, trust-held or foreign ownership structures don't map onto the standard fields, so they stall outright. Stripe effectively conceded this by adding a dedicated "proof of ultimate beneficial ownership" document type in January 2025, because "the existing KYC fields might not sufficiently capture your company's UBO declaration." Any seller more complex than a single owner is a candidate to get stuck here. Sources: Stripe changelog - UBO document · Stripe - ownership & director requirement
Stripe models verification as a set of requirement buckets on the account - currently_due, eventually_due, past_due - plus a disabled_reason when things go wrong. As deadlines pass or thresholds trip, an account that was fine silently moves to "restricted", and the platform has to detect it, interpret it and collect the new documents (often by sending a Stripe remediation link). It's not a one-time form; it's an ongoing obligation that lands on your team and your seller repeatedly. Sources: Stripe - handle verification updates · Stripe - remediation links
The requirement buckets have teeth. Until they clear, Stripe can pause charges or payouts on the connected account - so a seller who made sales can't get their money. Nothing drives a support escalation, or a public review, faster than "I earned it and I can't withdraw it." For the platform, it's the worst possible moment to be the one holding the seller relationship but not the licence. Source: Stripe - handle verification updates
Even a clean, verified account isn't settled. Stripe states its KYC requirements change "due to regulatory and financial institution changes", and it re-opens requirements on already-live accounts through future_requirements. So verification isn't a milestone you pass once - it's a moving target your sellers have to keep re-clearing, and every re-open is a fresh chance to lose them. Source: Stripe - future requirements
Every problem above traces to one design choice: on Stripe Connect, you are the platform onboarding sub-merchants, so the verification burden, the remediation work and the sub-merchant liability land on you - while Stripe's risk engine decides, on its timeline, who passes. You get the tickets; you don't get the control.
| Verification reality | Stripe Connect | paas.build / unipaas |
|---|---|---|
| Who runs KYB/KYC | You surface it; Stripe decides | UniPaaS runs it end to end |
| Seller transacting during checks | Usually blocked until cleared | Yes - real capped account, same session |
| Failed liveness / rejected docs | Your ticket to resolve | Handled by the institution |
| Re-opened requirements later | future_requirements on live accounts | Managed by UniPaaS, not you |
| Regulated sub-merchant liability | Yours as the platform | UniPaaS, FCA-authorised PI (No. 929994) |
Stripe behaviours are from Stripe's public documentation, July 2026. Onboarding figures are UniPaaS platform averages; your numbers depend on your seller mix and market.
Create a real account and onboard your sellers today - live the same session, verification handled in the background.
Open my accountDrowning in verification tickets, or have a specific seller mix? Leave your email and our CTO will design the setup and pricing around your platform.
Stripe restricts a connected account when a verification requirement is outstanding - a representative's identity or selfie couldn't be confirmed, a proof of address or beneficial-ownership document is missing or rejected, or new requirements opened because Stripe's KYC rules changed. Stripe exposes this as the account's requirements (currently_due, past_due, disabled_reason); until they clear, charges or payouts can be paused.
Any individual who owns 25% or more of the business, or who otherwise exercises significant control. Stripe must verify each one, and the ownership document has to clearly show each owner's full legal name and exact ownership percentage. Complex or foreign holding structures often don't fit the standard fields, which is why Stripe added a dedicated proof-of-ultimate-beneficial-ownership document type in 2025.
Payouts pause when the account has an unmet verification requirement, or when Stripe re-opens requirements on an already-live account through future_requirements after a KYC or regulatory change. The money is held until the seller supplies whatever Stripe now asks for - which is where sellers churn.
Yes - paas.build on UniPaaS (an FCA-authorised PI, No. 929994) uses progressive KYB: the seller gets a real capped account immediately and verification completes in the background, while UniPaaS runs KYB/KYC and carries the regulated sub-merchant liability instead of your platform. 80% of sub-merchants are fully onboarded in an average of 12 minutes.