#nickagain
spice zealot
wanton flame
HI 👋
Do you have example customer ID's I could look at? Has your integration changed in any way that it may be creating new customers instead of using the IDs of existing ones?
plain spindle
The integration should not have changed, but it is something I'm exploring as well. Different things are happening with different ones. This customer number was with one customer, then got assigned to another cus_MnnHaCVFVzJG4o . This customer
was a test customer we had and is now cus_NEmAV6DuMYIQjf but was cus_MngiHn9VnXiZWv
wanton flame
Okay lets take a step back. Do you have your own record system that tracks customers? How do you know they are changing?
Okay for cus_MnnHaCVFVzJG4o it was directly created by your PHP code. Here's the request: https://dashboard.stripe.com/logs/req_5a5EgkSmKSUAJn
plain spindle
Yeah, when we call the api to create a payment intent we see if the customer on our website has a stripe account by a stripe customer id in our database, if they don't we create a new one, otherwise we use the one we have recorded already. So we know what the customer id was when it was first created.
wanton flame
All of these were created by your server.
So something in the logic of looking up the customer ID on your end is failing
There is nothing automatic happening from Stripe
plain spindle
Correct. The weird thing about that one is that the same customer id was used for two different orders, but that one is a little more out of our control. Because it is a third party app.
Correct they should be. But they seem to not line up over time. It is very possible it is an implementation error but I first wanted to make sure that a customer id wasn't infact mutable, as that seems to be what is happening. so I think that answers my question, thanks!