#intelagent_api

1 messages · Page 1 of 1 (latest)

mental crowBOT
#

👋 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/1262865836134236211

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

obsidian wrenBOT
#

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.

kindred scaffold
#

I presume you are supplying a payment_method token in your request?

keen hazel
#

Oh man, of course I just found it.

kindred scaffold
#

on the first payment by the customer you need to create the intent with:
payment_intent_data[setup_future_usage] = "off_session"

then in subsequent requests you can pass the payment_method and customer.

keen hazel
#

We can close this, thank you

keen hazel
#

I tried to open a new thread, but it directed me here. I'm migrating my checkout flow to use confirmation tokens. The confirmation token is first generated on the client, and then sent down to the server to confirm the payment. However, we have 1 payment intent per cart so we first create the payment intent and update if needed on checkout. But when manually confirming the payment intent (since we don't want to create and confirm at the same time), I'm getting this error: confirm payment intent: {"status":400,"message":"Payment details were collected through Stripe Elements and cannot be confirmed with a Payment Intent configured with manual confirmation_method."}

mental crowBOT
inland lichen
#

👋 Stepping in for my teammate

keen hazel
#

Hey thanks!

inland lichen
#

I think there might be a misunderstanding here. Using confirmation_method: manual means you intend to confirm using a secret key. I think you intend to use confirm: 'false' instead? Since confirm defaults to false, there's no need to pass this parameter at all when creating the PaymentIntent

keen hazel
#

Oh I see. The golang docs say: Describes whether we can confirm this PaymentIntent automatically, or if it requires customer action to confirm the payment. You are correct, this worked but I still don't understand what this parameter means?

inland lichen
#

This can likely be explained better in our docs. Using manual confirmation means that funds will only ever move if the PaymentIntent is confirmed server side

keen hazel
#

I am confirming the payment intent server side in this case, so wouldn't I want manual confirmation?

inland lichen
#

Sorry, this is a little tricky to explain. "Manual confirmation" is not "server side confirmation". "Manual confirmation" means that a re-confirmation is needed server side to move funds.

Since you're using ConfirmationTokens, you should omit confirmation_method altogether (this will default to automatic) and confirm the PaymentIntent when you're ready

#

Also, "manual confirmation" is different from "manual capture"

keen hazel
#

Correct I think I'm clear on the differences there. Appreciate your help