#hazelnutgelato-Treasury-ToS

1 messages · Page 1 of 1 (latest)

radiant magnet
#

Hi there!

#

Yep only way is via the API

lost plinth
#

Haha of course, fwiw all the other required steps of setting up a custom connect w/ treasury can be done via the dashboard. In any case, have any doc links to where I can find that curl?

radiant magnet
#

Or, you can send them through Custom Onboarding

#

You can't accept the normal ToS via the Dashboard either, no?

lost plinth
#

Yea I just manually made this one because I want to link it to a demo instance in production

#

so where can I find the API side way of accepting those ToS?

radiant magnet
#

Gotcha. If I remember correctly you just pass the tos_acceptance again

#

I'm assuming in this case you added the Treasury capability after you had already accepted ToS initially

#

So cURL should be: curl https://api.stripe.com/v1/accounts/{{CONNECTED_ACCOUNT_ID}} \ -u sk_test_123: \ -d "tos_acceptance[date]"=timestamp \ -d "tos_acceptance[ip]"="ip" \

lost plinth
#

No I just hit "create" in the dashboard and followed the steps there, so I think they just never surfaced the ToS for treasury in the dashboard-side create process.

#

Oh sweet thanks for the curl!

#

was just looking at the docs

radiant magnet
#

Sure. Other way is to use an Account Link and go to the hosted onboarding page where it should also prompt you for acceptance.

lost plinth
#

Ooo I didn't know about Account Links, seeing that now

#

thanks a ton this was all very informative!

radiant magnet
#

Sure thing!

lost plinth
#

All of the above worked, I'm all set 👍

radiant magnet
#

🎉

lost plinth
#

Any chance there's a Treasury channel, or do you all prefer everything goes in #dev-help ?

radiant magnet
#

You said: Me again! I'm getting the error that I need to add an account to support Payouts. But, treasury is Active and enabled. Isn't Treasury supposed to act as the payouts account?

#

(and sorry for not clarifying that you can just post followups in the same thread)

lost plinth
#

No worries, sorry for being the guy on the question spree, I promise this is my last one

radiant magnet
#

So the Treasury capability by itself doesn't act as an external account.

radiant magnet
#

So now that you have the Connected Account active you still need to attach a Financial Account

lost plinth
#

Got it, is that a recent update? What started me on this journey actually is that we had a customer in prod complete the setup flow for custom connect and treasury, but their treasury account isn't being treated as the payout account. For previous customers it has been though. We're an alpha user of Treasury though so things may have changed

#

Appreciate those docs

radiant magnet
#

Hmmm I wasn't very familiar with Treasury during the alpha stage so I'm not sure if something changed. If you give me specific IDs then I can take a look at what might be going on?

lost plinth
#

Yea of course, that'd be really helpful. Just trying to figure out if we need to add a set in our code after they complete custom connect setup

#

Do you want the prod example or test example?

radiant magnet
#

Both would be great

lost plinth
#

One sec, thanks again

#

also seeing here in the docs, it does look like it should be auto-setting the Treasury account as the External/Financial account

#

Stripe Treasury introduces another type of account to the Stripe ecosystem: financial accounts. When you onboard your platform to Treasury, Stripe automatically creates and assigns a FinancialAccount object to your platform account.

#

Here's prod: acct_1LT8MdQ6X8ccLzAa

#

here's test: acct_1LcbaxQ3ZQWyEzfm

radiant magnet
#

Yeah it assigns a financial account to your platform, but not the Connected Account as far as I know

#

Give me a few minutes to look at the above accounts

lost plinth
#

No problem, thank you! And yea I do see that on the prod one that it says "financial account active"

radiant magnet
#

Okay sorry server got busy. Taking an actual look now

lost plinth
#

All good, I really appreciate the help

#

If I can understand this well enough we may be able to configure our onboarding to let folks choose between using their existing bank account for payouts or Treasury

radiant magnet
lost plinth
#

wow sorry for the delayed response, had notifications off

#

looking at this now

radiant magnet
#

No worries

lost plinth
#

Yup, I see that. If I'm understanding correctly, that only happens because we're using Treasury yea? If we were doing normal custom connect there would be no need for that financial account creation? And, that created financial account should be being automatically set as the account to send payouts too, correct?

radiant magnet
#

Yep that's correct.

#

You can just create an External Account as normal for payouts without Treasury

lost plinth
#

So if that financial account is being created on the prod one, why isn't it being auto-set as the external account?

sand flame
#

Hi 👋
I"m stepping in for @radiant magnet . Give me a minute to catch up

#

Okay so I'm looking at the recent events on the Prod account (acct_1LT8MdQ6X8ccLzAa). I see a banking account is created. Then financial account status is updated and features are added. Finally the treasure.financial_account.features-status_updated event fires:
https://dashboard.stripe.com/events/evt_1LaS1cQ6X8ccLzAakrO3w4VN

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

lost plinth
#

That link isn't working for me, but that all sounds correct

#

but I'm not seeing why it doesn't have the financial/treasury account set as the account to send payouts to

sand flame
#

Oh, that event is on the Connect Account

lost plinth
#

got it, see that now

#

but yea, before this month that process would result in the treasury account being auto-set as the External Account to send payouts too

#

but now it's coming as "Restricted" because there's no external account

sand flame
#

Okay, do you have any example accounts where it did set the new treasury.financial_account as the default for payouts?

lost plinth
#

yup!

#

Here's one

#

both of those are in production

sand flame
#

I see the request for a financial account but then about 2 hours later there's an API request that makes a standard External Account for that Connect Account

lost plinth
#

Yea but I'm quite sure that's not us, it's Stripe. Because the account created is a Treasury account. It's Evolve Bank, that's the Treasury partner. So our customer didn't make that bank account and neither did we. It was generated by Stripe

sand flame
#

That API request was not made by Stripe. It was made the the secret API key belonging to this account (acct_1EulNtLSbxUgPeeE) and it was made using the Stripe NodeJS client library.

lost plinth
#

Hmm ok that does sound like us haha, apologies for that. And that request set the existing Financial account as the external account?

sand flame
#

It provided all the details for an entirely separate External Account.

external_account: {
    object: "bank_account",
    currency: "usd",
    country: "US",
    routing_number: "0******8",
    account_number: "*********4",
    account_holder_name: "PracticeProtection Insurance Company (a Risk Retention Group)"
  }

this was the payload (with numbers obscured).

#

Same situation with the second. A separate POST request was made to /v1/accounts/acct_XXXXXX to create an external account with all the details for the bank (routing and account numbers)

lost plinth
#

Sorry for the delay, had to hop to another call, but I'm certain those are both Treasury accounts. Are you able to see if those are the same as the Financial Accounts?

sand flame
#

Nope they are not. The details may be the same but they are created as separate and independent records from your servers

lost plinth
#

Ok, I don't think I can be productive with your time without looking at our own code more. I'm very confident that those Treasury accounts were being set up automatically by Stripe, but let me dig into it more on my side. Thanks for all the help so far!