[pbalau]

> Stripe Treasury does not violate our terms, and allows SaaS platforms (and similar) to provide their business users with access to capabilities which are regulated with those capabilities fulfilled by entities with the appropriate licensing and backed by our financial partners.

Ha? What does this mean?

[tfehring]

My very speculative reading of this: Stripe needs to fulfill KYC/AML requirements for its own customers, but not for its customers' customers. If I own a store and accept payments via Stripe, Stripe needs information about me to help make sure I'm not using the money I receive for unseemly things. But if you visit my store and buy something and pay me via Stripe, Stripe doesn't need that same information about you.

If instead of running a store I'm running a bank or some other financial service, that all changes - in that case, someone has to verify your identity to fulfill KYC/AML requirements. Stripe doesn't trust me to do that myself, since it's hard and heavily regulated and it would be onerous for Stripe to make sure I and all their other customers are doing it properly. But now they'll outsource that responsibility to banks on my behalf.

[smallnamespace]

I read it as:

> ... provide their business users with access to capabilities which are regulated_,_ with those capabilities fulfilled by entities with the appropriate licensing ...

Short version: we do the hard things for you so you don't have to. Correction welcome if that comma doesn't convey the intended meaning.

[pbalau]

The comma I got on my own, after some time. I'm still not clear on what those capabilities are.

[strogonoff]

Capabilities = stuff described on the landing page. If you provide that stuff yourself, you’d be breaking Stripe’s terms. If you use Stripe’s mechanisms, which under the hood delegate to entities Stripe trusts, you’d be fine. (IANAL.)

[graeme]

Financial or banking capabilities, I think