#alinadialog
cosmic surge
frank pier
No. They have to continue to exist separately unless explicitly deleted: https://stripe.com/docs/api/customers/delete
royal hatch
Is this something on the roadmap? It's hindering functionality greatly and causing a lot of legacy debt.
How have other people handled their duplicates in databases?
frank pier
I think generally other users track the object in their own database and keep it synced with what Stripe has so that duplicates don't occur (or occur so infrequently so as not to be a problem)
Nothing on the roadmap that I know of, but that doesn't necessarily mean it's not on the product team's radar
royal hatch
Sure! I'm actually using a low code website builder, so not building the Stripe instance myself. I'm in touch with the developers there and understand this is ultimately their problem... but I am surprised to hear this is such an infrequent issue, at the very least transferring invoices to another customer.
I definitely get going forward, I'll be trying to work with the developers to curb this problem but for now, we have a lot of legacy issues as our Stripe instance is effectively nuked.
Is there anything you could recommend us to do besides "stop doing that", haha?
frank pier
You could run a report of all your customers, then pare it down to only the customers you want and delete the duplicates, though this essentially just a bandaid cure that won't solve the underlying problem. You could also cache the user-agent on your website to make sure that returning customers are not duplicated, but that would only solve the problem for most future customers, as opposed to all customers.
royal hatch
Gotcha, thank you! What's the best way to keep up to date with roadmap updates?
Apologies for harping, I appreciate the help.
frank pier
Our changelog is a great place to start: https://stripe.com/docs/changelog
