#CodyL-ACH-verification
1 messages · Page 1 of 1 (latest)
Yes
It kind of creates the impression that the customer is done
Rather than that they have just inputted the information of their bank account
And they still need to click submit before that's transferred to stripe to update the setup intent
And by submit I mean the add bank account button
I don't necessary want to control the language, but I think it should be updated to say something like "once added your account will be verified by micro-deposit verification...."
The way it flows now I can see users abandoning the process after clicking done because well they think they are done.
done should probably say next as well
Hi @alpine lake! I'm stepping in for @haughty sand as they need to step away. Give me a moment to catch up
The "Add Bank Account" button is your own UI, right?
correct
that is the final step that submits the element to stripe
that calls the stripe.confirmSetup
see what I'm talking about with how that reads. Some users are going to see that as they are done and the micro deposits have been initiated
when really nothing clicks off until you click submit the form for the stripe element
Gotcha. I think this is fair feedback, but the "Done" button allows for flexibility on the developers end with how/when they want to confirm the SetupIntent. Basically the generic nature here allows for more flexibility overall. It sounds like you will want to add something to your UI that indicates they must click "Add bank account" after completing the modal.
well I think they must either way
I thought about clicking it for them after the element was "complete" and valid
but then that kind of is in conflict with the displayed mandate text
You will see a $0.01 deposit in your account in 1-2 business days. Then you'll get an email with instructions to complete payment to Clearfly.
By saving your bank account for Clearfly you agree to authorize payments pursuant to these terms.
which shows up below
feels like the user should be clicking
that is stripe generated langauge
Wait actually one sec.... I thought that modal was dependent on SetupIntent confirmation.
I haven't played with that flow in a minute, let me review
Routing: 110000000
Account: 000123456789
are the test numbers
that is for when you are entering the account numbers manually
Can you provide your account ID that is linked to that page? Would like to take a peak at the flow on the account for this route
That works
you can submit it or whatever
all test data
I'm just using the payment element which I use for cards as well with a different allowed payment method type, but maybe I should be using. https://stripe.com/docs/js/setup_intents/collect_bank_account_for_setup
seemed like the payment element was the prefered way but maybe I misread that and went down the wrong path.
what I have does work other than being a bit confusing
Yeah okay, I do see what you mean and I think you are doing everything correctly.
As you noted, the customer has to agree to the mandate terms in order to confirm.
I know it's a bit new
I think this is good feedback for our team
Yep agreed. I don't think there is a real workaround right now.
But I do think we can make the modal more clear
No problem. Just want to make sure you all were aware.