#Peter Silie
1 messages ยท Page 1 of 1 (latest)
๐ Thanks for reaching out
Stripe does not guarantee delivery of events in the order in which they are generated
https://stripe.com/docs/webhooks/best-practices#event-ordering
In the dispute object, you have the related payment_intent Id
https://stripe.com/docs/api/disputes/object#dispute_object-payment_intent
Yes, true but if O create a Order in my Database I only have the stripe_checkout_id and no payment_intend id.
Until I get the session.completed from the Webhook I can't store a payment_intent id
But the dispute.created come only with the payment_intend id.
As you can see here, there is no payment_intend id while creating the session.
Any Idea or best practice?
Ah I see, you don't have the link betwen payment_intent and the checkout session. Probably you need to store the dispute in a temporary location (separate table) and once you get the session.completed event you make the link and you complete the flow
Yes I think the is the only way. I need to have some more checks in the session.completed moment.
I'm even writing a log in a table, maybe I van reley on that.
In Testmode, how can I set a Payment which is fraudulent to "ok".
I can send the money back with "challenge lost" but how do I test the opposite?
I can only send the "proofs" but the payment remains pending.
Hi there ๐ I'm jumping in and catching up on the thread. With our newer API versions it is expected for Checkout Sessions to no longer create a Payment Intent during their creation (so the payment_intent field on the session object remains null), instead they are created while the customer is completing the checkout process.
Regarding your more recent question, I think it sounds like you're trying to test out dispute flows. Do the test Evidence values provided here help you achieve that?
https://stripe.com/docs/testing#evidence
I'll take a look
Oh I see, I can enter a special Text in the Dashboard.
Thanks a lot.
Happy to help!
Thanks a lot, you can close this thread.