#kenpm_api

1 messages ¡ Page 1 of 1 (latest)

wild swallowBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1331578981564157986

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

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.

rose inlet
#

hi there!

#

looks like the error message is pretty clear.

#

what's your question?

tender turret
#

yay, i got "This PaymentIntent could not be captured because it has already been captured." after set "capture_method": "automatic",

rose inlet
#

I don't understand your question. as mentioned in the error message, if a PaymentIntent is already captured, why are you trying to capture it again?

tender turret
#

let me check please wait

rose inlet
#

so why are you trying to capture an already cpatured PaymentIntent? this doesn't make sense, so it's expected to return an error.

tender turret
#

hmm i will check again

rose inlet
#

the PaymentIntent is laready captured. so don't try to capture it again.

tender turret
#

i see, we selected some event so it is call capture again

#

fixed thank you ^^