#blagi.connecto
abstract jacinthBOT
Hello blagi.connecto, we'll be with you shortly! Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
• blagi.connecto, 4 days ago, 10 messages
gleaming adder
hi! sure, we can look, what's the PaymentIntent ID pi_xxx
dark hemlock
pi_3O3BYbHyMHmjD7NO0r2A5VoO
I don't understand this even: https://dashboard.stripe.com/events/evt_3O3BYbHyMHmjD7NO0JXpjTRH
gleaming adder
it was captured here by the magento plugin you use : https://dashboard.stripe.com/logs/req_QokSheLgsmfrTa
gleaming adder
I don't understand this even: https://dashboard.stripe.com/events/evt_3O3BYbHyMH...
what about it don't you understand specifically?
dark hemlock
It looks to me that this event change something in capture manual to capture. We are not using magento, we have we application. And I don't understands that capture event either. Cannot find it in our logs tha it was initiated. That's why I 'm looking at that payment intent change.
gleaming adder
It looks to me that this event change something in capture manual to capture.
it's a normal event that is fired when the auth on the PaymentIntent happens, it's to let you know that it's possible to capture it manually
We are not using magento
indeed, sorry, I think I hallucinated seeing the word Magento in the log, oops
then really the reason the PaymentIntent is captured is your own code directly called the API to capture it.
dark hemlock
Ok. Thanks. I just didn't find explanation why it's there. It shouldn't be. Hoped you can help me but looks like I have to do some more investigation.
gleaming adder
no worries, but there's not much we can say, we just recieve an API call from your own server and code