#longbeard1215
lost basinBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- longbeard1215-account-support, 1 day ago, 5 messages
spark thicket
Hello
Yep that's the correct way to do this.
I don't believe you set permissions on the client though
stuck bluff
So I am clear, this will incur a charge due to the instant verification. Is the charge any different based on the permissions? Or would you know?
spark thicket
I don't believe the charge is different based on the permissions but yeah we don't really know much about fees so you'd be better off confirming that with our Support team via https://support.stripe.com/contact/login
stuck bluff
I don't believe you set permissions on the client though
https://stripe.com/docs/js/elements_object/update#elements_update-options-paymentMethodOptions
I was confused about setting them on the client as well. It seems they are there though?
spark thicket
Ah yeah my bad. You do set both on the client as well
This is assuming you are using the deferred intent flow
Where you create your Payment Element before creating your PaymentIntent
stuck bluff
I do. It's also been running for a month without the settings on the client. I don't see a difference. Caught that today while doing some updates
spark thicket
The difference would be that microdeposits would be an option if you don't specify it on the client
And the permissions would be the default
stuck bluff
OK, I had left off the permissions. The verification_method was always there
spark thicket
Gotcha
stuck bluff
One other question. If I am not creating a customer when I create this intent, Stripe will do an instant verification for the same payer and bank account if they pay again at later date, correct?
Similarly, if I do create a customer, but do not use the set_future_usage the same will occur.
Said another way. The only way to avoid doing an instant verification for an ACH is if I both create the customer and also use set_future_usage and re-use the payment method
I know you don't deal with fees, but I am trying to understand the relation of what I do programmatically to the costs we incur
spark thicket
Yes the above is correct
If you don't attach the PaymentMethod to a Customer then you can't re-use it
And you would have to create a new one each time
stuck bluff
thank you