#unclecarl2.0
1 messages · Page 1 of 1 (latest)
Hey Toby, hope you're having a good one so far.
Hi 👋 thanks, it's going alright!
Hm, I'm not too familiar with Treasury flows, but I think if we have a product to support that, it would be Treasury. Connect can't let you do nested layers of entities like that well. Let me see what I can find.
awesome thanks! we've been using connect very successfully and love what ya'll are doing. If we can set this up through Treasury or whatever structure works best, we're all for it
Taking a closer look at the Treasury flows, it seems like they're largely built on top of Connect Concepts, so my fear there is the same limitation would be a concern. Do they strictly need to be three-tier? Sort of like
National
- State
- - Local```
(hm, discord did not format this the way I hoped)
or could the structure be flat with a single platform orchestrating the flow of funds between the accounts
Platform
/ | \
nat. state. local
Gotcha, in that case I think Treasury should work. You'd be the Platform account responsible for orchestration, and each entity would be a Connected Account with an associated Treasury Financial Account. I believe that will allow your Platform to move funds between those Connected Accounts as needed.
Excellent! thanks for your help. Where would you recommend we start or are there any docs in particular that we should be aware of?
I think this is probably a good starting point:
https://stripe.com/docs/treasury
It's our topmost doc for Treasury, and has a series of docs underneath it to walk through flows, requirements, and implementation guides.
solid thanks. definitely appreciate it