#dubes - setup intents

1 messages · Page 1 of 1 (latest)

steep rampart
#

Hello! Just starting a thread for you -- I'll review and respond as soon as I can 🙂

#

Not specifically - it depends on the payment method details. But generally you should create and confirm the setup intent during a single session with the customer, then use the payment method you save in future

#

Payment Intents can be kept around unconfirmed, and its reasonable to keep a single PI for a single abstract "payment" with a given customer

exotic monolith
#

I'm looking at creating SetupIntents for US bank accounts, and we need to hang on to the setup intent for when the user doesn't immediately accept the mandate or confirm the micro-deposits. Is there a minimum timeframe where we can know that it won't expire?

steep rampart
#

Hmm I don't expect there would be specific issues with this, at least I don't see anything called out in teh documentation

#

Certainly we would allow for several days to account for the delays in the microdeposits arriving, since that is not necessarily available right away

#

Ah, here we go

#

There is a callout at the bottom here: https://stripe.com/docs/payments/ach-debit/set-up-payment?platform=web#web-verify-with-microdeposits

Verification attempts have a limit of three failures. If you exceed this limit, we can no longer verify the bank account. In addition, microdeposit verifications have a timeout of 10 days. If you can’t verify microdeposits in that time, the PaymentIntent reverts to requiring new payment method details. Clear messaging about what these microdeposits are and how you use them can help your customers avoid verification issues.

#

So, needs o be completed within 10 days, or you'll have to collect bank details again