carterjfulcher

[dull gale]

^ an example of the aforementioned issue

[humble fractal]

Do you have example Customer IDs that I can look at for these duplicates?

[dull gale]

Sure, here's an example of duplicate pairs:

cus_NhrkkRuD9fEmKB cus_NhrklfB7PVaay4

Using the stripe/firestore-stripe-payments extension version 0.3.1

[humble fractal]

So it looks like one customer (cus_NhrkkRuD9fEmKB) was created and then immediately and repeatedly sent to expired Checkout Sessions: https://dashboard.stripe.com/events?related_object=cus_NhrkkRuD9fEmKB

[dull gale]

I see, any idea what the common causes are for that?

[humble fractal]

That's not a particularly common problem. As far as I can tell Firebase is creating all the Checkout Sessions, and then they're expired when your Customer gets redirected to them. Take a look at Source header on these requests: https://dashboard.stripe.com/logs?method[0]=post&method[1]=delete&path=%2Fv1%2Fcheckout%2Fsessions&direction[0]=self&direction[1]=connect_in&showIP=false

[dull gale]

I am seeing a lot of checkout sessions in Firebase, but I wonder if these are just the customer being redirected to the checkout after they've already paid (stuck in a loop)

Does it seem like it's an issue on our side or with the firestore extension?

[humble fractal]

Hard to say, but somehow multiple Checkout sessions are being created and then the Customer is getting redirected to them after they've expired. Beyond that, I don't have a lot of visibility

[dull gale]

Okay I’ll investigate that avenue and let you know if I have any other questions. Thanks!