Yeah, definitely. I’d love to hear more about the high volume site that they rejected, though, if you’re willing and able to share. I’m just curious what went on in the backend because, in my experience, Stripe is good about not being overly zealous in shutting down Connect accounts. We’ve had accounts rejected for fraud or TOS violations (and they clearly were), but my sense is that had Stripe closed any accounts incorrectly, we very much could have interceded in the merchants behalf and got things corrected.

On the KYC front, if there are difficulties, it’s usually just a matter of Stripe requiring a more rigorous form of verification (such as a copy of photo ID). We’ve never had a merchant to unable to completely KYC and lose their account. Of course, we operate at a much, much smaller scale than Shopify (and in a rather low risk vertical), so surely run into fewer problems and can handle them in a more personal manner.

I wonder, though, how much of this could be Shopify’s inability or unwillingness to handle these edge cases that come up with Connect accounts rather than any malice on their part.

Certainly pushing merchants to a Stripe Connect account and then not letting them go back to a regular Stripe is pretty bad, but, having been behind the scenes in a scenario ms like this, I could see how these could result from poor decision making and incomplete knowledge rather than malice. It’d be easy for someone to make the assumption that if a merchant as a stand-alone Stripe account, they’d obviously not run into any problems with a Connect accounts. Coupled with the fact that companies using Stripe Connect will tend to (not unreasonably) want to drive as much of the processing that happens on their platform into Stripe Connect, so that they can either begin to receiving volumes discounts on the processing or increase the discounts they already receive, which they can use to either make money on the processing or offer more competitive rates to their merchants.