#Paul Han
1 messages · Page 1 of 1 (latest)
I understand this is a case-by-case basis kind of question, just wondering if Stripe had a general suggestion/opinion
Hello! It depends on your use case, business needs, and integration. Generally speaking we do recommend you keep some things on your end and rely on Stripe for others. For example, it's common to add the Stripe Customer ID to your database and associate it with your own user accounts. It also often makes sense to store info on your end regarding past/current payments.
May I ask what might the benefits be of storing past/current payments?
If you have something like a subscription service it would be good to store the paid/unpaid status on your end so you don't have to fetch the Subscription from Stripe every time you want to check to see if you should grant access to paid content or not.
ah that makes sense
is there a doc/article that might go over some of these cases? nw if not, just wondering
No, not really, sorry.
okay no problem, thank you so much for your help 🙏