#giuseppe_best-practices
1 messages ¡ Page 1 of 1 (latest)
đ 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/1326144685751795732
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Not directly with a single Payment Intent, no. You'd need to create one for each part of the payment. Alternatively there's an invoicing beta you could look at: https://docs.stripe.com/invoicing/payment-plans
I saw that the payment is not done automatically, but the customer is contacted each time with an email to make the payment, if instead I create a payment intent with the deposit payment by setting setup_future_usage to off_session then with my own internal schedule I create other payment intent on the date I need can it work?
Yep, that can work too. setup_future_usage will save the card so you can charge it off-session as required: https://docs.stripe.com/payments/save-and-reuse?platform=web&ui=elements#charge-saved-payment-method
This the the full guide you want actually: https://docs.stripe.com/payments/save-during-payment
Details how to save during initial payment, and then make subsequent charges as per your schedule
Reading https://docs.stripe.com/payments/save-and-reuse I saw that the payment can fail with 402 status, if it happens and I try again to make the payment with the same card it fails until the customer gives authorization right? and to make a new authentication just the customer creates a confirmpayment in the browser?
Yes, if the off-session payment fails because auth was requested then you'd need to bring the customer back online to auth the payment. It can happen, but we do try to reduce the chance of that by requesting exemption (enabled by setup_future_usage)
ok thanks