#JeffP-checkout-save-card
vapid sorrel
https://js.stripe.com/v2/ checkout from 2017
this year it has come to our attention that the option for the user to save a card with stripe is no longer there
west veldt
Hmm, I'm not sure I'd need to check on that
Legacy Checkout is fully deprecated now – you should look at upgrading
I think that is set by the rememberMe param: https://stripe.com/docs/legacy-checkout#optional
You still passing that?
vapid sorrel
Yes, a different question I have is what is the quickest path to upgrade from checkout 2. Currently checkout gets a token then we process the token for a charge on server. If there a solution that we can likley keep the server code the same to process the token but a new way to get the token?
west veldt
There's a good guide for this here: https://stripe.com/docs/payments/checkout/migration
vapid sorrel
The session seems to create the charge now instead of a token. How are we suppose to add logic after the session passes for denied cards and or successful payment processes? We use to create the charge and dig through the response to create the logic
west veldt
How are we suppose to add logic after the session passes for denied cards and or successful payment processes?
You'd rely on webhooks to handle fulfilment async: https://stripe.com/docs/payments/checkout/fulfill-orders
vapid sorrel
Would using elements give me more of the approach i am looking for?
west veldt
What specific concerns do you have about the new Checkout integration?
Both Checkout and Elements use the same underlying APIs (Payment Intents), Elements just gives you more control over the integration
vapid sorrel
currently through connect we have processed over 20m this year and we have relied heavy on checkout. Now checkout is failing after years of use and there currently is no support for it (We have tried many times and stripe always says they will get back, here we are a month later ) and our customers are getting angry when their customers can no longer make payments on their phones because the payment button from stripe is greyed out. I do not want to overcomplicate the upgrade and rely on webhooks which will likely fail resulting in incorrect data on our end and "Lost" payments. Super bummed with how much more complicated stripe has decided to make things in the newer version of checkout
is https://js.stripe.com/v3 depricated as well?
heady pawn
Stripe js v3 is the current version
ynoj had to step out, I am catching up on this thread and will be with you in a minute
Sorry to hear about your concerns with upgrading. Is there anything about upgrading that you are wondering how to do at the moment?
To address webhooks specifically, ours are very reliable and we will automatically re-send them if your server experiences any issues and misses them. I understand that listening for webhooks can add complication if your integration was not already using them, but I do want to flag that webhooks in todays integrations are most often a source of reliability rather than something that takes away from it.
vapid sorrel
when using the new checkout session, is it possible that in some way the user can proceed to the success_url if a charged failed?