#hendr1x_api

1 messages ¡ Page 1 of 1 (latest)

low ingotBOT
#

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

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

woven pewterBOT
#

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.

umbral valve
#

Hello

atomic gulch
#

Working through the two step confirmation guide...it seems like confirmPayment() submits the payment for processing and it also does vital steps such as authorization

#

Hello

umbral valve
#

Yep that's correct

atomic gulch
#

What I was hoping to do is take care of all authorization steps etc while I have the client "on_session"...and then have the admin review the total amount...perhaps make a change. And then charge

#

Is this possible?

umbral valve
#

You want to actually perform the authorization first and then have the admin review?

#

In that case you can't really make changes to the authorization -- you would have to cancel and perform a new authorization.

#

With the two-step flow you would collect the PaymentMethod and have the admin review before then performing the authorization.

atomic gulch
#

But in some cases the authorization requires the customer to be on_session correct?

#

So it seems like I can't do what I was hoping to do

umbral valve
#

Some authorizations will require 3DS to be completed, yes.

#

You aren't planning on having the customer be present when the admin performs this check?

atomic gulch
#

No...the order was going to put in a queue to be reviewed

umbral valve
#

If that's the case, then you would use manual capture for the admin check, but the only adjustment that can be made in that case is to either cancel or partially capture the amount. You wouldn't be able to increase the authorization

#

Does that work for what you are looking for?

atomic gulch
#

Can i just ask if it is possible to somehow bring the customer back into the session if 3ds is required. Does that question make sense?

umbral valve
#

Yep you could certainly do that.

atomic gulch
#

Do you a tutorial on resurecting sessions?

#

I'm also interested in learning more about the manual capture if you have a link for that I would appreciate it

umbral valve
#

That guide is very similar to the two-step guide, except the two-step guide assumes your customer is still present when you create the authorization

atomic gulch
#

Ok...yeah...looks almost the same. Can you confirm, it seems like all I have to do is get the client on a page and run handleNextAction()

umbral valve
#

Yep

atomic gulch
#

So how do I know if a next action is required? When I create a paymentIntent does it return an error?

#

actually I think I see it now

#

handleServerResponse()

#

oh...I find out when I create the confirmationToken...so I have to store that I guess

umbral valve
#

It returns a status of requires_action

#

No you find out when you confirm the PaymentIntent on your server

atomic gulch
#

I'm sure you are right but that does't seem to be how the guide is showing it

#

handleServerResponse() is run based off response of confirmationToken

umbral valve
atomic gulch
#

Sorry...I don't use react....so I see /create-confirm-intent......it req, res which is generated from the await stripe.paymentIntents.create()?

#

So using vanilla js it would be...

#

const {req, res} = await stripe.paymentIntents.create({});

#

?

umbral valve
#

This is on your backend so perhaps you are using Node? If so, then it would just be:
const intent = await stripe.paymentIntents.create({...

atomic gulch
#

PHP....ok...thats all i need, I can figure it out in PHP no problem

#

Last question please

#

So handleNextAction()...has to run on the frontend...and am I correct that it basically is just a redirect

umbral valve
#

Ah I see the code snippet in the docs makes it look like that is client-side as it is an app.js file

#

I'll flag that internally to get fixed

atomic gulch
#

If a person coded in node more they would probably know...definitely a bit confusing for me

umbral valve
atomic gulch
#

Perfect

#

thanks for your help. I appreciate it