#ashleyyy_unexpected
1 messages ยท Page 1 of 1 (latest)
๐ 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/1392208072319176706
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
hello! account capabilities are different than payment method configurations, which is what you're seeing in the dashboard
ahhhhh. That's the thing I didn't understand.
capabilities specify what an account is allowed to do, and adding new capabilities will often trigger requirements for new info to be gathered
so what you want to do here is update the account.capabilities
and specifically the acss_debit_payments part
okay, so does acss_debit have to be one of the account capabilities in order for invoices to be payable in this way?
This has been super different from our experience in the test environment. ๐
yep! it's possible you were doing something different in test mode, if the behavior is inconsistent that would not be great... are you sure you were doing on_behalf_of with a custom account in test mode too?
this behavior is documented here:
https://docs.stripe.com/connect/destination-charges?platform=web&ui=elements#settlement-merchant
can you also share the failing request ID so i can double check some things?
yes. We do all the API calls on our end identically in test mode vs. production, and I only had to update the payment method settings in our platform account, but now Support told me the setting is actually on the connected accounts because of tighter restrictions in the real world.
req_wVvVelXtjNoeLM
oh neat, okay. Adding the capability via the API worked.
ok cool! yeah it's a little concerning if you didn't hit this same error in test mode so i might try to reproduce that for you
If I have the capability now on the connected account, will it show up as an option in the regular checkout? I'm less clear on how all of that works on our end but I believe we're using an embedded component for that.
the capability just determines if we'll allow them to accept that payment at all - whether or not it's shown depends on what payment method configuration (PMC) is being used and if it's enabled in that PMC
and if you're passing the payment method type parameter explicitly, we ignore the PMC entirely
ah, okay. I think for our checkout the payment method config might be configured on the Platform account.
We set it to "Off by default" for our connected accounts in Production, along with ACH but now I'm seeing it as an option in the embedded component for this account - which is extra weird because her presentment currency is CAD. hmmmm
Hello
Taking over here..
Can you share more details? Are you using adaptive pricing?
I am not using adaptive pricing.
sorry, just testing something with a teammate at the moment
so we found that in the platform PMC if I set ACH to "off by default", the connected account has the ability to turn it on in their embedded component, which I don't want but when I did on my test account it created the capability, which is great, if I toggle it back off invoices still work.
I think my last question for you is that if I set it to "blocked" in my platform PMC, will it still work if the accounts have the capability and and we explicitly set the payment method on the invoice/
If you're setting the payment method type explicitly, I believe that overrides your Payment Method Configuration
So it should still work
Correct
okay so what I've done is blocked the pre authorized debit options so they won't show up in places I don't want them to, and once that propagates to all our connected accounts I'm going to test finalizing an invoice with one of my test accounts that has the capability, and we'll know for sure.
that propagation took like an entire day last time so I'm good for now. Thank you for your help!