* Open loop wallets, like offering a “spend” account within your product that a user can either use to buy in-product purchases, or use the card/ach/wire functionality to buy external goods. E.g. a car leasing platform for drivers adds Treasury, drivers can use the wallet for discounts on car leases, also use the card to spend on gas.
* Product operations, like having a platform-level Treasury balance you use for reserves, chargebacks, and as glue to make your product flow work. E.g. On demand services marketplace that “buys items customers need and delivers it to their door” can issue cards from a central Treasury balance to their drivers, so that they can use a physical card to buy the burrito for the customer at the restaurant.
...but part of the point with Treasury is that we don’t know every use case prior, just like we didn’t know every way developers would use Stripe Connect (developers are pretty creative!). Our goal was to build for specific use cases, of course, but also build composable enough primitives that people could recombine them in ways we didn’t imagine. We wanted to make a tool that helped unlock developer creativity, because flexible tools were so lacking in the existing fintech infrastructure space.