#aham1141_tokenizing-bank-details-for-connect

1 messages · Page 1 of 1 (latest)

eager hingeBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1341531040434487357

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

thorn mortar
#

Hi! What exactly are you trying to accomplish here?

regal mural
#

I am building an issuing application using Stripe treasury. I have been battling one basic problem for like a month: a treasury connected account requires an external bank account. We want to use the Financial Connections UI to do this. We ALSO want to be able to use that resulting account for payouts and top-ups.

Which I can't make work. The reason is that in order to attach an external bank account the payment method must be tokenized and then added to the connected account. You simply can not create a SetupIntent, load the financial connectinos UI, and then tokenize the result if the SetupIntent is created using the connected account iself. You must use the platform account.

So you end up in this state:

  1. A customer is created in the platform account because it has to be in order to use it for the SetupIntent.
  2. A SetupIntent in the platform account.
  3. A PaymentMethod is added to the Customer after they complete the financial connections UI.
  4. A Connected Account has an external bank account.
  5. There are no accessible payment methods on the connected account.

So #5 is the problem. I have to ask the user to go through the whole process again, this time using a SetupIntent in the connected account (with AttachToSelf=true). Which I really don't want to ask the user to do.

thorn mortar
#

What documentation are you using to guide you through this?

regal mural
#

Here is a crude drawing of what is happening

Untitled_presentation.png
thorn mortar
#

That's not what you're trying to do though, right?

regal mural
#

I think it is?

thorn mortar
eager hingeBOT
#

aham1141_tokenizing-bank-details-for-connect

regal mural
#

The InboundTransfer requires a PaymentMethodId and the result of all of this is that there are no valid Payment Methods anywhere in the connected account (they all exist in the platform account).

thorn mortar
#

Learn how to transfer money from another account you own into a Treasury financial account.

You don't 'own' the Connected Account though?

#

Also, unless you followed the step from the link I just sent you that 'copies' the payment method onto the Connected Account, then no, you wouldn't have any payment methods there.

regal mural
#

Doesn't the platform account "own" the connected account? I have full permissions to it

#

That step creates an external account on the connected account which is not a payment method (I honestly have no idea what external_account is exactly, but I can find no way to access a payment method from it)

thorn mortar
#

That's the Connected Account's "pay my money into here" account.

regal mural
#

So if I want to do a top-up ("put money into my treasury account") is there no way to do it without asking the user to create a whole different payment method?

thorn mortar
#

Ok, let's take a step back. What does your app do?

regal mural
#

We issue cards to people in the beverage alcohol industry (basically Ramp for our specific niche)

thorn mortar
#

Using Stripe Issuing?

regal mural
#

A user signs up with us, we create a connected account (and a treasury) account on the backend and issue them charge cards (NOT credit cards)

#

Yes using issuing

thorn mortar
#

Ah ok.

#

Why the treasury account?

#

Why are you creating a Connected Account?

regal mural
#

The treasury account is required to provide the money for the charge card

#

I am creating a connected account because it is required for the treasury account

thorn mortar
#

Connected Accounts are for platforms like Lyft/DoorDash/Uber etc, or for marketplaces like Shopify - where there are three parties involved: the platform, a customer, and a service-provider.

This doesn't sound like the model you're describing - it sounds more like "we have multiple customers and we give them each a payment card and provide controls, reporting, etc, but they're all customers of me/my business/my app"

Correct?

regal mural
#

That is correct

thorn mortar
#

Then using Connect is not correct.

regal mural
#

"If you need to issue cards for users that aren’t directly employed by your business, set up Stripe Connect for your Issuing integration. For example, a business building a new expense management product for small businesses can integrate with Connect. Each small business that uses the expense management product is set up as a connected account."

thorn mortar
#

Gotcha, ok.

regal mural
#

That second link is super helpful. Thank you!

thorn mortar
#

You're very welcome!

eager hingeBOT