#swe_api
tight laurelBOT
👋 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/1333704621432115241
📝 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.
- swe_file-download-read-error, 13 hours ago, 32 messages
- swe_api, 6 days ago, 14 messages
thorny bison
curl --location --request POST 'https://api.stripe.com/v1/accounts/<connected_acc_id>/capabilities/us_bank_transfer_payments'
--header 'Stripe-Version: 2019-05-16'
--header 'Authorization: Basic <platform-account_sandbox_secret key>'
subtle finch
Hi! Looking into this!
thorny bison
Thanks, Sam.
thorny bison
Hi Sam, any updates?
subtle finch
Hi! Apologies still looking into this.
thorny bison
No problem. Can wait. Thank you.
subtle finch
Thank you for waiting! Can you try it without the Stripe Account header: https://docs.stripe.com/connect/account-capabilities?lang=curl#requesting-unrequesting?
subtle finch
Do you have the request ID?
thorny bison
subtle finch
As per the new request, you are still using the Stripe Account header: https://docs.stripe.com/api/connected-accounts?lang=curl
Can you try without it?
subtle finch
Sorry the latest request still has the Stripe account header. Are you not able to remove it?
tight laurelBOT
wary vault
👋 taking over for my colleague. Let me know if there's any follow-up Qs I can answer!
thorny bison
I have removed it. Not sure why it's recurring.
Sharing you the screenshot of the same
Hello, Tarzan.
wary vault
would you mind sharing the code you're using?
thorny bison
I am trying it out using curl and postman.
It's as simple as the screenshot I've shared above
wary vault
what's the curl command you're running?
would you mind copy pasting it here without the Authorization token please
just leave the sk_test or sk_liveportion
thorny bison
curl --location --request POST 'https://api.stripe.com/v1/accounts/<account_id>/capabilities/us_bank_transfer_payments'
--header 'Stripe-Version: 2019-05-16'
--header 'Authorization: Basic '
wary vault
ok
basically you're using the sk_test secret
to update the account
acct_19o4IFJv9j0DyntJ capability
but you're not connected to that account in test mode
you either need to create that connection or use the sk_live
thorny bison
Under the platform account from which I am using the test secret key credentials, the account - acct_19o4IFJv9j0DyntJ is connected.
The connection is already present.
wary vault
you need to use the live key since the account is only connected in live mode
it's not connected in test mode
thorny bison
I have verified that it's connected in test mode.
If I use live secret key of platform account, I am getting the below error.
{
"error": {
"message": "The account <connected-account-id> was a test account created with a testmode key, and therefore can only be used with testmode keys.",
"type": "invalid_request_error"
}
}
This is the screenshot taken from platform account in test mode.
wary vault
this is a very weird setup
thorny bison
May we know what went wrong here?
We are doing the usual flow, using platform test credential for an account connected in test mode.
wary vault
I'm just trying to understand the flow here
thorny bison
Sure, let me know if you need any help in understanding this.
I basically wanted to enable US bank transfer for all the connected accounts under the platform. I am trying this via API.
wary vault
you don't really need that to achieve this
thorny bison
Okay, how can we do this instead?
wary vault
you can do it from your dashboard settings
thorny bison
I have 1000s of connected accounts, and would like to automate this step.
Not possible to do from the dashboard for every connected account.
wary vault
just let me understand
are you creating the PaymentIntents on behalf of your connected accounts?
thorny bison
Yes, we are.
We are using connected account ID and credentials of platform account to. make any request to Stripe.
wary vault
ok so these are called Direct Charges
you can enable US bank transfer directly from the dashboard
thorny bison
So, using this, can we activate bank transfers without connected account's intervention?
I reached out to Stripe support yesterday, and they said it was not possible.
I am only seeing all accounts as "ineligible" for au_bank_transfer, where as I am trying to enable us_bank transfer. May I know why?
wary vault
So, using this, can we activate bank transfers without connected account's inter...
yes for the Direct Charges you create on your connected accounts
if your connected accounts want to create their own charges they need to enable it on their own dashboard
tight laurelBOT
thorny bison
But, why am I seeing "au_bank_transfer" alone and all accounts are shown as ineligible for this particular platform account?
idle steppe
Hi! I'm taking over from my colleague. Please, give me a moment to catch up.
thorny bison
Sure, thank you.
Also, how do I convert tokens using workbench for all the connected accounts from platform account? This is reg. migrating source to paymetn method tokens at Stripe.
idle steppe
But, why am I seeing "au_bank_transfer" alone and all accounts are shown as inel...
Are you talking about us_bank_transfer? There's no such thing as au_bank_transfer payment method type.
idle steppe
Also, how do I convert tokens using workbench for all the connected accounts fro...
I am not sure about the exact process to migrate Sources to PaymentMethods on the Dashboard. I would suggest reaching out to Stripe Support for that: https://support.stripe.com/?contact=true
thorny bison
I checked the payment methods section -> "for connected accounts" and it gave me account data for which Bank transfer is not eligible. It only has au_bank_transfer_payments in the list.
idle steppe
What is this file exactly?
thorny bison
When I tried to enable bank transfers for all the connected accounts, at the bottom, it shared a list of accounts and why they are not eligible for bank transfer.
idle steppe
I think I am a bit confused. Could you please summarise the situation for me, and do you need help to achieve exactly.
thorny bison
Sure.
I basically wanted to enable US bank transfer for all the connected accounts under the platform. I tried via capabilities API and it did not work. I have 1000s of connected accounts, and would like to automate this step.
Not possible to do from the dashboard for every connected account.
So, your colleague just suggested to use https://dashboard.stripe.com/test/settings/payment_methods/connected_accounts
to enable US bank transfer for all the connected accounts within the platform, since we are using direct charges.
I tried doing that, and I checked the payment methods section -> "for connected accounts" and it gave me account data csv for which Bank transfer is not eligible. It only has au_bank_transfer_payments in the list. I wanted to enable us bank transfer, and not sure why none of my connected accounts are eligible for US Bank transfer
idle steppe
I tried via capabilities API and it did not work
What do you mean by "did not work" exactly?
thorny bison
Yes, we faced an error as mentioned in the initial parts of this discussion.
Later, we were suggested an easy alternative, but that's not working as expected for US Bank transfer
idle steppe
In your case, you should both request the capability and enable the payment methods.
Request https://dashboard.stripe.com/test/logs/req_OGIgowbvORBgjS seems to have failed because your Connected account is connected in Live mode, but you're trying to modify it with Platform's Test mode keys which won't work. You have to use Live mode keys for that.
tight laurelBOT
thorny bison
No, the connected account is connected in test mode, which I have confirmed in the screenshots above.
When I tried via live mode keys, it threw an error as well.
acoustic lodge
thorny bison
Sure, thanks
past bison
Hi there 👋 apologies for the delay. I'm jumping in to lend a hand, please bear with me a moment while I catch up on the context here.
thorny bison
Sure, thanks.
past bison
Correct, the Connected Account was created in test mode.
This issue will require an in-depth investigation from our team in order to figure out the root cause. Can we ask that you write in to us, providing as much detail and context as possible (you can also reference this thread).
Also, you can check the 'developer' box when writing in it will come straight to our team.