thomas_api

[tribal cedar]

👋 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/1234654334025859203

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[hybrid bison]

More context: As for why our flow works in test mode, I discovered this thread https://discord.com/channels/841573134531821608/841573134531821616/threads/1120286368380235907 that says test mode does not check if the payment method is enabled for an account. I assume this is why we can show the modal to link an external account in test mode even though the us_bank_account_ach_payments capability isn't enabled at this part of the flow (it's enabled later for us).

So now I am figuring out how to fix production for us. I tried enabling the us_bank_account_ach_payments earlier in test mode, but we do not have required info to enable the capability (like ownership info) at this part of the flow yet.

I see in the Payment Methods tab that there’s ACH Direct Debit which we have turned off by default but seems to be very related to this capability.

Some of our accounts do have the us_bank_account_ach_payments capability because we request it later in our flow. I notice that for these accounts, the us_bank_account_ach_payments shows as a capability in our dashboard, but ACH Direct Debit payment method remains off. However, linking an extrnal bank account with stripe.collectBankAccountForSetup works for these accounts (just not earlier in the flow which we desire). I’m wondering why the capability and dashboard setting don’t turn on and off together?

My thought is that we could set the ACH Direct Debit payment method to “on” by default in place of requesting the capability, but that opens up some questions like:

• If we turn on ACH Direct Debit in the dashboard, will we still be required to provide additional info (like ownership) which is required by the us_bank_account_ach_payments capability?
• Will turning this setting on even fix our problem of stripe.collectBankAccountForSetup with the us_bank_account payment method not working in prod? Or do we need specifically the capability. I think I’m unclear what the difference between the dashboard setting and the capability are.

Because of the mismatch between test and prod, it’s hard for us to do our own experiments, because we can’t do testing on production. So I am hoping you guys will have some better knowledge of how these pieces work 🙏 Ideally there’s some way to avoid refactoring our onboarding flow.

[trail thunder]

Hi there, I believe us_bank_account_ach_payments is the capability name and in order to have a capability, you need to both turn on ACH Direct Debit in Dashboard, and then provide required information for the account. The final result of having or not having us_bank_account_ach_payments will reflect in the capability.

I notice that for these accounts, the us_bank_account_ach_payments shows as a capability in our dashboard, but ACH Direct Debit payment method remains off
This sounds a bit odd, but probably after the capability is granted, someone toggle off the settings in the Dashboard. You would want to reach out to Support to help checking on those accounts. But in general, having the capability means you can accept ACH Direct Debits from your customers

[hybrid bison]

Ah ok I see. Thanks for the clarification. So the us_bank_account_ach_payments capability is a strict requirement, and turning the ACH Direct Debit dashboard setting "on" alone without the capability is not enough to link bank info via api?