#iggna_api

1 messages ¡ Page 1 of 1 (latest)

languid flumeBOT
#

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

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

tawdry cairn
#

Hey! Looking into this now.

pine tinsel
#

I already like you bc of outer wilds

#

you are great

tawdry cairn
#

I think in this case there are a couple possible options, each with their own limitation.

  1. Like you said, you can pre-authorize payments now and manually capture them later, which has a default limit of 5 days. However, depending on which pricing option you're using for Stripe, you may have the ability to use extended authorization which allows you to extend the authorization to 30 days. This may or may not work for you, since as you say users might be able to book a whole month in advance, and as months can be 31 days this may be too far out. I recommend reviewing the doc carefully because there are other limitations as well:
    https://docs.stripe.com/payments/extended-authorization

  2. You can also use Setup Intents to gather payment details now and set them up for off-session payment, and then create a Payment Intent using the off_session=true parameter when you're ready to gather payment. However it's worth noting that this flow won't pre-authorize payment, so it's possible the customer's payment details may have changed (e.g. insufficient funds, cancelled card, etc).
    https://docs.stripe.com/payments/setup-intents
    https://docs.stripe.com/api/payment_intents/create#create_payment_intent-off_session

tawdry cairn
#

Literally my favorite game. I think I've convinced 10+ people in my life to play it

pine tinsel
#

on of my easy top 5 too, spent too much time on youtbe on 5 hours lore videos. DLC story is crazy good in my opinion

#

let me read the response and get back to you, a pleasure to meet a fellow outer wilds fan ❤️

#

probably best approach would be option 1, but would like to know, wouldn't be better to set up a scheduler on my end that tracks reservations and payment intents and days before the reservation I automate the creation of a payment intent? I think that would also work.

tawdry cairn
#

The scheduler option you're talking about is essentially my option 2. The only difference is that I recommend starting the flow by creating a Setup Intent, which handles things like cards that require authentication and will reduce the number of failed payments you get when you try to create the Payment Intent by quite a bit.

pine tinsel
#

thing is, customers in our app attach themselves a payment method beforehand, and set them as default payment method that handles all the charges in our system, wouldn't the setup Intent interrupt that flow?

languid flumeBOT
tawdry cairn
#

If you're already saving payment methods you can definitely try to charge them again by creating a Payment Intent when the time comes. However, depending on how you're saving payment methods you could be at risk of the charge being declined. Setup Intents are mostly useful because they handle things like 3DS for you. Can you elaborate on exactly how you're attaching payment methods currently?

#

Depending on how you're saving payment methods now my recommendation may just be to migrate to Setup Intents, which again is just to reduce the number of declines you're going to get when you go to charge the card.

pine tinsel
#

FE provides me the stripe token generated from UI and attach it to the customer on a backend method. Seen in the doc that is recommended to migrate to setup intents but sadly is not in our roadmap now.

#

even I save payment methods, there is no scheduler function built in for payment intents, but is available for setup intents?

tawdry cairn
#

No, setup intents also won't handle the scheduling for you. Based on your use case I think you're going to need to handle the scheduling part yourself no matter how you're saving payment methods.