My experience with the product has been that it has made very clear attempts to provide the user ID for SaaS implementations of the payments system.
I first heard of someone who was using stripe to store all user data on the Running in Production podcast, I thought they were nuts.
But then I went to reimplement the services this year due to the deprecation the "legacy" popover modal on Checkoit.
The new version seems more about locking builders to stripe than it is about anti-fraud, checkout UX or developer experience.
It’s subtle but can be discerned from the implementation details and docs or lack thereof. In that way I would suggest the company has made some insidious decisions about the product.
On one hand, it’s hard to blame them, because before their API could be replicated and swapped out like S3.
My experience with the product has been that it has made very clear attempts to provide the user ID for SaaS implementations of the payments system.
I first heard of someone who was using stripe to store all user data on the Running in Production podcast, I thought they were nuts.
But then I went to reimplement the services this year due to the deprecation the "legacy" popover modal on Checkoit.
The new version seems more about locking builders to stripe than it is about anti-fraud, checkout UX or developer experience.
It’s subtle but can be discerned from the implementation details and docs or lack thereof. In that way I would suggest the company has made some insidious decisions about the product.
On one hand, it’s hard to blame them, because before their API could be replicated and swapped out like S3.