#simon_payments

1 messages ¡ Page 1 of 1 (latest)

modern heronBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1248336482779926569

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

vital rapids
#

Hello! Yes, you can confirm it months later as long as you don't cancel the Payment Intent

modern heronBOT
#

simon_payments

sterile seal
#

thanks so much for answering so quickly!
a quick follow up however: what would push my team to use SetupIntents over just creating incomplete PaymentIntents?

vital rapids
#

Setup Intents are what you should use if you want to save a Payment Method to be used in the future but not charge it immediately

sterile seal
#

Is that different from creating an incomplete PaymentIntent that also has a PaymentMethod and leave it incomplete for a month?

vital rapids
#

They're not really comparable - an incomplete Payment Intent means that you want to charge some amount and you just haven't completed payment. A Setup Intent has no potential to charge a customer. For most folks that use Setup Intents they'll create + confirm the Setup Intent to properly configure the Payment Method and when it's time to actually charge the customer in the future that's when they create the Payment Intent

sterile seal
#

ahh I understand

#

it sounds like I will be leverage incomplete paymentIntents for my use case

#

this was very helpful, thank you! I appreciate you (: