๐Ÿคท๐Ÿฝ Stripe, Buildship, & Firebase for Recurring Payments ๐Ÿ˜ญ

Database & APIs

Hey friends! My Flutterflow app uses Stripe for transactions. I am using Buildship to manage the backend of that. I'm having a hard time figuring out how to distinguish initial checkout events from recurring subscription payments. More importantly, I'm having a hard time figuring out how to get Stripe to give me enough information to run necessary operations when a recurring subscription payment happens.

For an initial checkout event, I'm able to have FF send Stripe metadata that I can use to create and make changes to Firebase docs as necessary. But I can't figure out how to get the recurring payments that Stripe does automatically to contain similar information.

An example of what I need to be able to do is create a "Transactions" doc in Firebase when each recurring payment happens. Creating that doc requires Firebase information like the Seller's Doc ID, the Customer's Doc ID, the original Product's Doc ID, and the Doc ID of the Customer/Seller relationship doc. (All of which I'm able to include in the Metadata of the initial checkout because it originates from Flutterflow, but the recurring payments originate from Stripe.)

Any thoughts? Thanks!

What have you tried so far?

I've analyzed the information currently available from the Stripe API when a recurring payment comes through.

Did you check FlutterFlow's Documentation for this topic?
Yes
3
2 replies