Re:How Shopify Manages API Versioning and Breaking Changes
by Judson on Thursday December 19, 2019 @10:17AM
(#21835547)
You know, you just jogged my memory here. We did have an issue with Stripe changing the order / timing of payment_failed webhooks, which caused them to be sent before the next payment attempt was known.
We used the payment failed hook to send an email to our customers and let them know when we'd be retrying the charge, which was no longer possible because the next_payment_attempt field was null. Before the change, a next_payment_attempt=null meant the charge would not be retried.
I reported the issue and the webhook changes were rolled back a month later. Really threw a wrench into our flow.
I will say that generally speaking, Stripe is the canonical backwards compatibility API in my mind. With a few edge cases.
Re:How Shopify Manages API Versioning and Breaking Changes
by rudasn on Thursday December 19, 2019 @12:04PM
(#21836749)
Not sure if this helps but there was an issue with chrome submitting forms multiple times recently. It has been fixed in the recent 79 release.
Re:How Shopify Manages API Versioning and Breaking Changes
by gingerlime on Thursday December 19, 2019 @07:16PM
(#21840652)
It’s not that. Purely a Stripe backend change in this case. They confirmed it but I’m still waiting for more details.
... Until just recently in mid Nov they changed some behavior that caused us to double/triple/quadruple charge customers unintentionally in some not-so-uncommon edge cases... I’m still trying to square this one with their support, so details are a bit thin. But definitely a big surprise for me to see this happening when previously I never imagined something like this can happen given the API versioning stability.