You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user successfully pays for their subscription, only a 'checkout_sessions' subcollection is created in Firestore. There is supposed to be a 'subscriptions' and a 'payments' subcollection that is created when a user succesfully pays for a subscription. I am not the only user experiencing this issue.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
I experienced the same issue with the firestore-stripe-payments setup. Here's how I resolved it:
Check Stripe Webhook Posts: I started by examining the Stripe webhook posts to understand the issue better. In my case, I found an error (see attached image for reference).
Review Cloud Function Logs: Next, I reviewed the Cloud Function logs to pinpoint the exact problem. The logs indicated there was an issue with the Stripe key.
To resolve the problem, I deleted the existing Stripe key and created a new one. After updating my configuration with the new Stripe key, the issue was fixed and the 'subscriptions' and 'payments' subcollections were created successfully when a user paid for their subscription.
I recommend following these steps:
Check your Stripe webhook posts for any errors.
Review the Cloud Function logs to see if there are any issues mentioned.
Please let me know what errors you find, and I'll be happy to help diagnose and resolve them.
Bug report
firestore-stripe-payments
Describe the bug
When a user successfully pays for their subscription, only a 'checkout_sessions' subcollection is created in Firestore. There is supposed to be a 'subscriptions' and a 'payments' subcollection that is created when a user succesfully pays for a subscription. I am not the only user experiencing this issue.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
The text was updated successfully, but these errors were encountered: