molawson-bankaccount-method

[calm stream]

molawson-bankaccount-method

[latent obsidian]

Maybe the presence of a value in payment_method.us_bank_account.financial_connections_account? Is that deterministic enough?

[calm stream]

@latent obsidian I don't think that's possible today unfortunately

[latent obsidian]

I'm seeing in my console that instant verification accounts have a value for that field and microdeposit accounts seem to not have a value there.

The issue we're in is that calling confirmUsBankAccountSetup for a microdeposit account starts the microdeposit process. But if that's also the first time we can tell the user "hey, you can't actually give today, you'll need to come back later", there are a number of users who will bail or go back and try another method. But they'll still get the microdeposit.

Even worse, sometimes they come back and decide "fine, I'll do the microdeposit dance". They add the account again and go through the entire process. Then they go to their bank account and see a microdeposit and think "dang, that was fast!" But that microdeposit was for the earlier account they bailed on. So they try to verify the new account with the previous account's descriptor code. They exhaust their attempts. And now they're locked out of adding that account 😭

I don't mean to be dramatic. But that's a situation we've seen several times now and it requires quite a bit of manual intervention to sort it out.

If we had a way to tell whether the account is setup for instant or microdeposit verification before actually starting the microdeposit process, that would be a HUGE help.

[calm stream]

I'd recommend raising this to our support team directly in that case. I thought we handle the "double deposits" in a way where we use the same code to handle this. This seems something the support team would help raise to the product team directly

have you considered starting with "instant verification only" and only offer micro-deposits if they ask for that? That way you know

[latent obsidian]

That's a good question about starting with one and only falling back to the slower process if they want it.

[calm stream]

I do agree with the feedback you just shared so raising it to our support team is important. Just it would take a while to see some improvements so I've seen developers start with "instant only" to avoid that issue

[latent obsidian]

We used to do that with Plaid instant + Stripe legacy microdeposit verification. We've seen enough folks who just want to do instant right off the bat, that the combined setup is nice in other ways. But I forgot we had the option to separate them.

I'll raise the issue with support. Thanks for your help!