#kelvin_code

1 messages · Page 1 of 1 (latest)

gritty ruinBOT
#

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

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

inland iris
#

Could you share where do you take that code from? I think our official Doc only mention about intentCreationCallback

whole sky
#

handleNextAction is recommend by our BE team, and we currently use it on Web

#

can you help explain me the differenciation between intentCreationCallback and handleNextAction ?

inland iris
#

Normally it should be intentCreationCallback only. The PaymentSheet should handle the needed nextAction, which is often be used by handleNextAction

whole sky
#

is there any resource to read about it? or any docs that i can tell my BE team that Web is handled different from app in this case?

inland iris
#

Build an integration where you render the Mobile Payment Element before you create a PaymentIntent or SetupIntent, then confirm the Intent from your server.

#

So intentCreationCallback should already cover the handleNextAction