#bdanforth-subscription
1 messages ยท Page 1 of 1 (latest)
We have a cache that updates on webhook events (fetching the latest object directly from Stripe), and right now I see that while the customer in Stripe has a currency of "usd", our cache is still null presumably from originally creating the customer when we did not yet have payment info.
So in this case the currency was changed when you created the subscription. 2022-03-29 21:14:47 UTC
Thank you; so Stripe updates the customer.currency automatically when a subscription is created if the currency is not yet set?
Yes, it looks like so.
Should I expect a webhook event for that change to the customer? I don't see a customer.updated event for that change.
So I just made a test, and when creating a new subscription, I do get a customer.updated event that shows that the currency was updated.
But do you see one for this customer's event history? I don't.
(Particularly for the first subscription created)
Hum... still looking but for now I can't find it either.
At least I know it's not just me. ๐
Yes sorry that's odd. I'm not sure why.
Okay; I guess I will need to implement a workaround in these cases for now (as it seems to happen 100% of the time for these customers).
Do you plan to file a bug for this? If so is there some way I can track when it is resolved, so I can remove my workaround potentially?
Also I'm curious: how did you know that the customer currency was updated when the subscription was created for the Stripe customer I linked?
Do you plan to file a bug for this?
Yes we will investigate this on our end. Do you have other customer IDs where this happened?
If so is there some way I can track when it is resolved, so I can remove my workaround potentially?
Unfortunately no.
Also I'm curious: how did you know that the customer currency was updated when the subscription was created for the Stripe customer I linked?
We have internal tools that list all updated to an object, and I could see an update on thecustomer.currencywhen the subscription was created
I have one other customer for sure that has the same issue right off hand: https://dashboard.stripe.com/customers/cus_LOQOIONbjetoc1
Last question before I leave you alone ๐ given the customer.currency is updated when the subscription is created, would you recommend the best workaround would be to update our customer cache on the customer.subscription.created webhook?
(by fetching the latest customer object directly from Stripe)
I know customers are single currency, and we don't capture payment until after the subscription is created, so I am concerened that we make their currency incompatible with their out of band payment method currency.
Well I guess that'd be a problem either way since it's set by Stripe in the first place already.
to update our customer cache on the customer.subscription.created webhook?
Yes, that sounds reasonable to me, since is what should be happening.
Okay thank you very much for your help today.