#dpelkey98
ancient vaultBOT
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.
- dpelkey98, 6 days ago, 7 messages
hybrid saffron
hi! hmm well not really. The way it works is either
- you process a payment now, and run 3D Secure during that payment. You can save the card during the payment using
setup_future_usage - you save the card now, and process a payment later. At the time you save the card you use a SetupIntent to that, and the SetupIntent can run a "non-payment" 3D Secure transaction, and that having been done allows exemptions to be claimed on future payments on that card
as a corollary, you can combine option 1 with manual capture https://stripe.com/docs/payments/place-a-hold-on-a-payment-method to delay when the actual funds move. But 3DS happens at the time you authorise the payment.
pastel ferry
Right, I save them now using setup intents. Can I reverify them somehow? I just need the best chance possible for the cards to get charged at a future date while the user is off-app
pastel ferry
as a corollary, you can combine option 1 with manual capture https://stripe.com/...
I've looked into this, but we have opted into not holding funds as the process can take longer than you allow us to hold the funds for our business category
Essentially a user submits a "proposal" with an attached total and pre-saved payment method. Once the receiving user accepts it, then both users are charged. Hence one user being off-app and stumping the flow if a 3DS issue comes up
hybrid saffron
Hmm no you can't really reverify and I don't think that's needed. If you set up the card then that's it, you have the best chances already. What happens when you process the off-session payment later is we will claim an exemption and it's up to the bank to grant it.
pastel ferry
I see. And a theoretical question: if the off-session payment fails for a card, and I walk the user back through 3DS in-app to confirm the payment intent. How likely is it that the off-session payment for the same card will fail a second time? Is this even measurable, or does it still depend on the bank?
Really I'm asking, if a card fails off-session, is it safe to assume that it shouldn't be used again off-session?
hybrid saffron
I don't know the answer to that question.
as far as I know you should just try off-session each time. There's no harm. You need the recovery flow of re-attempting on-session in any case so you can always go to that if the off-session attempt fails.