@tara_seshan @kensavage We have a few use cases on the landing page, that include the following: * Bank account replacement for SMBs and sole props, integrated directly into the platform or marketplace they’re already using. For example, today a Shopify merchant earns their revenue on Shopify but then has to transfer funds out to manage overall cash flow elsewhere (e.g., pay bills). Shopify is building Balance [0] with the Treasury API so this user can manage all of this in one place with a single view of revenue and spend. Other benefits of course include faster payouts, rewards specific to the ecosystem, and adding product features enabled by read/write access to the money management data (e.g. you could roll your own invoice reconciliation or alerts, or give users a discount on your SaaS if they ran sufficient volume on your card). * 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. * Classic Treasury 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.

@tara_seshan @kensavage could a SaaS product use this for embeddable revenue capture and relay to their (own) customers bank account?

@jontronic Closed loop debit, for use cases like stored value or gift cards, aren't supported today. You *can* use Stripe Issuing (https://stripe.com/issuing) to manage exactly where payment cards can be used—but we'd love to chat more about what you're thinking of if you can email us at support-issuing@stripe.com.

@thepbnjay We have quite a few fee structure options, including one that allows for minimal to no transaction fees on ACH. If you're interested in pricing, get in touch here: https://stripe.com/treasury#requ...

@_ritesh_ No solid plans to share just yet, but let's stay in touch. We do want to make Treasury available in APAC!

@mclinton @ellebelle thanks! We've built a great POS solution for CBD retailers but mainstream payment processing options are limited (working on adding our 2nd integration). We're adding compliance functionality as well to attract more bank partners. But there's still a resistance to join an industry that was 100% legalized 2 years ago... It's baffling.

@tara_seshan this is impeccable timing! Eager to explore this for our startup https://hona.io.

@siosism Thank you George... I have been wishing for something like this for a while... get it launched already !

@tara_seshan is the invite a temp thing and will get invites or is it a marketing database campaign?

@tara_seshan nice work Tara! Hope to try this out soon. You are truly one of the top product managers in the valley

@tara_seshan @sbrands It's not a marketing tactic. We often start with a waitlist to gauge early feedback and ramp up overtime. (e.g. Stripe Atlas had a waitlist when it was first announced and now you can get started immediatley.)

@lukestacey85 Just US/USD for now. Working on others!