#jrfr23

1 messages · Page 1 of 1 (latest)

red rampartBOT
tribal blaze
#

Yeah each PaymentMethod will have a separated capability. Card and ACH are 2 different payment methods

short juniper
#

You can see in that highlighted sentence it seems to say the card payments capability allows processing card and ach?

#

So if a connect account has the "Card payments" capability it seems like it includes whats also the separate "ACH Direct Debit payments" capability?

tribal blaze
#

Hmm I see. I personally think this Doc could be wrong, but could you clarify with Support? They have better knowledge than us about Account and Capability.

short juniper
#

sure ok thanks will do

#

If you dont mind i had a related question - I was expecting if a capability didnt show for a connect account that the corresponding payment method wouldnt be supported in the payment element and would trigger some sort of error. So for example if i try to use the payment element and the corresponding connect account doesnt have the card or ach capability that it shouldnt allow those payments?

#

does that sound right?

tribal blaze
#

Yeah I think it should error on the PaymentIntent creation on backend, when you specify that payment_method_types. But you are welcomed to try in Test mode 🙂

short juniper
#

yeah im not getting any errors thats why i was so confused, and not only that im specifically calling the connect provision api and NOT specifying the ach debit capability

#

but then I see hours later that the capability appears for the connect account

#

The only thing ive changed is the global payment method "ACH" to be "On" instead of "Off by default"

#

that isnt supposed to just assign capabilities to connect accounts after they are provisioned is it?

tribal blaze
#

Sorry don't fully follow your thoughts. So you changed the ACH option from Dashboard to "Off by default" to "On"? If that so then the PaymentElement, if it's using Automatic Payment Method, will automatically show ACH, is an expected behavior

short juniper
#

oh sorry will try to explain differently

#

i have never assigned the ACH capability to a connect account

#

I have noticed that when I turn the global payment method "ACH" to "on by default" instead of "off by default" i notice that merchants start to get that capability

#

ive created 1 in a brand new test platform account and thats the behavior I observe

#

are the payment methods supposed to have anything to do with assigning capabilities to connect accounts?

#

you can even check the logs in our account friday I created a connect account and you can see it was created from the stripe dashboard

#

you can see the dashboard only requested the capabilities "card payments" and "transfers"

#

but the connect account several hours later gets the "ach direct debit" capability

#

this probably sounds ridicluous but this is the 2nd account ive seen this behavior in and it seems like the way the connect accounts get the capability is if i change the payment method settings

#

which seems like shouldnt be related to what capabilities get assigned to a connect account

tribal blaze
#

when I turn the global payment method "ACH" to "on by default" instead of "off by default" i notice that merchants start to get that capability
Yes I think this is expected, and this setting is indeed related to the capabilities (but Support team could help you better IMO).