#aham1141_api

1 messages · Page 1 of 1 (latest)

trail folioBOT
#

👋 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/1334289727096094771

📝 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.

molten dragon
#

From the GO SDK:

#

// The ID of a Payment Method with a `type` of `us_bank_account`. The Payment Method's bank account information will be copied and // returned as a Bank Account Token. This parameter is exclusive with respect to all other parameters in the `bank_account` hash. // You must include the top-level `customer` parameter if the Payment Method is attached to a `Customer` object. If the Payment // Method is not attached to a `Customer` object, it will be consumed and cannot be used again. You may not use Payment Methods which were // created by a Setup Intent with `attach_to_self=true`. // This is used for TokenParams.BankAccountParams only and will be removed in the next major version. // **DO NOT USE THIS FOR OTHER METHODS.**

#

^ That is the payment method parameter. I do not have a customer as this is attached to connected treasury account not a customer.

#

attach_to_self is false

cerulean onyx
#

Hi, I'm unable to hold your hand or write your code for you. However, I'm happy to partner with you.

molten dragon
#

That would be great

#

Interestingly the code flow works if I do the whole thing against my root account (not the connected account) and then attach the result to the connected account in the last step.

#

Is that how this is supposed to work?

#

requests:


req_zuUO77v73d7nC6 (/v1/tokens)

req_5McVQ60mP2tKn1 (/v1/accounts/acct_1QmgOBH0O8KPfzIH)```
cerulean onyx
#

Still looking here

#

I'm asking for help from a teammate as I can't see what the issue might be right off the bat

#

Thank you for your patience

molten dragon
#

No worries. I am currently trying to figure out if I can somehow turn the attached external account into a payment method that works. So just experimenting 🙂

trail folioBOT
pale siren
#

Hi hi! Why are you attempting to tokenize the result?

molten dragon
#

The thing I am ultimately trying to accomplish is adding an external bank account to a connected account that I can then use to issue inbound and outbound transfers on

#

Basically: Create a SetupIntent -> show the UI -> Confirm the Intent -> Tokenize the result -> Add it to the connected account as an external account.

molten dragon
#

Right now I can make this work by creating the SetupIntent against my root account, tokenizing it, and then adding it to the account. Which is great (althoughI would like confirmation that is intended behavior).

#

The thing I am at a loss as to how to do is to then use that attached BankAccount to actually create a PaymentIntent

pale siren
#

Ok, I think I see what's going on here.

molten dragon
#

The resulting PaymentMethod isn't meant to be attached to a customer tho?

#

It's a SetupIntent for a Treasury Account. I'm not really sure who or what a "Customer" is in this context.

#

I guess my question is: can I use a PaymentMethod that is attached to a Customer to initiate Inbound and Outbound transfers from a Treasury Account?

pale siren
#

The documentation you're following is for Connect and Connected Accounts.

molten dragon
#

I have no documentation specific to Treasury. And my understanding is that Treasury is just a connected account with a FinancialAccount attached to it.

#

Which creates a SetupIntent that uses "AttachToSelf" to attach the resulting PaymentMethod to the Connected Account. Which works great. Except that there is no way (that I can find) to then use that PaymentMethod to satisfy the external_account requirement on the Connected Account.

#

Like you end up with a PaymentMethod that will happily transfer money in/out (on Sandbox at least)

pale siren
#

I'm sorry for the confusion here, but we can'

molten dragon
#

But payouts are disabled because there is no external account in the connected account.

pale siren
#

I'm sorry for the confusion here, but we can't generally support gated features in Discord, so your best bet is likely to reach out to support - but I can tell you that your even better bet is to follow the Treasury-specific guides for all the work related to this.