sfd6088

[unreal dagger]

Can you share some IDs that explain your situation?

[dire flicker]

cs_live_a1lgAOxo..

this is the dead session

cs_live_a1...

this is the live session, that completed the payment

in the metadata you can see the order id i use to check orders

the ecommerce is custom made in laravel

[unreal dagger]

There is no metadata set on either of those sessions. It's set on the associated Payment Intent

[dire flicker]

i'm sorry, yeah, it's set in the pi

[unreal dagger]

Ok, then what is the issue?

[dire flicker]

the problem is that the flow seems broken, user started the payment, I create the session and the payment intent, then redirect to the payment page, and after the payment I expect the webhook to confirm the order. In this case, the webhook confirmed a cs different from the one i created

[unreal dagger]

The flow is broken how? Your integration generated a new Checkout Session which your customer subsequently completed

[dire flicker]

it would have a different order id, that's what i don't get, is it possible for the customer to create a new session refreshing the page? everytime a customer click pay before redirecting him to the stripe page i create a new order

using the cs_live_ to check is correct?

[unreal dagger]

No, refreshing the hosted payment page won't generated a new order. My assumption is they went back to your store and clicked 'buy' again which likely generated a new session

[unreal dagger]

What do you mean?

[dire flicker]

i mean is correct to use the cs_live id to check if the order is payed? i used payment intent but i saw that sometimes it was changing and found the the cs was better.

[dire flicker]

that's the problem, if he went back, and clicked buy again the order id would be different

[unreal dagger]

Then that's an issue you need to resolve in your integration

[unreal dagger]

Based on this predicament I'd say no as the cs_xxx could change

[dire flicker]

you mean that the session can change during the payment?

[unreal dagger]

It will change if your integration creates a new session yes

[dire flicker]

if a customer click buy i create a new order and then a new stripe session using order id in the metadata

[unreal dagger]

Then it seems expected to me that if they click the buy button on your site multiple times they'd get multiple sessions with different cs_xxx IDs, right?

Don't rely on the cs_xxx for fulfilment

Use the metadata on the session for your order reference