#ghadgraft_api
frigid latchBOT
👋 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/1268522578142826516
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
hallow sequoia
yes it has been working without the issuer parameter
lunar ridge
Seems like a faulty error message. Let me check what's actually happening...
Still looking...
hallow sequoia
If a call (via google hangouts, zoom, etc) would be useful heppy to jump on.
lunar ridge
I understand the problem. I am just trying to understand why this specific error message was chosen on Stripe side. I just need a few minutes.
warm ivy
hmm I'm not 100% sure this (gb_bank_transfers with Connect with the connected account being the one offering the method and creating the VBAN) is supported, not really clear form internal/external docs. But for example there isn't an capability you can request for it for the connected account https://docs.stripe.com/connect/account-capabilities which is what is making me doubt this)
hallow sequoia
This is working via test mode. The outlet has branding and details for the connected account however the banking details are for the platform account
The same code produces this PDF, the capabilities for the 2 accounts seem to be the same as far as i can tell
hallow sequoia
I think this was the request that generated that invoice https://dashboard.stripe.com/test/logs/req_l1tGXAsLx3S5fP
warm ivy
hmm
yeah that's weird. I have no idea, sorry. I'd suggest opening a support ticket at https://support.stripe.com/?contact=true so we can escalate and dig into it in more detail.
digging into the code a bit my best guess is it only works if the connected account has banktransfers enabled in livemode too
or rather I suppose it's because it's because "acct_1DLTbII7hAh17KrA" is not a "real" test mode account, it's an old/real livemode Stripe account you connected to over OAuth and are able to make test mode requests on due to the way that flow works, so we're checking some livemode status of it
it probably works fine on "real" test mode accounts like ones you create in the API or with testmode redirects, which is what the connected account in your other example is. So I'd suggest using that account and others created that way , to test
frigid latchBOT
hallow sequoia
I'm a bit confused by that statement above "acct_1DLTbII7hAh17KrA" is not any kind of test mode account it's a connected account on our live account. Did you mean another account there?
Could you try explaing that again please. What do i need to do in test mode to recreate what is happening in production.
warm ivy
I mean it's not an account explicitly created as a test mode account via using a test mode API key (e.g. https://docs.stripe.com/connect/custom-accounts#create ), rather it was created in the old way where you would visit the OAuth redirect page for your platform, and that creates a "full" Stripe account, you connected to it in livemode, and that also implies access in test mode.
but that "implied" access sometimes has problems and I suppose this is one of them. In your working example for
acct_1GIcfGEqkFbuCxIT it's created normally as fully test mode via an API request, and it works
so I suggest — just test with acct_1GIcfGEqkFbuCxIT, or create a new test account in the same way, and use that, and ignore that old 2018 connected account.
ah right it's a live mode account and livemode request , thought it was test mode, so ignore that I suppose.
Then I'm back to — I don't know. My best guess if the connected account needs to enable gb_bank_transfers in live mode for this to be able to work but I can't see how that can be done. I'd suggest a support ticket for deeper investigation.
cunning agate
Hmm, the banks transfers PM is disabled by default on the platform's connected account PM config: https://dashboard.stripe.com/settings/payment_methods/connected_accounts?config_id=pmc_1LNGuZAXxcazmLcJib8LZ36e
Might explains why there's no capability for acct_1DLTbII7hAh17KrA
hallow sequoia
We did see that but the bank transfers PM appears disabled. But from an earlier conversation my understanding would be that bank trasnfers would still go through the platform account where bank trasnfers have been previously working
cunning agate
Which earlier conversation? Working where? Overall though, I think this would be best escalated to our support queue (https://support.stripe.com/contact/email?topic=api_integration) and we can take a deeper look there