#alpha-mouse
1 messages · Page 1 of 1 (latest)
Hi 👋
Can you be more specific about the ACH DD transaction you tested?
Request IDs for your test transactions would help me understand specifically what integration path you are following
req_c4T7LTBCt5LnL4
Okay so the connect account here has the ACH Direct Debit payment method as active.
Hm. Indeed. I don't think the capability was requested explicitly. Let me investigate more. Could it be that as this connected account was created today, and platform already had this capability, that it got it as well this way?
No. Ignore that. I might be lying about not requesting explicitly. I'll do more investigation
Okay, The payment methods are being managed entirely by the platform and you can see tat ACH Direct Debit is available by default without additional verifications here: https://stripe.com/docs/connect/account-capabilities
It says it's enabled by default on standard accounts. And our connected ones are Express. Does it make any difference?
If I switch the account type to Custom/Express in the drop down menuI still see that it is available and supported without additional requirements
Indeed. Why does the documentation on ACH DD say to request it then?
I've investigated more and have found that indeed for the previous account the capability was requested. An example of DD payment for connected account lacking capability would be req_oTlf0KNYwxFyQ7
I think the terminology in the docs is a bit off. The language under the header for Request ACH Direct Debit capabilities simply states that you can turn it on.
Ok. So long story short, the capability doesn't have to be requested for connected accounts for DD to work and that's convenient. Thanks!
Yeah, sorry we went a long way around the barn for that one. And since you are using Destination charges on an Express account, your Platform Account is the one making the charge . So you flip the switch to activate the ACH DD on the Connect Account and charge away
No worries, thanks for the help!