#abl - saved payment method
serene scaffold
Hi 👋 yes the user should have already authenticated. The error is returned in this case so your integration can take actions like notifying your customer
fluid bobcat
Thanks, what actions would the customer need to take in this case to authenticate? Will the user get a notification from their bank?
serene scaffold
No, this is something your application would need to handle. You could either request they provide a new payment method or that they simply go through the confirm payment step directly in your application
fluid bobcat
sorry can you clarify by "go through the confirm payment step directly in your application"
my understanding was this happens while the payment info is being saved, so the user would be in a state where they can't get back to this step since its at a later point in time off session
serene scaffold
If the user needs to re-authenticate then the payment intent in step 7 of the guide your shared will fail. So in that case you would re-attempt the same payment but directly as shown here: https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements#web-collect-payment-details
ocean hare
The documentation does say you need to be ready to re-authenticate on any payment attempt - confirming at initial capture is helpful, but banks can decide for themselves to require RE-authentication on any transaction
serene scaffold
You can also make sure to set up that on-session payment intent to save for future usage as shown here: https://stripe.com/docs/payments/save-during-payment#web-create-payment-intent
fluid bobcat
Right I guess I am trying to understand how I can let a user re-authenticate if we are trying to charge them off session
serene scaffold
That's where, in my test integrations, I send an email to the user with a link to take them back to my app and process the payment there.
ocean hare
In my current system, the customer is sent an email when there is an action required, and an alert displayed when they return to the app.