#dgsunesen
leaden hatchBOT
Hello! 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.
late vine
Hi there, are you asking why many payment intents wered created for the same customer?. Do you have the ID of one of payment intents?
cold wadi
sure
this is the customer it happend for
you should be able to see the list of all the payment intents that happend
late vine
https://dashboard.stripe.com/logs/req_zUz05L6cPpNYFT based on the log, this payment intent was created by using your secret key
https://dashboard.stripe.com/logs/req_YSqiNsjckMZBOg hmm, this request was created from a different IP address
Are you running a distructed system where API calls are made from different servers from different countries?
cold wadi
nope
late vine
Then there's a possiblities that your API key is leaked, you should roll it asap https://stripe.com/docs/keys#rolling-keys
cold wadi
Okay. Hm...
Lets say API calls are made from different servers, what would then be an approach to try and see what could be the reason for this?
late vine
I don't know. All I can see is these requests were created with your secret key.
cold wadi
All right — thanks for looking into this. I just looked a bit further into it, and in fact it does API calls from differnet servers / nodes (sorry for the misinformation)
so I don't think the API key got leaked
late vine
Great! good to hear that, then you should check your server logs to determine why it created so many payment intents