#hendr1x_api

1 messages ¡ Page 1 of 1 (latest)

eternal jacinthBOT
#

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

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

wise edgeBOT
#

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.

eternal jacinthBOT
humble yacht
#

Hello?

summer nacelle
#

When you're collecting and validating payment details, you're either intending to collect payment then or not (later). This is the difference between a setup intent and payment intent

#

If you have an amount and intent to charge ~now, use payment intents, optionally saving the card for later use with setup_future_usage. If no payment now, only to be decided later, use a setup intent.

humble yacht
#

So does setup intent handle authentication/3ds?

summer nacelle
#

Yes

humble yacht
#

at time of setup or when payment occurs?

summer nacelle
#

At setup time, when you confirm the setup intent

humble yacht
#

ok...man...I wish I was told about this 5 days before I coded everything

#

So is there any tutorials available that show setupIntent

summer nacelle
#

It should only be a few small changes to switch

humble yacht
#

ok, thats good

#

you guys have all been great fyi

#

not trying to complain

summer nacelle
#

initialize payment element in mode=setup instead of mode=payment, use confirmSetup instead of confirmPayment and on the server create a setup intent instead of a payment intent

humble yacht
#

Ok...I'm looking at the docs now

#

No tutorials/walk throughs though?

summer nacelle
humble yacht
#

Is there any downsides to this approach that I should know about?

summer nacelle
#

One of those, depending on whether you create your intent up front or only just-in-time when the customer confirms

#

You just need to be ready to handle additional authentication if the bank ask for it when you do the off session payment later

humble yacht
#

Thats the 3ds stuff that was talking about earlier

#

Sorry...I thought you said it was taken care of during setup

#

This is the same problem I have with paymentIntent

#

Am I misunderstanding?

#

Does setupIntent have this same issue?

summer nacelle
#

Yes, thats always a possibility

#

When set up on the client initially, this should happen less, but the bank always has the option to require authentication again, you can't avoid that

humble yacht
#

Ok...so if I understand correctly, setupIntent requests authentication from visitors if needed but the banks may always require it happen again?

summer nacelle
#

Yes, exactly. Any off-session payment in future can be declined for requiring additional authentication, this is true no matter how you initially collect the payment details.

#

The point is to do the confirmation with the customer on-session once up front to hopefully reduce that in future, but it is always possible

humble yacht
#

Understood...thanks for explaining everything so clearly

#

I appreciate it

#

I'm all set for now. Have a good day!

summer nacelle
#

NP! happy to help -- you too!