#gazzagood
midnight valve
quick question - is this a test scenario you're hitting (so you're using a test card) or is this something you're seeing in live mode?
lone shard
Both, we were seeing failed upgrades in live, but only for some users. We've managed to replicate it in our developer environment.
It works perfect for the 4242 4242 4242 4242
But the Authenticate unless set up and Always authenticate cards trigger this issue every time
midnight valve
Can you share an example test subscription with the Authenticate unless setup card?
lone shard
Sure, what info do you need?
midnight valve
Just the subscription ID would be fine
midnight valve
Ah I see the issue - with that test card you need to be passing in off_session: true (https://stripe.com/docs/api/subscriptions/update#update_subscription-off_session) when you update the Subscriptoin
For the Always authenticate card the behavior you're seeing is expected and is meant to mirror card issuers who choose to ignore/not accept the exemption we pass for recurring charges. You need to make sure your system can handle these situations and bring your customer back on-session to re-provide authentication for these cases
lone shard
Ahh! Yes that makes sense.. Ok we'll test that now and I'll get back to you with the results 🙂
Appreciate the quick help
midnight valve
👍
lone shard
Just quickly, we should be passing off_session for all subscription updates?
midnight valve
If your customer is not there (on-session) then yes, that's what I'd recommend. If you need to bring them back because authentication is still required then you'd want to not set it
lone shard
Got it! Thanks
pearl charmBOT
lone shard
did the trick 😎
Whilst I have you, could I ask one more question
When we create a new subscription, we are passing save default card, it saves the card to the user, but isn't showing a default tag next to the card in stripe
Is there something else we need to do to actually set the card as default?
midnight valve
Are you looking at the default tag on the dashboard when viewing the customer?
lone shard
correct, under payment methods
Also, sorry, one more thing, is there anything we can do to handle upgrades for the Always authenticate cards? Or is there nothing that can be done with these cards?
midnight valve
The dashboard is looking at the default set on the Customer under (invoice_settings.default_payment_method or default_source). If you're relying on payment_settings.save_default_payment_method on the Subscription then that saves a default on the SUbscription, not the Customer
lone shard
Ahhh, is there a way to set a default on the customer during checkout?
midnight valve
No, there's no way to set that automatically (you'd have to set it yourself if you want that behavior)
reef orchid
You can optionally update the customer to set invoice_settings.default_payment_method when you get the session completed event, for example
lone shard
You can optionally update the customer to set `invoice_settings.default_payment_...
Got it, thanks, we'll handle it 🙂 just wanted to check if there was an easier way
midnight valve
And for handling upgrades with the Always authenticate cards the expectation is that you'd need to build a flow that brings your customer back to your site to authenticate - it may be helpful for you to look at https://stripe.com/docs/billing/migration/strong-customer-authentication#settings-3ds-payment (there are dashboard settings you can enable to send an email to your users who need to authenticate to complete payment0
lone shard
Awesome, thank you! I figured this would be the case, we'll adjust our flow a bit to handle this 🙂