#hendr1x_api

1 messages ¡ Page 1 of 1 (latest)

modern nacelleBOT
#

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

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

tight fiberBOT
#

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.

twilit cairn
#

I notice you are now asking for confirmation_token in the setupIntent->confirm() method. Where am I getting this from.
This isn't a required parameter. You only need to pass this if you use one of our integration paths that use confirmation tokens.

I notice bother paymentIntent->create() and paymentIntent->confirm() have flags for setup_future_usage...is it required to do it in both places?
No you only need to set it once on the payment intent

marble zinc
#

I think I made a mistake

#

Sorry...I think made a mistake with my first question...I'm only using paymentIntents NOT setupIntents

#

You guys changed a guide on me so I'm all messed up

#

So this guide its telling me to use confirmation_token

#

I remember somewhere it said it was the proper way to handle things...and I should change my code to support it

twilit cairn
#

Do you want to do two-step confirmation?

marble zinc
#

Yes

twilit cairn
#

We deprecated the old way of creating a payment method first

marble zinc
twilit cairn
#

Confirmation tokens are the new way

#

Yep exactly

marble zinc
#

Ok...this is a new site and I want to make it setup as best as I can

#

So convert payment_method to confirmation_tokens is the most up to date approach?

twilit cairn
#

Yeah if you want two step confirmation, we highly recommend using confirmation tokens

#

That's the latest flow

marble zinc
#

So, can I just ask, if a visitor on my site wants to change their payment information or address...how do I handle that

#

Do I have a way to update or do I delete the confirmation token and create a new one?

twilit cairn
#

No confirmation tokens are just temporary objects to confirm a payment intent with

#

If you're referring to the billing address, you'd want to update it on the payment method object (or customer object)

marble zinc
twilit cairn
#

A payment method is created when you confirm the payment intent

#

The old flow created the payment method up-front

marble zinc
#

Yeah...thats how my system is coded now

twilit cairn
#

If possible recommend you use confirmation tokens

marble zinc
#

Ok....so, after I create a confirmation token....how do I change it...assuming the change happens before the payment method is created

twilit cairn
#

There's not an endpoint to update a confirmation token unfortunately

marble zinc
#

No problem...so is there a delete command or should I just create a new one?

twilit cairn
#

Just create a new one. They're really supposed to be temporary objects

#

There's not a delete