#Utkarsh-Plaid-Stripe-Treasury

1 messages · Page 1 of 1 (latest)

keen path
#

Looking in to this. Not as familiar with Treasury, what call are you looking to use the token with?

abstract leaf
#

/v1/setup_intents

keen path
#

As far as I understand, you should be able to use the Plaid Stripe token the way you can use any other bank account token.

Can you describe what you are trying to do here a bit more with the setup intent?

abstract leaf
#

I am trying to use the Stripe Treasury APIs to create a connected account and add a bank account to that connected account without using Stripe JS

keen path
#

I think you need to do something slightly different there. Let me see what I can find...

abstract leaf
#

I did have some additional questions regarding Treasury. For example the documentation says that I should see a platform treasury account with it's own balance under "balances" but I don't see that.

keen path
#

Can you send me the doc for that as well?

#

And as in it should be in your dashboard but you do not see it?

abstract leaf
#

Platform FinancialAccount
During enrollment into Stripe Treasury, we automatically provide you with a platform FinancialAccount that allows you to store your own funds as working capital for your Treasury integration. This platform FinancialAccount has its own routing number and account number and supports all types of money movement.

You can find your platform FinancialAccount routing number and account number in the Treasury balance section under the Balances tab of your Stripe Dashboard.

Different from FinancialAccounts created for your connected account, we currently only support viewing your Platform FinancialAccount in /v1/financial_accounts API.

keen path
#

And then as the first Treasury doc you sent lays out, you can pass the ID of that payment method in as the payment_method for the SetupIntent call

#

Looking in to your second question now...

#

So you are not seeing that account in either the dashboard or from that API call?

abstract leaf
#

correct

keen path
#

They will better be able to look in to your account's set up with that beta.

abstract leaf
#

Thanks

abstract leaf
#

One last question, we are getting an exception when trying to de-serialize a Stripe webhook with stripe-java SDK 20.94.0. Do you know if there is a specific Java SDK version we should use?

keen path
#

Is that the version you are using?

abstract leaf
#

Yes, 20.94.0

red heath
#

mind sharing the webhook event ID?

abstract leaf
#

I think it is evt_00000000000000

#

This is a test event I generated from the dashboard

#

Or it might be this req_mcIUMZGZ6o1BJ2

red heath
#

the request and its API version are actually irrelevant there

#

the Event API version can be entirely different from the Request API version so they are unrelated

abstract leaf
#

2020-08-27;financial_accounts_beta=v3

#

and 2020-08-27
Default
Latest

red heath
#

gotcha

#

that dummy event, was it on your account? or a Connect event meaning it happened on a Connect account?
cause that might be it

the WebhookEndpoint you created we_1KBP9XGAnZyEKADzwNbsUF09
that is a Connect Webhook Endpoint

any real Connect events (like creating a Customer on a Connect account via your own API request, not the evt_0000 dummy event) should work, try that and see, it should deserialize correctly

abstract leaf
#

Ah, I see

#

And do I need to configure another endpoint for the platform?

red heath
#

yes, for events happening on the Platform (not on Connect accounts), it would be an "Account Webhook Endpoint"

abstract leaf
#

And where does one create that?

red heath
#

Dashboard or API, there is a checkbox in Dashboard (IIRC) to create the Webhook Endpoint as a Connect Webhook (or not)

abstract leaf
#

Gotcha. That was my mistake

#

I checked the "Listen to events on Connected Accounts"

red heath
#

np yeah that checkbox creates the "Connect Webhook Endpoint" to listen to events happening on Connect accts

abstract leaf
#

I am hoping I can use the same endpoint for both connected and platform events?

red heath
#

no you have to have separate endpoints

#

they have different webhook signing secrets

abstract leaf
#

Gotcha, that makes sense.

#

Atleast my error changed now:
"message": "Invalid signature: No signatures found matching the expected signature for payload"