#hendr1x_api

1 messages ¡ Page 1 of 1 (latest)

crystal urchinBOT
#

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

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

midnight ploverBOT
#

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.

past grove
#

Hello

dusky canopy
#

Hello

past grove
#

No a Customer is not required for a SetupIntent

dusky canopy
#

Ok. That helps me a lot.

past grove
#

You should be able to test this quite easily as well!

dusky canopy
#

My code is far from being able to test yet .....ol

#

lol

#

Your documention might be incorrect

#

Step #4

#

"To set up a payment method for future payments, you must attach it to a Customer. "

past grove
#

That documentation assumes you are going to charge the Customer later

#

In which case you would use a Customer object, yes.

#

If you don't use a Customer then the PaymentMethod can only be used for a one-time payment

dusky canopy
#

Sorry...I'm not clear

#

I want to charge the customer later

#

but only one to do so once

#

*but only want to do so once

past grove
#

Hmm well then you don't technically have to use a Customer but I would strongly recommend doing so in case you end up needing to charge them multiple times or you want to retry a charge attempt

#

If you do not attach the PaymentMethod to a Customer then you only get one attempt, then the PaymentMethod is consumed and can't be used again

dusky canopy
#

So the scenerio I am trying to figure out is a guest checkout...where I collect payment..an admin will review order and then charge after it has been reviewed (off session)

past grove
#

Sure, I'd still attach the PaymentMethod to an empty Customer object

#

If you really want to, after you successfully take payment you can delete the Customer

#

But by going this route you give yourself flexibility if something goes wrong

dusky canopy
#

Ok. That does sound like the best approach

#

And in regards to deleting the customer object after...that will just help keep my stripe admin area cleaner I assume?

past grove
#

Kind of... it is more of if your customer doesn't think you are going to store their data, but that is up to you really

dusky canopy
#

ok

#

make sense

#

Thanks for your help...again!