#blkprnt
tribal bone
native ferry
that helped, thank you.
i had more more question
For the "invoice.paid" event, the documentation states “Continue to provision the subscription as payments continue to be made. Store the status in your database and check when a user accesses your service. This approach helps you avoid hitting rate limits.” Could you elaborate a bit more on what approach exactly would help us avoid hitting rate limits? I was a bit confused on this description
cedar flower
instead of checking each time the status of a subscription on Stripe API you would check it on your database
native ferry
makes complete sense
from my understanding, when creating a new Checkout Session, there's a field called ClientReferenceID that we can pass which can represent the userID in our internal systems. this way when we get callback's from stripe, the ClientReferenceID will be on the event for us to reconcile who the user is. does that sound correct?
cedar flower
yes
native ferry
if a user has a monthly subscription, and then say a two or 3 days later they upgrade to the yearly subscription, what event is sent? customer.subscription.updated
