I tried to set up a process to allow for automatic detection of Stripe Payment Failures in my app because as far as I can tell, this functionality is not present in the Bubble Stripe Plugin.
Now what I am experiencing is perplexing and a bit annoying. I am seeing two different “Paid” status dependent on how I am retrieving the information, despite all other aspects to the invoice being the same.
Notice that the two different repeating groups are showing the same Invoice ID, Subscription, Total, Period Start and Period End information, however the difference is the Paid status. One says YES the other says NO.
I set up one repeating group using the Get Stripe Invoices function
In this repeating group I am getting the Paid status of YES
The other repeating group I used entries I saved to my Database
I set up a database data type of Payment Details and added a list data field for stripe invoices and set up a backend workflow to add the users most recent invoice to this list at the end of each payment period (when a new payment would be made, which could be successful or fail)
The backend workflow is saving to the database correctly, at least it seems that way, however the repeating group with this list of invoices shows the Paid Status as NO
In my Stripe account I have only one user with this email address and all payments are showing that it succeeded
If I was able to see something within Stripe that would signal there are two customers with the same Email, I’d understand why there could be the issue, but there is not, it is the same customer.
What is more annoying about this as well is that my backend workflow that is set up to trigger based on a failed payment is using the conditional to check the Paid Status, and if the Paid Status is NO it is supposed to trigger the failed payment workflow but it has never been triggered, presumably, because it is getting the correct Paid Status which would have been YES the entire period and was instead triggering the backend workflow for successful payments.
Also, looking at my logs, it shows the scheduled workflows is based on a successful payment with a Paid status of YES
Any ideas why this would be happening?