#daniele-de-benedetto_webhooks

1 messages ¡ Page 1 of 1 (latest)

cold dirgeBOT
#

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

📝 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.

blazing flare
#

What guide are you following? can you share with me the link?

hearty pilot
blazing flare
#

The guide that you are following is for PaymentIntents API, but you are using chekout sessions API

#

PaymentIntent created by a checkout session can't be updated.

hearty pilot
#

is the ones that your collwgue gaves to me yesterday

#

ok i try to have a look to this one

#

ok the guide says to handle the hook, but there is no explaination on what i need to do to 'close' the checkout session

blazing flare
#

No you don't need to handle such case

hearty pilot
#

ok, but i have an external system in wich i need to send the 'amount' in some cases i receive only
checkout.session.async_payment_succeeded if the amount is totally covered, in the other cases i receive payment_intent.partially_funded but i there are multiple payment_intent.partially_funded i receive checkout.session.async_payment_succeeded

how can i handle the 'amount' once, the risk is that managing the payment_intent.partially_funded and the checkout.session.async_payment_succeeded i can count twice

#

or there is a hook only for get the amount that the user transfer, without checking for the checkout.session.async_payment_succeeded ?

blazing flare
hearty pilot
#

yes but if the user never send all the founds i loss the partial founding

#

i can't reconcile them in my external system

blazing flare
hearty pilot
#

clear but you agree with me that this webhook is never fired if the user send only one partial payment ?

#

my system for example says that there is an outstanding balance of 200, the user send a bank transfer of 100

if the user never send the remaining 100 for my external system there is still an outstanding of 200

#

and for my vision i want to bill him of 200 because i don't know that i receive 100

blazing flare
#

I see what you mean. yes checkout.session.async_payment_succeeded will only be fired when the customer has completed the payment. Sending one paritial payment won't trigger it

#

If. you want to complete the payment with partially applied funds by updating the paymentIntent amount, you should use paymentIntents API directly because paymentIntent created by a checkout session can't be updated.

hearty pilot
#

ok, but i cannot use the embedded form with a payment intent api, i need to build the ui by my self

cold dirgeBOT
snow heath
#

hi! I'm taking over this thread.

#

if you are directly creating the PaymentIntent, then you should use the Payment Element to collect the payment method information.

hearty pilot
#

yeah, i need to change all my integration, just to handle partial found in checkout session ? really? also is not consistent,because the first hook is partially founded, but i i found all the remaining amount, i'm not receiving the other 'partilly founded' but only the succeded, that seems that the user send the 'total' amount instead of a partial

snow heath
#

well creating a PaymentIntent directly gives you more control over the payment flow. It seems like your use case it quite specific, so it makes sense to create a PaymentIntent for this.