#StephenPaoli
1 messages ยท Page 1 of 1 (latest)
Hello ๐
Can you share the example PaymentIntent IDs for 1? ๐
For 2/ We don't implicitly copy metadata between objects. It is possible that the dashboard is pulling the metadata from the PaymentIntent object instead. Yes, please share the example
For number 1: pi_3MeekAD4siJYPQuY03L2TrfG, pi_3MealwD4siJYPQuY2qdGUVTz, pi_3MdlkhD4siJYPQuY2ohm3lFz, pi_3MeSqjD4siJYPQuY0UdlvxdN
Apologies, now that I'm looking at it a little closer for number 2, I think that this is a case of us charging a merchant directly through the Stripe dashboard, rather than going through our system. The Payment ID is py_1Mf24aD4siJYPQuYXrLefCco.
For 1/
It doesn't look like confirm: true was passed in the request body which explains why they're all in requires_confirmation status
https://dashboard.stripe.com/logs/req_tmZh13Arm3wREB
https://dashboard.stripe.com/logs/req_JIlESDE7frpoMJ
https://dashboard.stripe.com/logs/req_TfxMSXp6v6H9TB
https://dashboard.stripe.com/logs/req_6QvcpwiiysAoau
For 2/ The example payment you've shared was created by calling the API directly from your server
https://dashboard.stripe.com/logs/req_2oDxNPk6rArrV3
However, no metadata was passed in the request body. So the charge.succeeded event wouldn't have any metadata either.
Let me know if that clarifies ๐
This was a big help, thank you! They both make sense, number 2 is correct, I think we have to set up a way to ignore those webhooks. I will have to do some digging to figure out why we aren't sending the Confirm property on our requests for number 1. But I am going in the right direction, thanks again!