jokamax

[scarlet quartz]

Yes as the metadata set on the Payment Link only propagates to the Checkout Session object and not the underlying Payment Intent

We're working on adding support for that via a new parameter

[whole garnet]

Ok thanks because I received two events not event not attached... so I have duplicate line on my side

But I understand : I will try to find a way to work with the anonymous payment intent

[scarlet quartz]

Recommendation is to generally just rely on the checkout.session.completed event and ignore the payment_intent.* events

[scarlet quartz]

The workaround for now would be to update the Payment Intent metadata post-payment in a webhook

[whole garnet]

I can't ignore them : I have also real paymentIntent from other way of payments.

[whole garnet]

I will try to check that

[scarlet quartz]

Yeah sorry I meant speficially for those generated by a Payment Link. But unfortunately there's no easy way to identify them

[whole garnet]

Ok thanks 😢

[scarlet quartz]

You'd need to map the id from the payment_intent.* event to the payment_intent field of the checkout.session.completed event: https://stripe.com/docs/api/checkout/sessions/object#checkout_session_object-payment_intent

[whole garnet]

I understand : so I have to integrate payment intent for nothing in my DB and next cancel it if a checkout linked is found... Ok I will wait for the new data link to the payment intent lol

But thanks a lot for the solution

I will explain to my boss

[scarlet quartz]

Not really sure what scenario you're describing. Why would you cancel a PI?

You can't cancel a PI created by Checkout

[whole garnet]

Cancel in my DB (mysql) Mirror. Internal functionning : intent by webhook are saved

Don't worry : it's good.
I have the way